Feature #6764
Updated by Greg Shah almost 2 years ago
For keyboard events there is a specific order on which 4GL is looking for the right trigger to fire:
- key label
- key function
- any-printable (if appropriate)
- any-key
It is using that order first for exact widget, then for the widget with @anywhere@ option and then it goes up the widget's parents tree and as last resort it looks for @anywhere@ without any widget (default handler).
- key label
- key function
- any-printable (if appropriate)
- any-key
It is using that order first for exact widget, then for the widget with @anywhere@ option and then it goes up the widget's parents tree and as last resort it looks for @anywhere@ without any widget (default handler).