| Summary: | [navigation] Go to Line dialog should remember the last entered value | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Stepan Herold <sherold.dev> |
| Component: | Text | Assignee: | Platform-Text-Inbox <platform-text-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, markus.kell.r |
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Stepan Herold
I rather think the dialog should be pre-filled with the current line number, see bug 236241. To get a history, the text field could be converted into a combo. I disagree with comment 1. Especially adding a history with line numbers sounds overkill. I don't think that prefilling the text field with the current line would make much sense. There is no point in using the dialog for bringing you to the line where you already are. You should think about the use cases the dialog was intended for in the first place. snippet from bug 236241: >Advantages: >- Allows to copy the line number >- Allows to modify the line number (e.g. when you mistyped 17493 as 17439) Advanatage #1: This seems to me like a hack. The dialog was designed to take you to a desired line and not as an aid for copying the current line number. BTW, most of the developers I know have the editor's feature 'show line numbers' always on and writing down the line number manually takes you less than a second. Advanatage #2: This should work even better with the fix suggested in this bug, because you would always get the last mistyped value even if you changed the line between the two dialog invocations. Due to accessibility benefit we'll initialize the dialog as suggested by Markus. In addition, I don't want to remember the last line number per file. |