comp.lang.idl-pvwave archive: archive » Keyboard input from widgets

Home » Public Forums » archive » Keyboard input from widgets

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Keyboard input from widgets [message #29414 is a reply to message #29346]

Fri, 15 February 2002 01:43

alt
Messages: 28
Registered: August 2001

Junior Member

I use for this purpose widget_text trick
(it's visible because there are situations when focus nevertheless
become lost) and TVCRS to position cursor on widget_draw. The only
inconvenience is widget_text does not catch arrow keys and one should
use some text keys.
I would recommend "ASDW" keys - standard direction keys in games
(a pair hours of Quake and you'll forget about arrows :-))

Probably it can be overcome if use widget_table instead of
widget_text. Table cell selection events catch arrow keys and edit
cell mode catch text keys. But I didn't check it.

Altyntsev Dmitriy,
Remote Sensing Center
Irkutsk, Russia
http://ckm.iszf.irk.ru

to_oleg@mail.ru (Oleg Kornilov) wrote in message news:<820c611d.0202130822.7806e3dc@posting.google.com>...
> Hi,
> I have draw widget and I use mouse events in it (cursor moving and
> buttons). I need to know also what key on keyboard was pressed (for
> example, for precision moving of mouse cursor). Problem that
> base_widget does't generate events for keyboard and draw_widget
> switches into stdin (IDL command line). Probably I can use timer
> events and get_kbrd() to check keyboard buffer.
> Is there another way ?
> Thank you.

Report message to a moderator

[Message index]

		Keyboard input from widgets By: to_oleg on Wed, 13 February 2002 08:22
		Re: Keyboard input from widgets By: alt on Fri, 15 February 2002 01:43
		Re: Keyboard input from widgets By: JD Smith on Wed, 20 February 2002 19:42

Previous Topic:	Variance in sub-sections?
Next Topic:	Does anybody know an 'undocumented IDL feature' that does this

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 05:47:35 PDT 2025

Total time taken to generate the page: 0.72429 seconds