Lars, the attached patch to xforms' forms.c cures these two bugs in xforms
handling of key events.
o xforms should swallow null keyevents. They occur during composition of
multi-byte chars. The problem was reported and a solution proposed here:
o xforms should pass FL_KEYRELEASE events to the
Angus Leeming [EMAIL PROTECTED] writes:
| Lars, the attached patch to xforms' forms.c cures these two bugs in xforms
| handling of key events.
| o xforms should swallow null keyevents. They occur during composition of
| multi-byte chars. The problem was reported and a solution proposed here:
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 2:19 pm, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| Lars, the attached patch to xforms' forms.c cures these two bugs in
| xforms handling of key events.
|
| o xforms should swallow null keyevents.
On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
Look at the time difference between the KEYRELEASE and KEYPRESS
events.
|
| Why? Ie, I don't understand what you're attempting to do with this code.
Just do it
KeyRelease event, serial 27, synthetic NO, window 0x4a1,
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
Look at the time difference between the KEYRELEASE and KEYPRESS
events.
|
| Why? Ie, I don't understand what you're attempting to do with this code.
Just do it
KeyRelease event,
On Tuesday 10 December 2002 3:01 pm, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
Look at the time difference between the KEYRELEASE and KEYPRESS
events.
|
| Why? Ie, I don't understand what you're
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 3:01 pm, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
Look at the time difference between the KEYRELEASE and KEYPRESS
events.
|
On Tuesday 10 December 2002 3:26 pm, Lars Gullik Bjønnes wrote:
What we do not want is cursors, auto-repeat chars that just continue
to go after the key has been released. so we use xsync for this.
The problem is to know when to run this xsync, we want to loose as few
xevents as possible.
|
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 3:26 pm, Lars Gullik Bjønnes wrote:
What we do not want is cursors, auto-repeat chars that just continue
to go after the key has been released. so we use xsync for this.
The problem is to know when to run this xsync, we want
On Tuesday 10 December 2002 4:18 pm, Lars Gullik Bjønnes wrote:
| Ok. I'm getting there. You want code like this:
Sorry for leading you on a leash like that...
As we progressed I began feeling a bit queasy...it might not be som
clever after all.
..but yes, something similar to this was
On Tuesday 10 December 2002 16:34, Angus Leeming wrote:
Ie, can you envisage ANY situations where one
might want to pass auto-repeat events to the widgets?
When Lars finally commit his insetgame that he has in one of the other trees
we develops. (?) ;-)
That would be uber cool. ::-)
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 4:18 pm, Lars Gullik Bjønnes wrote:
| Ok. I'm getting there. You want code like this:
Sorry for leading you on a leash like that...
As we progressed I began feeling a bit queasy...it might not be som
clever after all.
José Matos [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 16:34, Angus Leeming wrote:
Ie, can you envisage ANY situations where one
might want to pass auto-repeat events to the widgets?
| When Lars finally commit his insetgame that he has in one of the
| other trees we develops.
Lars, the attached patch to xforms' forms.c cures these two bugs in xforms
handling of key events.
o xforms should swallow null keyevents. They occur during composition of
multi-byte chars. The problem was reported and a solution proposed here:
o xforms should pass FL_KEYRELEASE events to the
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars, the attached patch to xforms' forms.c cures these two bugs in xforms
| handling of key events.
>
| o xforms should swallow null keyevents. They occur during composition of
| multi-byte chars. The problem was reported and a solution proposed
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Tuesday 10 December 2002 2:19 pm, Lars Gullik Bjønnes wrote:
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>> | Lars, the attached patch to xforms' forms.c cures these two bugs in
>> | xforms handling of key events.
>> |
>> | o xforms should swallow
On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
> >> Look at the time difference between the KEYRELEASE and KEYPRESS
> >> events.
> |
> | Why? Ie, I don't understand what you're attempting to do with this code.
>
> Just do it
>
> KeyRelease event, serial 27, synthetic NO,
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
>> >> Look at the time difference between the KEYRELEASE and KEYPRESS
>> >> events.
>> |
>> | Why? Ie, I don't understand what you're attempting to do with this code.
>>
>> Just do it
On Tuesday 10 December 2002 3:01 pm, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
> >> >> Look at the time difference between the KEYRELEASE and KEYPRESS
> >> >> events.
> >> |
> >> | Why? Ie, I don't
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Tuesday 10 December 2002 3:01 pm, Lars Gullik Bjønnes wrote:
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>> | On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
>> >> >> Look at the time difference between the KEYRELEASE and KEYPRESS
>>
On Tuesday 10 December 2002 3:26 pm, Lars Gullik Bjønnes wrote:
> What we do not want is cursors, auto-repeat chars that just continue
> to go after the key has been released. so we use xsync for this.
> The problem is to know when to run this xsync, we want to loose as few
> xevents as possible.
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Tuesday 10 December 2002 3:26 pm, Lars Gullik Bjønnes wrote:
>> What we do not want is cursors, auto-repeat chars that just continue
>> to go after the key has been released. so we use xsync for this.
>> The problem is to know when to run this xsync,
On Tuesday 10 December 2002 4:18 pm, Lars Gullik Bjønnes wrote:
> | Ok. I'm getting there. You want code like this:
>
> Sorry for leading you on a leash like that...
>
> As we progressed I began feeling a bit queasy...it might not be som
> clever after all.
>
> ..but yes, something similar to this
On Tuesday 10 December 2002 16:34, Angus Leeming wrote:
> Ie, can you envisage ANY situations where one
> might want to pass auto-repeat events to the widgets?
When Lars finally commit his insetgame that he has in one of the other trees
we develops. (?) ;-)
That would be uber cool. ::-)
>
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Tuesday 10 December 2002 4:18 pm, Lars Gullik Bjønnes wrote:
>> | Ok. I'm getting there. You want code like this:
>>
>> Sorry for leading you on a leash like that...
>>
>> As we progressed I began feeling a bit queasy...it might not be som
>> clever
José Matos <[EMAIL PROTECTED]> writes:
| On Tuesday 10 December 2002 16:34, Angus Leeming wrote:
>> Ie, can you envisage ANY situations where one
>> might want to pass auto-repeat events to the widgets?
>
| When Lars finally commit his insetgame that he has in one of the
| other trees we
26 matches
Mail list logo
