[Bug 1181] Keyboard translation broken: uses raw keycodes

Tom Spear speeddymon at gmail.com
Fri Mar 31 17:16:07 CST 2006

On 3/31/06, Augusto Arcoverde da Rocha <agarobr.listas at gmail.com> wrote:
> > On 3/31/06, Tom Spear <speeddymon at gmail.com> wrote:
> [cut]
> > I think that rewriting the keyboard code in this way is a very good
> thing,
> > and will be more than happy to help coordinate testing of it, although I
> > can't test any myself.  Rewriting the code should allow us to close many
> of
> > the keyboard related bugs in bugzilla, which will be a big BIG plus in
> my
> > book.
> >
> > Like I said, if you want me to, I will coordinate testing of new
> code.  I'll
> > start a new thread called keyboard rewrite and ask for volunteers with
> > different keyboard layouts to reply to that thread to test new
> code.  I'm
> > also going to create an offspring of the main wiki page for this
> project,
> > once given confirmation that you will do the rewrite.
> >
> > Tom
> Tom,
> "I offer a hand and you grab my arm?" ;-)
> (in Portuguese this is a funny quote...)

Thats pretty funny even in english!  lol
Sorry if that is what I did.

I just said that I *started thinking* in rewriting the code, and I am
> still thinking... Nevertheless, I'm not an experience C programmer --
> like many programmers in this list -- and I don't know the X server
> API and what vkey, keycode and keyscan mean until the last month when
> I tried to solve bug 2400 ("Issue with Delete when NumLock active").

Yes I understand, which is why I said even if you can only contribute a
little bit.  I'm not expecting a complete rewrite overnight..  Heck, even
Alexandre's window management rewrite has been ongoing for several months if
not over the last year.  I just figured that if you could do some of it,
then other developers with more experience might take notice and start
submitting patches, or might offer more tips on what is right and what needs
to be changed about your patches..

I have looked at the rdesktop code and found an approach completely
> different of my ideas, a sign that I may be wrong (and probably am)
> about "keysym2vkey". :-/

I see.  Personally I think even if the approach is wrong, we could see the
differences between it and our code and figure out what to do to make ours
work like theirs does (100% all the time) without using the same approach
(hope that makes sense)..

If Wine Devel Community has no problem in putting this task on new
> hands -- even though I can dedicate full time to that task -- I also
> haven't got a problem! 8D

I'm sure that others will step up to the plate shortly.  It has only been a
couple of hours since I posted.

Hopefully nobody forces me to make this a call to arms for developers! ;-D

I will get very happy if some more programmers offer some *arms* (or
> some comments) to help me. :-)
> But... I have a request... ;-)
> Please apply the patch that I have sent to fix bug 2400 [1], because
> the <del> + <comma> key bug is too annoying ... and, at least, the
> problem is reduced until we can deliver a new keyboard driver.

Alexandre?  Can you comment please?

> [1] http://www.winehq.org/pipermail/wine-patches/2006-March/024891.html

Thanks so much guys

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-devel/attachments/20060331/6a948580/attachment.htm

More information about the wine-devel mailing list