fs@uwasa.fi (Filip Sawicki LAKE) (06/25/90)
Article <EVAN.90Jun25165742@manikin.cs.rmit.OZ.AU>: > 1) Popup a menu using button 1, even over the command widget, not > allowing it to be selected using the same button. As I understand it, > this should not be happening over the command widget. > > 2) Popup a menu using button 2 everywhere except over the command > widget, but none of the menu items can be selected. Yup, this is the most annoying and brain-damaged problem with R4 I've ever found. I hope someone from Consortium will explain not only the reason it works like that, but also WHY it was decided so. In general, problems can be specified as follows: ad 1) Children ALWAYS (!!!) inherit parent's translations. It may be OK, but it seems to be hard-coded, and even the following algorithm doesn't work -- though it should: * save child's translations * install translations in the parent * restore saved child's translations Effect: parent's translations STILL override those of a child. Simply it looks like: parent's translations == parent's accelerators within children ad 2) (It has been already discussed here) Menus refuse to work if they are invoked by the callback from the widget which child has installed similar translations. Overall effect is that, for example, if you use BTN1 to popup menu from the Form containing TextWidget, either this menu is popped up also in the TextWidget (making mouse useless), or popping works correctly, but no item is selectable. And, dear Consortium explainer, don't even try to suggest me using Shift | Ctrl | Meta <BTN1> in the example above! fi.