| Cursor and Scrollwheel Sync? [message #66685] |
Tue, 12 October 2004 13:40  |
Eclipse User |
|
|
|
Originally posted by: cdouglas.nospam.oz.net
Has anyone else noticed a discrepancy with the synchronization of the mouse
wheel and the displayed cursor when using VE?
I often use the "Java beans" view to find a component that I want to edit.
I select it, then switch to the "source" view in the VE editor. The cursor
is correctly placed in the bean I selected, but if I use the mouse wheel to
try and scroll the editor, it immediately jumps to the beginning of the
file.
I have to click in the source view first, then I can correctly use the
mouse wheel to scroll.
A search on "wheel" in VE bugs didn't reveal anything, but maybe it's
something in my setup.
Chas Douglass
|
|
|
|
| Re: Cursor and Scrollwheel Sync? [message #66852 is a reply to message #66707] |
Tue, 12 October 2004 17:34  |
| Eclipse User |
|
|
|
Originally posted by: cdouglas.nospam.oz.net
Rich Kulp <richkulp@us.NO_SPAM.ibm.com> wrote in
news:ckh67u$ch6$1@eclipse.org:
> I'm afraid I don't see that on my machine. Are you using split pane
> view or the view where design and source are on two different tabs?
>
> The only problem I found with the two different tabs is that clicking
> on the "source" tab at the bottom of the editor switchs to the source
> view,
> but it doesn't always activate the source view so the wheel actually
> doesn't work at all until I select into the source view.
I am using the tab view (sorry, should have mentioned that), and I don't
have the problem of it not activating.
They don't really seem like the same problem.
I use a Logitech cordless mouse, which interacts a little oddly with
some applications, and that's why I asked before just posting it as a
bug.
I just switched to the split-pane view and noticed that whenever you
select something in the design view, it was immediately and correctly
setting the source view.
I switched back to the tab-view and clicked on a control in the design
view. I switched to the source view and noticed that it was NOT in sync
-- it was showing a different spot in the file (don't remember exactly
where, now). When I clicked on the java bean the source view then
syncronized -- but the mouse wheel was NOT sync'd.
This is the behavior I am used to. Selecting a control in the design
view did NOT sync the source view -- I had to select the java bean to
make the source view sync. At this point the display would be sync'd
but not the mouse wheel.
Thus my standard operating procedure had become: select control in
design view which would sync java bean. Select java bean which would
sync source window (but with mouse wheel NOT sync'd).
After playing with this for a few minutes in order to careefully
document the behavior, it started working CORRECTLY. Now when I select
a control in the design view the source view is correctly sync'd and the
mouse wheel works correctly. I have no idea why.
If I come across what breaks it, I'll post a bug.
Chas Douglass
|
|
|
| Re: Cursor and Scrollwheel Sync? [message #601427 is a reply to message #66685] |
Tue, 12 October 2004 14:08 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
I'm afraid I don't see that on my machine. Are you using split pane view
or the view where design and source are on two different tabs?
The only problem I found with the two different tabs is that clicking on
the "source" tab at the bottom of the editor switchs to the source view,
but it doesn't always activate the source view so the wheel actually
doesn't work at all until I select into the source view.
--
Thanks,
Rich Kulp
|
|
|
| Re: Cursor and Scrollwheel Sync? [message #601441 is a reply to message #66707] |
Tue, 12 October 2004 17:34 |
| Eclipse User |
|
|
|
Rich Kulp <richkulp@us.NO_SPAM.ibm.com> wrote in
news:ckh67u$ch6$1@eclipse.org:
> I'm afraid I don't see that on my machine. Are you using split pane
> view or the view where design and source are on two different tabs?
>
> The only problem I found with the two different tabs is that clicking
> on the "source" tab at the bottom of the editor switchs to the source
> view,
> but it doesn't always activate the source view so the wheel actually
> doesn't work at all until I select into the source view.
I am using the tab view (sorry, should have mentioned that), and I don't
have the problem of it not activating.
They don't really seem like the same problem.
I use a Logitech cordless mouse, which interacts a little oddly with
some applications, and that's why I asked before just posting it as a
bug.
I just switched to the split-pane view and noticed that whenever you
select something in the design view, it was immediately and correctly
setting the source view.
I switched back to the tab-view and clicked on a control in the design
view. I switched to the source view and noticed that it was NOT in sync
-- it was showing a different spot in the file (don't remember exactly
where, now). When I clicked on the java bean the source view then
syncronized -- but the mouse wheel was NOT sync'd.
This is the behavior I am used to. Selecting a control in the design
view did NOT sync the source view -- I had to select the java bean to
make the source view sync. At this point the display would be sync'd
but not the mouse wheel.
Thus my standard operating procedure had become: select control in
design view which would sync java bean. Select java bean which would
sync source window (but with mouse wheel NOT sync'd).
After playing with this for a few minutes in order to careefully
document the behavior, it started working CORRECTLY. Now when I select
a control in the design view the source view is correctly sync'd and the
mouse wheel works correctly. I have no idea why.
If I come across what breaks it, I'll post a bug.
Chas Douglass
|
|
|
Powered by
FUDForum. Page generated in 0.05376 seconds
Home