Sjoerd Op 't Land wrote:
> Of course I agree this would be a good addition. In the meanwhile, you could
> try to make your own workaround. The first step would be cathing the
> movements of the scrollwheel. I think we should try to do this first, and
> later (in further mails) think about how to let this work for the scrolling
> field. You could try cathing the rawKeyDown message.
If there could be a workaround, it would be great. However, it generates no
rawKeyDown message. I will try any other messages related to scrolling just
in case, but I don't think there will be any. The scrolling seems to work
with any typical Mac toolbox scrollbar, so it works in any application
except the ones with custom scrollbars.
I guess the mouse software figures out which scrollbar is closest, then
makes system calls directly, rather than sending click events or key events.
(Too bad the mouse software doesn't just send clicks--that would probably be
an even more global solution. It currently works in 90 percent or more of
applications I use, though.)
Curry Kenworthy
[EMAIL PROTECTED]
