Re: XKB Patch

keycode 255 is a special case. I found this:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6678061
We could just directly map keycode 255 to VK_OEM_4. Normally this keycode
isn't used.

How does it know that VK_OEM_4 has been pressed, if keycodes can't be used
as you say? Because XKB maintains a database of keycodes -> XKB keynames.
How many times do I have to repeat it? Yes, the keycode DOES change, it
isn't a constant, it will vary from one keyboard to another. THAT IS THE
WHOLE POINT OF USING XKB.

for instance, if I'm using digital_vndr/pc(pc_common) map from XKB, I get:

    VK_OEM_4    <84>

And now, if I look at digital_vndr/lk(lk_common):

    VK_OEM_4    <250>

And now, if I look at sun(type4):

    VK_OEM_4    <71>

Oh my God! What am I seeing? Different keycodes mapping to the same name?
Wasn't that the whole point of using XKB? Mapping different keycodes that
refer to the same key to a consistent naming system? Yes it is!

What the fuck is wrong with you guys? I'm here, submitting a damn patch
that's actually good, and you guys can't even manage to read it carefully
enough to understand what it is doing really. Instead, you insist on making
me repeat the same things over and over again, and when I think you finally
get it, no! You totally miss the point again. Keep your broken input system
if that is your wish, I'm so pissed at how bad this can be that I'm very
tempted to fork the damn project.

On Wed, May 20, 2009 at 6:39 AM, Peter Åstrand <[email protected]> wrote:

>
>  0x0000041d = Swedish keyboard layout
>>
>> scan code 0x1a corresponds to virtual key code VK_OEM_4
>>
>> Using a set of maps exported from the XKB database, a map of keycodes to
>> virtual key codes would be loaded.
>> 0x0000041d would be sent either automatically from auto-detection of
>> keyboard layout or from user specified
>> settings, in order to specify a Swedish keyboard layout. When the user
>> would press the key that is _consistently_
>> called VK_OEM_4, rdesktop would send scan code 0x1a, and the server would
>> then interpret 0x1a as being aring
>> according to the Swedish keyboard layout.
>>
>
> But how would rdesktop know that it should translate keycode 255 to
> VK_OEM_4? The answer is that it cannot, since there's no keycode with value
> 255 at all in the XKB database. Besides, the keycode might be 255 today, but
> 254 or something else tomorrow. Please try to understand that your approach
> of looking at the keycode does not work.
>
>
>
> Rgds, ---
> Peter Åstrand           ThinLinc Chief Developer
> Cendio AB               http://www.cendio.com
> Wallenbergs gata 4
> 583 30 Linköping        Phone: +46-13-21 46 00
>

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects

_______________________________________________
rdesktop-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rdesktop-devel