Re: Maximize/Restore Win vs OSX (REALbasic network user group Mailinglist archive)
Back to the thread list
Previous thread: Re: messy waveforms
Next thread: ProgressWheel freeze with HTTPSocket
| Re: Maximize/Restore Win vs OSX |
| Date: 02.03.10 22:59 (Tue, 02 Mar 2010 16:59:31 -0500) |
| From: Tom Buchler |
|
From: Tim Jones <<email address removed>>
Subject: Re: Maximize/Restore Win vs OSX Tim, Thanks for the discussion of Zoom. It doesn't seem that by default that is what RB document windows do, nor what OSX's own Finder window does. -Tom _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html> |
| Maximize/Restore Win vs OSX |
| Date: 02.03.10 07:27 (Tue, 02 Mar 2010 01:27:24 -0500) |
| From: Tom Buchler |
|
RB 10r1 (and also RB9)
With Window1, a normal Document window: Under Windows: Window1.Maximize maximizes the window, as expected. When the window is maximized, Window1.Restore returns the window to its previous dimensions. Under OSX (Leopard): Window1.Maximize maximizes the window, as expected. When the window is maximized, Window1.Restore makes the window even larger, so I can't see or use any of the titlebar buttons or features. Is this expected behavior? If so, how, under OSX, do I restore a window to its un-maximized dimensions? -Tom _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html> |
| Re: Maximize/Restore Win vs OSX |
| Date: 02.03.10 22:59 (Tue, 02 Mar 2010 16:59:20 -0500) |
| From: Chip G. |
|
On Mar 2, 2010, at 11:43, Tim Jones wrote:
> One thing that is important to remember is that OS X does not offer a "Maximize" button. The buttons are "Close", "Minimize", and "Zoom". > > The key difference is that the Zoom model is not "fill the screen" - "Return to last size" as it is on the Windows and Linux platforms. It's much more "convoluted" than that. So how does one 'zoom' a window on the Mac if you need to code your own? (I noticed that if you just select the right window and enable zooming it works, but there might be cases for needing to do your own coding.) |
| Re: Maximize/Restore Win vs OSX |
| Date: 02.03.10 17:43 (Tue, 2 Mar 2010 09:43:09 -0700) |
| From: Tim Jones |
|
On Mar 1, 2010, at 11:27 PM, Tom Buchler wrote:
> RB 10r1 (and also RB9) > > With Window1, a normal Document window: > Under Windows: > > Window1.Maximize maximizes the window, as expected. When the window is maximized, Window1.Restore returns the window to its previous dimensions. > > Under OSX (Leopard): > > Window1.Maximize maximizes the window, as expected. When the window is maximized, Window1.Restore makes the window even larger, so I can't see or use any of the titlebar buttons or features. > > Is this expected behavior? If so, how, under OSX, do I restore a window to its un-maximized dimensions? One thing that is important to remember is that OS X does not offer a "Maximize" button. The buttons are "Close", "Minimize", and "Zoom". The key difference is that the Zoom model is not "fill the screen" - "Return to last size" as it is on the Windows and Linux platforms. It's much more "convoluted" than that. Maybe this quote from the Apple HIG might better explain things: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Resizing and Zooming Windows Your application determines the minimum and maximum window size. Base these sizes on the resolution of the display and on the constraints of your interface. For document windows, try to show as much of the content as possible, or a reasonable unit, such as a page. Your application also sets the values for the initial size and position of a window, called the standard state. Don’t assume that the standard state should be as large as possible; some monitors are much larger than the useful size for a window. Choose a standard state that is best suited for working on the type of document your application creates and that shows as much of the document’s contents as possible. The user can’t change the standard size and location of a window, but your application can change the standard state when appropriate. For example, a word processor might define the standard size and location as wide enough to display a document whose width is specified in the Page Setup dialog. The user changes a window’s size by dragging the size control (in the lower-right corner). As a user drags, the amount of visible content in the window changes. The upper-left corner of the window remains in the same place. The actual window contents are displayed at all times. If the user changes a window’s size or location by at least 7 pixels, the new size and location is the user state.The user can toggle between the standard state and the user state by clicking the zoom button. When the user clicks the zoom button of a window in the user state, your application should first determine the appropriate size of the standard state. Move the window as little as possible to make it the standard size, and keep the entire window on the screen. The zoom button should not cause the window to fill the entire screen unless that was the last state the user set. When a user with more than one monitor zooms a window, the standard state should be on the monitor containing the largest portion of the window, not necessarily the monitor with the menu bar. This means that if the user moves a window between monitors, the window’s position in the standard state could be on different monitors at different times. The standard state for any window must always be fully contained on a single monitor. When zooming a window, make sure it doesn’t overlap with the Dock. For more information about the Dock, see “The Dock.” _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html> |
| Re: Maximize/Restore Win vs OSX |
| Date: 02.03.10 15:30 (Tue, 02 Mar 2010 09:30:14 -0500) |
| From: Chip G. |
|
On Mar 2, 2010, at 01:27, Tom Buchler wrote:
> Under OSX (Leopard): > > Window1.Maximize maximizes the window, as expected. When the window is maximized, Window1.Restore makes the window even larger, so I can't see or use any of the titlebar buttons or features. > > Is this expected behavior? If so, how, under OSX, do I restore a window to its un-maximized dimensions? I'm surprised no one has chimed in yet. On OS X, functionally we click on the "maximize" button (little green dot) to maximize and restore a window (it doesn't change, unlike in Windows). I'm not sure how it's supposed to work programmatically, but I'm fairly certain you can record the top, left, height, and width of a window prior to maximizing and restore those when desired to restore. I just did a test on my most recent app, if I click on the Maximize button it does, when I click again it restores. That is with no further coding by me, apparently most things can be done automagically. |
Links
MBS Filemaker Plugins - Christians Software aus Nickenich