Welcome to the MacNN Forums.

type_r503 · Jun 25, 2002, 03:32 PM

After I set the resolution to 800X600
<blockquote>code:<hr /><pre style="font-size:x-small; font-family: monospace;">
// Get the screen rect of our main display
frame = [[NSScreen mainScreen] frame];
cgFrame = CGDisplayBounds(kCGDirectMainDisplay);
printf("%f,%f,::%f,%f\n",frame.s ize.width, frame.size.height, cgFrame.size.width, cgFrame.size.height);</pre><hr /></blockquote>frame has the value of the original resolution and cgFrame has the new resolution. Am I missing something?

type R

Chuckit · Jun 26, 2002, 04:31 AM

<blockquote>quote:<hr />Originally posted by type_r503:
After I set the resolution to 800X600
<blockquote>code:<hr /><pre style="font-size:x-small; font-family: monospace;">
// Get the screen rect of our main display
frame = [[NSScreen mainScreen] frame];
cgFrame = CGDisplayBounds(kCGDirectMainDisplay);
printf("%f,%f,::%f,%f\n",frame.s ize.width, frame.size.height, cgFrame.size.width, cgFrame.size.height);</pre><hr /></blockquote>frame has the value of the original resolution and cgFrame has the new resolution. Am I missing something?

type R<hr /></blockquote>Well, this sounded like a possible bug, so I whipped up a small program with one method and a button in the main window to call it. This is the complete code in the method:
<blockquote>code:<hr /><pre style="font-size:x-small; font-family: monospace;"> NSRect cocoaRect;
CGRect cgRect;

cocoaRect = [[NSScreen mainScreen] frame];
cgRect = CGDisplayBounds(kCGDirectMainDisplay);

NSLog(@"\nThe Cocoa method says it is %f x %f\nThe CG way says it's %f x %f", cocoaRect.size.width, cocoaRect.size.height, cgRect.size.width, cgRect.size.height);</pre><hr /></blockquote>I get the same numbers on both lines (no matter how many times I change the resolution), so I don't imagine there's anything wrong with the functions.

So here's my theory: Project Builder doesn't seem to handle printf() quite right for some reason, so the rects might actually be right while the printing is delayed. Try using NSLog() and see if you get the results you were expecting.

Angus_D · Jun 26, 2002, 12:58 PM

<blockquote>quote:<hr />Originally posted by Chuckit:
So here's my theory: Project Builder doesn't seem to handle printf() quite right for some reason, so the rects might actually be right while the printing is delayed. Try using NSLog() and see if you get the results you were expecting.<hr /></blockquote>Use fflush(stdout) to make sure all stdout is flushed.