[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
Re: numlock sync patch
it doesn't seem as if the server send indications of this information, not by
itself anyway, perhaps it's possible to request it?
Should I include the patch anyway, until some better way exists?
what do you think?
//
peter
Peter Bystrom wrote:
> hmm... thanks for the patch, but I will wait awhile with including it....
> I didn't think of this problem earlier.... :\
>
> best regards,
>
> peter
>
> Ben McKeegan wrote:
>
> > On Wed, 10 Jan 2001, Norbert Federa wrote:
> >
> > > the attached patch is based on unified-patch 18-9.
> > > i've done this via xkb's XkbGetIndicatorState function
> > > if the states indicate that numlock is on then do a
> > > rdp_send_input witch the numlock scancode ...
> >
> > ...which unfortunately will do the exact opposite of what you want if you
> > happen to be reconnecting to a disconnected session in which you had
> > numlock turned on! And it doesn't help when programs toggle the status
> > for you.
> >
> > Does your patch do the caps lock status as well? (Caps lock suffers
> > exactly the same problem.)
> >
> > What we need is some way to check the key lock status on the
> > terminal server - does anybody know how? The T.128 document is not any
> > help in this area.
> >
> > Ben.
> >
> > / Ben McKeegan, I.T. Manager \
> > \ Fitzwilliam College, University of Cambridge, UK. /