Dmitry Timoshkov wrote:
Sylvain Petreolle [EMAIL PROTECTED] wrote:
At least, the detection mismatches should be fixed/explained IMHO.
I think that this topic was explained many times already.
Anyway, here is yet another attempt.
1. Keyboard detection code was introduced in order to make
Shachar Shemesh [EMAIL PROTECTED] wrote:
5. In the future, windows keyboard language APIs will need to be
handled. For those to work, we must be aware of which is the current
keyboard.
This one is just a missing functionality (support for keyboard layouts),
and has nothing to do with
Dmitry Timoshkov wrote:
Shachar Shemesh [EMAIL PROTECTED] wrote:
The reason I listed it here is because in order for Wine to know what
language the current keyboard is, it will also need to know what's the
current keyboard.
I have thought of two ways for Wine to do that - either it checks
[EMAIL PROTECTED] wrote:
I sent a patch that looks like yours and it was simply refused !
I wasn't the fisrt...
Because there were no explanations provided except that warning
message. If keyboard input works for you, there is no need to
send a patch.
--
Dmitry.
At least, the detection mismatches should be fixed/explained IMHO.
As it was said already, we will need at some point to comment out
that
FIXME in keyboard.c. If the keyboard input works for you, then I
don't
see what needs to be fixed.
Hi Jerome,
It seems your patch includes a currency sign 'ยค' instead of the Euro :
Altgr-E and Altgr-$ look the same (0xA4.)
Please use the unified format when sending patches.
=
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
ICQ #170597259
Say NO to software patents
Dites
