I had a similar thing happen a while ago.
It is caused because of something like this:
When a key event happens, there is a key value associated with the event.
BUT the WAIT allows the next key event to happen before the first key event
actually finishes and exits the SUB for that key value
So
the
Ken Thornton-Smith ha scritto:
> I'm entering numbers from an RFID tag reader into a text box.
> A keypress event here opens another text box and moves cursor focus.
>
> Obviously, the first character opens the second textbox and the rather
> slow usb puts the remaining characters in the second
I'm entering numbers from an RFID tag reader into a text box.
A keypress event here opens another text box and moves cursor focus.
Obviously, the first character opens the second textbox and the rather
slow usb puts the remaining characters in the second box.
Being lazy, instead of looking for
Le jeudi 04 juin 2009 17:20:01 Leonardo Miliani, vous avez écrit :
> Laurent Carlier ha scritto:
> > Le lundi 01 juin 2009 22:28:26 Leonardo Miliani, vous avez écrit :
> >> I got this error:
> >>
> >> (cd .libs && rm -f gb.db.sqlite3.so.0 && ln -s gb.db.sqlite3.so.0.0.0
> >> gb.db.sqlite3.so.0)
> >
Laurent Carlier ha scritto:
> Le lundi 01 juin 2009 22:28:26 Leonardo Miliani, vous avez écrit :
>> I got this error:
>>
>> (cd .libs && rm -f gb.db.sqlite3.so.0 && ln -s gb.db.sqlite3.so.0.0.0
>> gb.db.sqlite3.so.0)
>> (cd .libs && rm -f gb.db.sqlite3.so && ln -s gb.db.sqlite3.so.0.0.0
>> gb.db.sq
Laurent Carlier ha scritto:
> Le lundi 01 juin 2009 22:28:26 Leonardo Miliani, vous avez écrit :
>> I got this error:
>>
>> (cd .libs && rm -f gb.db.sqlite3.so.0 && ln -s gb.db.sqlite3.so.0.0.0
>> gb.db.sqlite3.so.0)
>> (cd .libs && rm -f gb.db.sqlite3.so && ln -s gb.db.sqlite3.so.0.0.0
>> gb.db.sq
Benoit,
Maybe the problem is an GTK Libraries installed at opensuse/fedora by
default (or gtk gambas package), because I've tryed to run the app in
other ubuntu 32/64 versions and allways run fine (8.04, 8.10, 9.04). I
thing this because you said than lostfocus event was fixed at revision
#1996 an
