nanogui: Improved keyboard event handler and mouse motion event handler for flnx
Subject:
Re: Improved keyboard event handler and mouse motion event handler for flnx
From:
"Greg Haerr" ####@####.####
Date:
27 Nov 2000 18:41:08 -0000
Message-Id: <06e301c058a1$c5c9f5a0$15320cd0@gregh>
Over the weekend I have completed a major keyboard design for
Microwindows, and have written scancode drivers for framebuffer
and X11. With this new design, there is no need or desire for the
escape-sequence processing that was previously required.
Instead, the new design always returns a 16-bit unicode value
for all keystrokes, press and release. The function, arrow and
special keys are placed in the UC16 private use area so there's
no overlap with other glyphs. In addition, the lower 256 codes
are mapped to latin-1. This has necessitated some API
changes with the GR_EVENT_KEYSTROKE as well as
GrInjectKeyboardEvent.
We are working on FLNX changes to be completly compatible
with this version, which will be released as 0.89pre7.
In order to fully test the keyboard, I have ported Doom! to
Microwindows, and it runs great.
These changes should correct all your keyboard issues with
Microwindows. The Century folks have fixed FLNX with better
scrollbar handling, including double-buffered output for ViewML,
for instance.
Regards,
Greg
----- Original Message -----
From: mateng
To: ####@####.####
Cc: ####@####.####
Sent: Sunday, November 26, 2000 6:39 PM
Subject: Improved keyboard event handler and mouse motion event handler for flnx
Hi Greg and others,
We are now working with microwindows-0.89pre5 and flnx-0.14.
Thank you for your great work that many problems were solved in these two newest released version.
But keyboard events processor is still incomplete and needs more work to be done. When press some special key(such as F10), a sequence of key press events is generated by nano-X. If we use a Fl_Input widget, it will result in a string as "[21~".
I did some work to solve this problem. All work is done in the flnx source file <Fl_x.cxx>. New added or modified code is marked with "MaTeng".
It is a simple but unperfect way. I just handle the keyboard press event. When meet special key, I record its string and match it in a key-map array, then forward. Now it seems work well.
I met another problem. When use framebuffer, the demo program scroll.cxx seems to be very inefficent while draging the scrollbar. The refresh rate is too slow. I made some modification to the method fl_wait() to filter the mouse motion event. Now, it looks better but still can not meet our needs. How can I solve this problem?
The last problem is after pressing CTRL_C in flnx demo program editor, I can not get keypress event any more from the nano-X server. I had to stop nano-X and restart it.
Since I am not familiar with nano-X, I think my modification is incomplete and maybe there is some other better way. Your advice will be very important and useful to me.
By the way, I am glad to commit my modification and wish it will do you good.
The attachment is a winzip archive file.
Best regards!
####@####.####
P.R.China
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####
