• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Window resizing behavior
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Window resizing behavior


  • Subject: Re: Window resizing behavior
  • From: Shawn Erickson <email@hidden>
  • Date: Wed, 24 Dec 2003 09:03:05 -0800

On Dec 24, 2003, at 8:20 AM, Don Rainwater wrote:

I've noticed something about window resizing behavior. Here's the scenario: With other applications already open, play a game that changes the display resolution. When you quit the game, the resolution changes back to it's original setting. The other applications' windows react differently to this change/change-back cycle.

I haven't done exhaustive testing, but here are the three outcomes I have observed:

1. Windows shrink to fit the lower resolution (Mail, Safari).
a. In some apps, the windows move toward the top left to fit within the lower-res bounds.
b. In others, the windows seem to move to the top right.

2. Windows expand to maximum size to fit the screen (Excel).

3. Windows remain at their original sizes (BBEdit).

My first reaction is that BBEdit has it right. If I run something, like a game, that changes the resolution temporarily, I want everything to return to "normal" when I quit that app. What is the correct resizing/repositioning action for well-behaved windows for resolution switches?

If an application captures the screen and changes the resolution just while it runs then on exit everything should go back to the way it was, just like it never happened. Neither the application capturing the screen nor other running application should have to do anything to make this happen (other then support standard application events), the OS should get things back the way it was. Of course the application capturing the screen has to use the capture API correctly.

Most often this is an example of a game capturing the screen in an incorrect fashion and/or a defect in the OS screen capture system (sometimes a defect in the "other" applications). Usually it is the "games" fault. If things are done correctly even if the game crashes while the screen is captured things should go back to normal. The current screen capture API allows for this ability the older, more classic/carbon based, API didn't make as bullet proof.

At least that is my understanding... on ADC you can view one of the WWDC sessions that covered this and source examples exist on Apple's website on how to capture the screen (however it doesn't do it the best of ways in my opinion because it doesn't use CGBeginDisplayConfiguration, CGCompleteDisplayConfiguration, or CGRestorePermanentDisplayConfiguration granted these didn't show up until 10.2).

The API to use is documented here...
http://developer.apple.com/documentation/GraphicsImaging/Reference/ Quartz_Services_Ref/index.html

-Shawn
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Window resizing behavior (From: Don Rainwater <email@hidden>)

  • Prev by Date: Re: Show panel that slide from the top of the window.
  • Next by Date: Re: Get milliseconds of current time
  • Previous by thread: Window resizing behavior
  • Next by thread: A real perdiciment
  • Index(es):
    • Date
    • Thread