RE: MI : window size dependency(2)
Jaques GISers This one has bugged me a lot for quite a while would also be interested in anyones workarounds (hopefully not delving into the Win API too much). It's most annoying when you usually have your Mapper maximised and just stop to browse some records/queries/graphs and then got lost in the deluge of maximised windows. Nothing critical just inefficient - is it on the wish-list? Mike ___ Mike Eden Senior Technical Services Manager RSK Environment (UK) Ltd. +44 (0)1928 726006 mailto:[EMAIL PROTECTED] -Original Message- From: Jacques Paris [mailto:[EMAIL PROTECTED]] Sent: 15 July 1999 17:20 To: [EMAIL PROTECTED] Subject: MI : window size dependency(2) Thanks to all that have answer me, but because I was not clear enough, most answers were off target. The situation is very simple. When in MapInfo (I am not talking about programming) if one chooses to maximize a window and then uses the window menu item to go through all the open windows, they are all displayed MAXIMIZED. If he chooses minimize or intermediate size, all the windows take that state (icons or as defined previously to MAX for each one). However, if a table of the pile is closed, nothing changes, even if it was the one that was used for the original MAX. In a MapBasic application, I got a similar situation. The program generates a table MAX then closes it. I had a MBwindow open at the time; after the job, the BMW remained MAX. There may be ways to correct that with some programming (I do not even know if it is worth the effort) in the case of an MB application, but I am concern by the behaviour in the MI context. Is that a "works as designed"? Can it be prevented? I am rather late at coming aware of it; I was never bugged by it until this week, and it had been there all that time (I checked back to 4.5 for fun!) Thanks again Jacques Paris e-mail [EMAIL PROTECTED] alternate [EMAIL PROTECTED] gis activity (MapInfo mainly) http://www.total.net/~rparis/gisproducts.htm -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
RE: MI : window size dependency(2)
Thanks to Trey Pattillo [[EMAIL PROTECTED]], I understand now that the global maximization of windows open in MI is more a Windows feature than anything else. I quote his explanation : "This is the behavior of the Multiple Document Interface [child windows] that can be duplicated by any application that allows opening multiple documents, such as M$ Word etc." This would explain other behaviours like the "de"maximization of a mapper when you open a browser. When working directly in the MI window, the only way to regain original window sizes is to click on the "intermediate" icon at the upper right corner. One click is enough, no matter how many windows are open. In MapBasic, the way I found is first to check if any window is open if numwindows()0 then restore the front window to its non-max size, all the other windows should follow set window frontwindow() restore I hope that the subject is now closed, but who knows? Thanks to contributors and commentators. Jacques Paris e-mail[EMAIL PROTECTED] alternate [EMAIL PROTECTED] gis activity (MapInfo mainly) http://www.total.net/~rparis/gisproducts.htm -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI : window size dependency(2)
Thanks to all that have answer me, but because I was not clear enough, most answers were off target. The situation is very simple. When in MapInfo (I am not talking about programming) if one chooses to maximize a window and then uses the window menu item to go through all the open windows, they are all displayed MAXIMIZED. If he chooses minimize or intermediate size, all the windows take that state (icons or as defined previously to MAX for each one). However, if a table of the pile is closed, nothing changes, even if it was the one that was used for the original MAX. In a MapBasic application, I got a similar situation. The program generates a table MAX then closes it. I had a MBwindow open at the time; after the job, the BMW remained MAX. There may be ways to correct that with some programming (I do not even know if it is worth the effort) in the case of an MB application, but I am concern by the behaviour in the MI context. Is that a works as designed? Can it be prevented? I am rather late at coming aware of it; I was never bugged by it until this week, and it had been there all that time (I checked back to 4.5 for fun!) Thanks again Jacques Parise-mail [EMAIL PROTECTED] alternate [EMAIL PROTECTED] gis activity (MapInfo mainly) http://www.total.net/~rparis/gisproducts.htm
