X
xander
Guest
I want to add some special behaviour to an editor widget when the user is pressing the tab key.
The problem is as soon as the any-key event trigger is applied to an editor widget the default behaviour like keyboard cursor keys and text replacement is lost.
Is there any way to keep the default behaviour or another way to react to the tab key? At the moment I have a simple event trigger like this
on any-key of gcContentEditor in frame F-Main
do:
if lastkey = keycode('TAB':U) then do:
/* do some stuff */
return no-apply.
end.
/* TODO: simulate default behaviour? */
end.
I've found the article Triggers and low-level keyboard events in the official Progress documentation, but it doesn't help with my problem I guess.
Continue reading...
The problem is as soon as the any-key event trigger is applied to an editor widget the default behaviour like keyboard cursor keys and text replacement is lost.
Is there any way to keep the default behaviour or another way to react to the tab key? At the moment I have a simple event trigger like this
on any-key of gcContentEditor in frame F-Main
do:
if lastkey = keycode('TAB':U) then do:
/* do some stuff */
return no-apply.
end.
/* TODO: simulate default behaviour? */
end.
I've found the article Triggers and low-level keyboard events in the official Progress documentation, but it doesn't help with my problem I guess.
Continue reading...