On 2 Mar 2005 at 16:03, A-NO-NE Music wrote: > David W. Fenton / 05.3.2 / 02:33 PM wrote: > > >I don't understand people who don't work with child windows > >maximized. Why would you want all that blank space in the parent > >window? > > > >Of course, the Mac works completely differently from the MDI on > >Windows, so maybe you're a Mac user and complaining about something > >different. > > You are right. You don't know Mac.
I knew enough to recognize that it doesn't work the same way as Windows. What I didn't know was whether you were on the Mac or on Windows (I should have remembered the virtual memory discussion). > Mac WindowServ is not like Win, no parent frame. For that, there is > no child windows a la Windows. . . Well, not as represented in the user interface, but the document windows are definitely "children" of the parent Finale application. > . . . It is not a matter of the API. In > fact, I think Trakton renders full frame, but I can't use it since it > crashes with Waves VST. > > Now, why I don't want Finale go full screen on my desktop, . . . That's one of the advantages of the Windows approach (and one of its drawbacks, too) -- you can run your parent application at 1/2 the screen and then run your document windows fully maximized within the parent window. > . . . besides it > gets under Toolbar (ack!), is that I print system log as well as > vm_stack on my desktop. I keep the bottom part of desktop visible all > the time. This way, as soon as system log reports something wrong, > such as house clock (in my case DTP) goes south, I would know before > something bad happen. I would definitely find the behavior you originally described to be annoying. I have a text editor that I use that when not maximized is very stupid about the placement of child windows (it doesn't remember that I last had my child windows maximized within the parent window) so that the child windows end up cut off at top (behind the tool palette) and on the right (by the parent window boundary). It's non- standard behavior for Windows MDI applications, and therefore, it's wrong. Your situation sounds similarly non-standard, whether the behavior you seek is provided by an OS API structure or by the programmers of the application itself. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
