This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Document popup search in explorer | ||
---|---|---|---|
Product: | platform | Reporter: | Lukas Hasik <lhasik> |
Component: | Explorer | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | deep_pl, jglick |
Priority: | P3 | Keywords: | UI |
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | TASK | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 33932 |
Description
Lukas Hasik
2003-05-27 15:00:42 UTC
popup search spec: - User is focused in the TTV (Explorer, Property sheet). - User will start to write/type a character. - Popup textfield will appear and characters will be visible in that Textfield area. - TTV will automatically scroll to the node that matches these written characters(pattern). - arrow up/down moves selection only on nodes matching the pattern. - when last character is deleted from pattern by Backspace then the first occurence of 'new' pattern from top is selected. - By ESC key press that popup disappears. - Last automatically selected node stay selected. assigning Jesse to comment. Jiri, is this ok ? Thanks a lot, Lukas. Only small corections: - User is focuse in TreeView (not in TreeTableView aka TTV), - if search popup is opened then a TAB press fills in the longest possible prefix of all matched nodes -popup search works only on expanded nodes in Explorer 1. TAB does not do anything in the popup search window for me; I was not aware it ever did. 2. The popup search feature works in all TreeView's AFAIK, not just the Explorer. But yes, it only works on expanded nodes. (Which is a bit of a bug - if some nodes are still expanding and you start typing too soon, it will fail to find things that are not yet there. TV.ET.doSearch should be using getNodes(true) I suppose.) Aha, TAB does do something, but it is broken. It completes the code name, rather than the display name; and the code name may be missing, or completely irrelevant to the user. I will fix this; it looks easy. Assigned to new owner. Isn't this obsolete? Please close if it is. is the behaviour of QuickSearch documented? + publish the link here and close bug - document it and then publish the link here and close bug ;) Reassigning to new module owner Tomas Holy. *** This issue has been marked as a duplicate of 56256 *** Nothing to do with the issue it was marked duplicate of, please reevaluate. OK, closing, as I have little clue what else shall be done. Sorry for a comment after such a long time since the last post. There is a need to insert into search pattern "*" or "%" will which represent any characters. If I understand what deep_pl is asking for, it would be an RFE in this component but otherwise unrelated to this issue (whatever this was). |