Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
- Subject: Re: Calling TransitionWindowWithOptions on a WindowRef returned from a [NSWindow windowRef]
- From: Eric Schlegel <email@hidden>
- Date: Fri, 10 Feb 2006 10:40:04 -0800
On Feb 9, 2006, at 3:17 PM, John Stiles wrote:
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 ;)
The ability for Carbon apps to contain Cocoa windows, and vice versa,
was mostly tested at the end-user scenario level rather than the API
level. Specifically, this code was implemented in order to support
features such as a Carbon application containing a Cocoa floating
window like the font panel. We've verified appropriate behavior in
specific user scenarios such as this one, but we don't verify
behavior at the API level. Tiger contains many bug fixes in both
Carbon and Cocoa to improve the behavior that we see in user
scenarios, and we intend to make further improvements in future
releases - your bug reports are helpful here in letting us know what
problems you're encountering.
-eric
_______________________________________________
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