Community
Participate
Working Groups
I20070918-0010 In a long text editor, select a word and drag it to the top or bottom edge of the viewport. The text area starts to scroll, but the line number ruler and the vertical ruler don't scroll.
The widget goes into 'silent' mode while dragging the text i.e. no mouse move events are sent out. BTW, is there a simpler way to detect StyledText's viewport change than listening to key and mouse events? E.g. something like a viewport listener on the scrollable?
During drag you are not suppose to receive mouse events. How do you update the line number ruler ? Do you listem for Selection change events in the vertical scrollbar and in the styledtext ?
We use a selection listener on the scroll bar, a document changed listener and a key listener. This is wrapped in the ViewPortGuard. So far it did not even listen to mouse move events but when I tried to add it I found out that it's not sent. Note that the state is OK once DnD is finished.
That's right. During a drag-n-drop, you will not receive mouse move events. If you need to track the mouse movement during a drag, you must listen to the dragOver event.
OK, I take the bug back then. Filed SWT enhancement request to get a viewport listener (bug 204079).
>, you must listen to the dragOver event. Nice try ;-) There's no API to do that from outside: only the site that adds the drag source can do that and since there is no API to get the drag source (see also bug 173410), there's nothing Text can do here.
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. If you have further information on the current state of the bug, please add it. 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.
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.
