Re: Using Memos in Windows

This is a standard 4GL problem. It should have been in the faq, but I can't remember to have seen it either. When you display a menu (execute the menu statement) it's allways done in the current window. Whenever you return to the menu so it has to be redisplayed (in case it was somehow removed) the 4GL runtime will allways automatically make the window the menu was displayed in the current window (as if current window is ... was executed). The runtime have to do this, so Informix can't change this behaviour. The solution is to open a special window for the menu only. A two line, 79 character wide window (some versions of 4GL have bugs so you can't use an 80 character wide window) at position 1,1 with no form should be used. Then you can easily switch between other windows via menu selections. You need do nothing special to the other windows as the menu window will only overlap the two first lines where the menu should be anyway. mrh@panix.com (Michael Hoffman) wrote: :Well I looked in the FAQ, but could fin no help. Therefore I turn to you. : :Background: I have a routing that needs two display screens. These screens :show information compiled from several Db tables, so I do not want to :constantly look up the data. These screens show a lot of data, and take up :the entire screen (except for the message and prompt lines). : :I want to open one window with the first screen. If the user requests the :second screen, I will open a second window, overlaying the first. This way :the user will be able to switch between screens quickly (I just have to :perform a "current window is" after determining which window is being shown. : :I am using the "menu" command to guide the users in their choices. : :Problem: When I open the second window, the information gets propogated into :the form correctly, but, as soon as that function ends, the first window :re-overlays the second. I thought that this was due to the Menu being located :on the first window. :I overcame that by putting the menu into a loop. Each time the user selects :a menu choice, I perform the routine and then "exit menu". This will cause a :loop and the Menu will reopen in the new current window. : :Well... that's not what happened. Instead, the first window continued to :overlay the second. The flags I set to help determine which window was active :showed that the second should be displayed. : :Question: Is there something in the Menu function that stops the current :window from being changed? Does anyone have any better ideas on how to handle :this situation? : :Thanks for any assistance. : :Michael Hoffman Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org