Re: [poedit-users] mouse / touchpad scroll does not work in translation window (Win32)

Hi,

[merging reply to your two emails in one]

On Mon, 2009-02-02 at 12:51 +0200, Cristian Secară wrote:
> > > For some reason, the mouse or touchpad scrolling does not work
> > > (anymore) in the translation window, 
> > This should be obvious, but sadly still isn't for many people: you
> > really do need to define "anymore" precisely if you want to get any
> > help. In other words, you do have to, precisely and correctly,
> > identify what changed. 
> 
> Ok, my message was poorly edited.
> Does not work anymore = after (clean) Windows XP reinstall.

Yes, I understood that. What I meant was that this was useless, because
it didn't tell me *anything* about what changed: I don't know the state
of your system either before or after the change, and knowing only that
there was *a* change is worthless.

> I remember it worked because now I am surprised it doesn't / the
> mouse driver was/is the same / the physical mouse aes/is the same /
> Poedit was/is the same.

Well, clearly there is *some* difference, otherwise you wouldn't get
different behavior, would you?

> No, *WRONG*: it has to do with "Always change focus to text input
> field" option. And I can toggle the behaviour of the mouse scrolling
> that way (window must be closed and then reopened for that checkbox to
> affect the scrolling).

This confirms my suspicion that the mouse driver (or something else
installed) is translating mouse wheel actions into PgUp/PgDown key
presses. Very old drivers used to do that back when the wheels were
introduced and operating systems didn't support them natively. That is
not the case for years, though, and any self-respecting app now handles
the wheel natively.

You can verify this yourself: if you put very long multiline text (that
forces the translation text entry to be vertically scrollable) into
translation field, scrollwheel will scroll this instead of the list
control. And using the wheel while holding Ctrl will scroll the list.

This also means that you *don't* have the same Poedit version and mouse
driver/software same as before and configured the same. Either you had
Poedit configured to not autofocus translation field, or had the
wheel-to-PgUp/PgDown translation disabled in the driver. 

> Is this a normal / desired behaviour ?

Let's say it is expected (with drivers translating mousewheel events
into PgUp/PgDown). Clearly, it is not desired, but there's no way Poedit
can differentiate between "real" PgUp/PgDown keys and the mousewheel if
the driver chooses to be deceptive.

Vaclav

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com

_______________________________________________
Poedit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/poedit-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkmHZn4ACgkQxDYa/UZSZMllRwCfftpp3ISws6kj1Pk6Pv9Sa9M8
SyoAnA0s+NM/MWv7ZEiVm/ZVPzAlVrbB
=aO1/
-----END PGP SIGNATURE-----