When do 4GL windows become current automatically?

There is some undocumented (well, I haven't found it) trickery going on with 4GL windows. I wonder if anyone can shed any light on it. What seems to happen is that if a menu is active in a window and a menu COMMAND block does something that causes another window to become the current window, returning to the menu causes the window the menu is in to become current automatically, without the need for a CURRENT WINDOW statement. My question is: Is that right? And: does this happen in any other circumstances, eg with INPUT, DISPLAY or PROMPT statements? An observation: inspecting the C header files provided with 4GL shows that many of the user input structures (like MENU) do have knowledge of the window they are in. A reason for wanting to know: some of my code uses a C function which allows me to pop the current window off the top of the window stack, revealing the previously current window. This is essential for modular code but is not portable. (Why didn't Informix provide a HIDE CURRENT WINDOW statement?) If 4GL can be relied upon to do the work automatically I can be more portable. Thanks for your insights into the murky depths of 4GL. -- Peter Lancashire Information Systems Specialist, Bayer plc Eastern Way, Bury St Edmunds, Suffolk, IP32 7AH, UK Tel: +44-1635-562258, Fax: +44-1635-562281 Mail: Peter.Lancashire.PL1@bayer.co.uk --- My Internet plumbing does not allow me to mail and post news together. Sorry. All opinions are my own and not those of Bayer plc. --- Join Infuse, the UK Informix User Group at http://www.infuse.org.uk/