Re: get_fldbuf(variable-field-name)

David Williams <djw@smooth1.demon.co.uk> wrote: : Yes - I would also like windows (struct WINDOW *?), forms and : menus to be documented - how do I find which windows and forms I : have open? I can't. How do I find out which window is current? : Again I can't. I had a nasty error where a window was not closed : (this window had NO border hence was 'invisible'!) this meant that : a display.. AT.. failed. A glance at the code indicated that a : large window should have be open at that time. I had to track down : several layers of searches/results list to find the bug.... : : The eventual reply from informix was that they do not track which : form files are open!! The whole 4GL window management system is faulty from the beginning. It should have contained "define window" and "current window is" or something like that. "current window is" should then do an implisit open if the window wasn't allready opened. If you are conserned about memory usage of open windows there might be a "close window" as well. (Memory usage should no longer be a problem though.) We have simulated this (as described in a post a long time ago). That does away with most of the problems assosiated with windows that you describe. If the correct window isn't displayed we can simply call the "current_window" function at any time. We also have a separate function that returns the name of the current window. We often use this in functions that need to display a window temporarily and go back to the previous window when finished. If you want a stack of windows to make it easy to go back to the previous one that's also not hard to implement when such a current_window function is available. We have however not found any need of it. 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