Bugzilla – Full Text Bug Listing
| Summary: | [win32] Text.selectAll() does not work as expected if a Text control has a tool tip | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Benjamin Leipold <benjamin.leipold> | ||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | cocoakevin, eclipse.felipe, niraj.modi | ||||
| Version: | 3.5 | Keywords: | triaged | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows All | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Benjamin Leipold
Created attachment 152959 [details]
Reproducer for the described behavior.
Why do you call selectAll() from mouse down ? Usually people call selectAll() from focus in. Because i have the same problem described as here: http://dev.eclipse.org/newslists/news.eclipse.platform.swt/msg14487.html. I see, you can use FocusIn+asyncExce instead of MouseDown. But neither works well when the user hold button1 down for one or two second (or worse, moves the mouse). To fix that you can use MouseUp, is that an option for you ? I will have a look at mouse up. But even if mouse up is an option for me, it is a bug, isn't it? (In reply to comment #5) > I will have a look at mouse up. But even if mouse up is an option for me, > it is a bug, isn't it? Not sure, note that the text without the tooltip also has the same problems, (click and hold the mouse down for a little longer and you will see it). What your are trying to do is valid, and I'm trying to help you find the best implementation. At this point I'm not sure if calling selectAll() from MouseDown alone is the right answer. Note the address bar in IE works the way you want and doesn't have any for the problems we have. I've tried MouseUp and it works well (every user must release the mouse button sometime ;-)). But, from the user's point of view, select all on a MouseDown event would be the more intuitional way. (In reply to comment #7) > I've tried MouseUp and it works well (every user must release the mouse button > sometime ;-)). But, from the user's point of view, select all on a MouseDown > event would be the more intuitional way. How does it look if you do it on both (mouse down and mouse up). Sorry that I'm just suggesting random ideas, I haven't had time to actually work on this problem. If i do it on both events, on mouse down only part of the text is selected and on mouse up all. But there seems to be another problem. If all text is selected on mouse up, the tool tip is never shown again. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |