Frequently Asked Questions

1. Keyboard events with keys 1, 2, 3, 4, 5, 6 from the numerical pad are not detected by WinDom. Is a bug ?

2. How control the redraw message, i.e. how disable the WinDom feature which clip and call the redraw function on each element of the AES rectangle list ?

1. Keyboard events with keys 1, 2, 3, 4, 5, 6 from the numerical pad are not detected by WinDom. Is a bug ?

   No, it is not a bug. It is probably due the application uses a menu created by Interface. When Interface creates a new, it gives to the accessory items in the menu the following names : Accessory 1, Accessory 2, ... Unfortunately, EvntWindom() - which handles automatically the menu shortcuts - interpretes the words 1, 2, 3 of accessory items as shortcut. It is why there are not interpreted as keybord event but as menu event. The solution is to give an another name to this accessory items. For example, Accessory_1. (Thanx to Zerkman for the solution).

2. How control the redraw message, i.e. how disable the WinDom feature which clip and call the redraw function on each element of the AES rectangle list ?

   You have to bind the WM_PREREDRAW event instead of the WM_REDRAW event. You should remove the standard redraw function binded to WM_REDRAW (with EventDelete()).