• 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: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]


  • Subject: Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
  • From: John Stiles <email@hidden>
  • Date: Thu, 9 Feb 2006 15:17:22 -0800

On Feb 9, 2006, at 3:13 PM, Eric Schlegel wrote:


On Feb 9, 2006, at 3:09 PM, Matt Gough wrote:

TransitionWindow is not tested or qualified on NSWindows. It may happen to work in certain instances, but there's currently no intention that it should.

So is there a list of the safe and unsafe functions for such WindowRefs? (Just the safe list would be fine, since I guess everything else should be considered unsafe).

Do you mean, safe and unsafe APIs other than TransitionWindow? I don't have such a list myself. It's possible that someone else in AppKit-land may have one, but I'm not sure anyone has gone through and exhaustively tested the Window Manager on AppKit-generated windows. In general, it's best to use the API the corresponds to the "true nature" of the window; if it's really an AppKit window, use NSWindow APIs, and if it's really a Carbon window, use Window Manager APIs.

I think the question is more along the lines of, is there a list of Carbon functions that Apple tests to ensure that they work when passed a [nsWindow windowRef]?


Your original post said something along the lines of "Apple doesn't test NSWindow transitions with TransitionWindow"... well, which parts do get tested? Surely some APIs must be guaranteed to work when passed a [nsWindow windowRef]... otherwise the API would be a bit too scary to use ;)

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
      • From: Eric Schlegel <email@hidden>
References: 
 >Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef] (From: Dave MacLachlan <email@hidden>)
 >Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef] (From: Eric Schlegel <email@hidden>)
 >Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef] (From: Matt Gough <email@hidden>)
 >Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef] (From: Eric Schlegel <email@hidden>)

  • Prev by Date: Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
  • Next by Date: Objective-C++, class scope constants, name conflicts
  • Previous by thread: Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
  • Next by thread: Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
  • Index(es):
    • Date
    • Thread