On Wed, May 9, 2012 at 5:08 AM, Peter Ammon wrote:
>
> Hope that helps,
>
It did. Thanks!
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-
On May 8, 2012, at 2:01 AM, ecir hana wrote:
> Why's that? Do I have to remember the returned NSPoint and pass it to
> next cascadeTopLeftFromPoint:?
Yes; the usual pattern is:
static NSPoint cascadeLoc = {0, 0};
cascadeLoc = [window cascadeTopLeftFromPoint:cascadeLoc];
The first time this is
Thanks! Will look at it.
On Tue, May 8, 2012 at 5:22 PM, Richard Somers wrote:
> On May 8, 2012, at 8:51 AM, ecir hana wrote:
>
> > Yes, document-based.
> >
> > However, not sure if it is an issue, but I have my own subclassed window
> controller. The docs also say that the default for "shouldCas
On May 8, 2012, at 8:51 AM, ecir hana wrote:
> Yes, document-based.
>
> However, not sure if it is an issue, but I have my own subclassed window
> controller. The docs also say that the default for "shouldCascadeWindows" is
> YES. I tried to set it to YES in "setShouldCascadeWindows:", without
Thank you for the reply!
Yes, document-based.
However, not sure if it is an issue, but I have my own subclassed window
controller. The docs also say that the default for "shouldCascadeWindows"
is YES. I tried to set it to YES in "setShouldCascadeWindows:", without
luck.
I look at the EnhancedDat
On May 8, 2012, at 3:01 AM, ecir hana wrote:
> I create a window like this:
>
> id window = [[[NSWindow alloc] initWithContentRect:NSMakeRect(0, 0, 200,
> 200) styleMask:NSTitledWindowMask backing:NSBackingStoreBuffered
> defer:NO] autorelease];
> [window cascadeTopLeftFromPoint:NSMakePoint(20,20
