What I don't understand is killing me (OpenInsight 32-bit Specific)
At 07 AUG 2003 09:48:55AM Gerald Lovel wrote:
I once watched my year old child crash 20 DOS computers in a line in less than 5 minutes. Oddly, she could never crash a Macintosh.
Being new to OI, there is a certain amount of natural experimentation trying to get things to work, and much of it probably falls within the description above.
1) Design MDI frames MDI_A and MDI_B. Start MDI_A. Issue the command,
Start_MDIChild( "MDI_B","MDI_A","","","",""). What happens?
2) Set the visible property of frame MDI_A to false. Start the frame, and in its create event, include the following code:
Window=Start_MDIChild("MDI_CHILD",@Window,"","","","")
Set_Property( @Window, "VISIBLE", True$ )
Reverse the sequence of these statements to produce a more-expected result.
3) A window designed with title unchecked opens without a title through Create_Dialog. Opening with Start_MDIChild adds a title bar.
4) We won't talk about the "always on top" OI dialog which has escaped its MDI frame and is floating over this Terminal Services session as I write this, title-less, unrelocatable, in the way, but DEFINITELY ON TOP.
The doctor said, "If it hurts when you do that, then don't do it!" Unfortunately, I have little guidance about what will hurt or help in advance. But then, maybe MicroSoft lacked guidance with DOS (and Windows). Please respond only if this amuses you.
At 08 AUG 2003 07:19AM Tim Marler wrote:
It amused, and confused, me!!!
At 08 AUG 2003 11:02AM Donald Bakke wrote:
Gerald,
MDI design and effect is dictated by the way Windows enforces certain aspects. For instance, MDIChild windows must have a titlebar.
