ThinkPad MouseWheel Simulation does not work

Hello,

using my thinkpad laptop i have to use the trackpoint and a special key for simulating the mousewheel in order to scroll up&down.

This does not work with IDEA.

Thanks in advance, Leif

8 comments
Comment actions Permalink

Hanack wrote:

Hello,

using my thinkpad laptop i have to use the trackpoint and a special key for simulating the mousewheel in order to scroll up&down.

This does not work with IDEA.

Thanks in advance, Leif


Please post this bug to SUN (JVM doesn't support your hardware)

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

0
Comment actions Permalink

It's more a problem of IBM. They have mixed something together here and named it mousewheel simulation. There are other non-Java applications that don't work all that good with it.

I have a T20 and I bought myself a mouse only because I couldn't stand not to have a real mousewheel anymore. BTW: In doing so you have the advantage of an available middle mousebutton which is very useful in IDEA.

0
Comment actions Permalink

What do you use your middle button for in IDEA?

0
Comment actions Permalink

Keith Lea wrote:

What do you use your middle button for in IDEA?

First you can close editor tabs by middle button. The second you can map
any action to mouse stroke. For example middle mouse button can show
quick Javadoc or go to declaration of the symbol. It's very useful.

Regards,
Vladimir Kondratyev
_____________________
JetBrains

0
Comment actions Permalink

If it is a IBM problem, why some applications will work with that key and some won't? What do the applications where it works other then the applications like IDEA where is doesn't work?

Is it a general bug with java applications only?

If so, it could fixed by SUN ? :)

If not, should i contact IBM ?

Question over question. Give me some light:-)

0
Comment actions Permalink

It's a problem that all Java applications suffer. The mousewheel scrolling
simulation on ThinkPads uses some proprietary native software which IBM does
not publish an interface for; it works for Windows apps but not for Java
apps. So the only people that would be able to fix it are IBM (or some
clever person with a decompiler and a flagrant disregard for EULAs).

I remember a while back someone tried to get it working with JBuilder. The
best solution they could find was to pop up a small native window under the
mouse cursor and catch the scroll events on it. It sort of worked but wasn't
very convenient. I don't know if that's been developed any further since -
it's been a LONG time since I used JBuilder :) - but that was the closest
thing I'd heard of.

So I guess the answer is to ask IBM to sort it out. Either get them to use
the standard mousewheel events for it, publish an interface for their
software, or even release a Java library for it. Actually, they may have
done either or both of the last two without me finding out. If anyone knows
anything more about this, please let me know!

Vil. (who uses a mouse with his ThinkPad...)


Hanack wrote:

If it is a IBM problem, why some applications will work with that key and some won't? What do the applications where it works other then the applications like IDEA where is doesn't work?


Is it a general bug with java applications only?

If so, it could fixed by SUN ? :)

If not, should i contact IBM ?

Question over question. Give me some light:-)


--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

Disclaimer

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

0
Comment actions Permalink

Another very useful feature is that you can click on a Class name, variable name or a method call and get instantly transfered to its declaration.

0
Comment actions Permalink

I don't really know how they made there mousewheel simulation, but I surmise that it works this way:
When you are in mousewheel simulation mode and press the track point in one or another direction, the driver tries to find the scrollbar of the area the cursor is in. When a scrollbar is found clicks on the up and down buttons are found. The probably look for objects with specific class ids here.
In Java programms this cannot work because the needed objects won't be found. So the mousewheel simulation does not see the java scrollbars though you as the user see them clearly.
The normal mouse wheels on Logitech, Microsoft etc. mice trigger some system function for mouse wheel support.

0

Please sign in to leave a comment.