This section documents the ad hoc mechanism used by the Toolbox module to notify the Window module that a sub-menu is about to open (before delivery of a Wimp MenuWarning message), the necessity of this mechanism, and the way in which it has been extended to all object classes in Toolbox 1.86.
It also describes the method used to update Wimp sub-menu pointers when showing objects of the FontMenu, Menu and ColourMenu classes, the flaws in this system, and a more robust mechanism to replace it (which requires support from Menu 0.51).
Existing sub-menu warning mechanism
When the Toolbox module's post-filter for Wimp events catches a MenuWarning (&400C0) message (event code 17 or 18), it calls SWI Window_PreSubMenuShow and then re-sends the message to the client task (thus deferring it). The initial message is intercepted so that neither client nor object modules see it. When the MenuWarning message returns it can be distinguished by the fact that its 'your ref' field is now non-zero.
The reason for this SWI is to give the Window module a chance to hide any Window object that is showing transiently and more importantly raise a Window_HasBeenHidden event that will be delivered before the MenuWarning message. (When the latter is received by the Menu module it will show the object attached at that point in the menu tree, potentially causing an AboutToBeShown-type event.)
This not for the benefit of the Window module, since it can easily ensure that generates a Window_HasBeenHidden event for any existing transient Window object before showing another one. The real reason is to give those object classes implemented using an underlying Window object (e.g. SaveAs) a chance to raise their own events (e.g. SaveAs_DialogueCompleted) in response to Window_HasBeenHidden, before the sub-menu object is shown.
The Toolbox module also calls SWI Window_PreSubMenuShow before the relevant class SWI when showing an object as a sub-menu.
Window_PreSubMenuShow (SWI &828BD)
No registers significant.
On exit :
R0 = 0 All other registers preserved.
N.B. The SWI decoding table in the Window module does not include a proper name for this SWI, where it is simply 'Window_61'. This is for compatibility with earlier versions.
Need for wider sub-menu warning
The mechanism outlined above is exclusive to the Window module; other object class modules do not receive notification before a MenuWarning message is deferred. The requirement to be able to *deliver* a HasBeenHidden-type event before a MenuWarning message is specific to object classes on top of which other classes are implemented (and only Window falls into this category).
However, forewarning of MenuWarning messages is also required in order to deduce that objects of any class have been hidden when an alternative sub- menu is about to open (not currently implemented, but desirable). In this case the notification could be immediately before the MenuWarning message is passed around the class modules, but it is simplest to combine this with the more stringent requirements of the Window class.
Forewarning is required because there is no guarantee of the order in which filters are called for a Wimp message. For example if the Menu module's filter receives a MenuWarning message first then it will call SWI Toolbox_ShowObject to show any attached object, potentially raising an AboutToBeShown-type event. When the message arrives at another class module's filter, it will raise HasBeenHidden-type events if it believes any of its objects to be showing as a sub-menu.
It can be seen that the event ordering is wrong. Worse, if the object about to be shown and the object deduced to have been hidden are the same then the class module is likely to become confused.
The additional notification prior to calling the class SWI to show an object as sub-menu is redundant because SWI Window_PreSubMenuShow should already have been called on receipt of a MenuWarning message.
Sub-menu pointers in Wimp menu data structures
The Wimp interpretation of sub-menu pointers is as follows:
To stop sub-menus from disappearing when a menu tree is re-opened after an ADJUST-click selection we must ensure that the Wimp sub-menu pointer is valid for the selected menu entry on each level.
Currently the Wimp sub-menu pointer is only filled in after a submenu-show object attached to a menu entry has been auto-shown in response to a MenuWarning message. The value of R0 returned by SWI Toolbox_ShowObject (officially undefined, except in case of error) is implicitly treated as a Wimp window handle or pointer to a Wimp menu data structure. However this assumption is flawed since only the FontMenu, Menu and ColourMenu classes return a meaningful value in R0!
The Wimp sub-menu pointer is never filled in for objects shown as sub-menu by the client task (e.g. in response to a Menu_SubMenu event). This is because clients are not aware of the significance of the value of R0 returned by SWI Toolbox_ShowObject when showing certain object classes as sub-menu. Also they do not know the address of the Wimp data structure for the parent menu.
Finally, if a menu is re-built by a client task before being shown (e.g. upon receiving a Menu_AboutToBeShown event) then the Wimp sub-menu pointer will be invalidated if the base address of the Wimp menu data changes. The problem is that the sub-menu data pointer is returned immediately by the class SWI - before the object has actually been shown.
New service call
R0 = handle of client task R1 = &400C0 R3 = sub-reason code: 0 = Notification that a MenuWarning message has been deferred. 1 = Request to link a sub-menu into the current menu tree. Other values reserved Other registers depend upon the reason code (see below).
On exit :
All registers must be preserved.
This service call is used by the Toolbox module and class modules to implement mechanisms relating to opening sub-menus. It provides an early warning that a sub-menu is about to open (before Wimp message &400C0), and also carries requests to update Wimp sub-menu pointers (thus avoiding the need to poke private data structures).
R0,R1 as above R2 = pointer to menu state (as for Wimp_GetMenuState) R3 = 0 (a sub-menu is about to open)
On exit :
All registers must be preserved.
The Toolbox module circulates this service call with reason code 0 when it is about to defer a Wimp MenuWarning message (&400C0). It must never be claimed.
This notification may be used by class modules to mark as hidden any objects belonging to the specified task that were believed to be showing as a sub- menu and, if appropriate, generate HasBeenHidden-type events for them. If a module implements an object class that itself supports sub-menus (like 'Menu') then the Wimp menu state pointed to by R2 can be examined to ensure that objects are not assumed to have been hidden if they form part of the menu tree leading to the sub-menu arrow that is being traversed.
For compatibility with existing versions of the Window module the Toolbox module also calls SWI Window_PreSubMenuShow. However, new versions of Window will ignore this SWI in favour of the service call. Note also that the Toolbox module no longer calls this SWI before asking a class module to show an object as sub-menu.
R0,R1 as above R2 = pointer to Wimp data for sub-menu (or window handle) R3 = 1 (request to link a sub-menu into the current menu tree) R4 = Object ID of parent menu R5 = Component ID of parent menu entry
R1 = 0 if claiming service call Other registers must be preserved.
Class modules should raise this service call with reason code 1 to request that the Wimp data structure for a sub-menu (or the handle of a window to be shown as sub-menu) be linked to the Wimp data structure for its parent. For backward compatibility, if no parent object was specified by the client then this service call should not be raised and no error returned.
This reason code should be ignored by all class modules except those that implement objects that may have other Toolbox objects as sub-menus. Currently this includes only the Menu module, which responds by updating the relevant sub-menu pointer within the Wimp data structure for the parent Menu and claiming the service call. It must not be claimed if the parent object belongs to a different class, or the parent menu entry has no sub-menu arrow.
If this service call returns unclaimed then none of the class modules were able to link the sub-menu onto the parent object and component specified by the client. The class module that is trying to show one of its objects as a sub-menu should respond by hiding the object (if it had already been shown) and returning an error message of the form "Component, 0x01234567 of object, 0x89abcdef, is unsuitable parent for submenu." This should aid programmers during application development.
This documentation is copyright 3QD Developments Ltd 2013 and may not be reproduced or published in any form without the copyright holders permission. RISC OS is subject to continuous development and improvement as such all information is reproduced by 3QD Developments Ltd in good faith and is believed to be correct at the time of publication E&OE. 3QD Developments Ltd cannot accept any liability for any loss or damage arising from the use of any information provided as part of the RISC OS Documentation.
HTML document version 1.03 3rd November 2015