Re: DebugAssert when getting a window
Re: DebugAssert when getting a window
- Subject: Re: DebugAssert when getting a window
- From: Eric Schlegel <email@hidden>
- Date: Mon, 9 May 2005 09:39:56 -0700
On May 9, 2005, at 9:30 AM, Darrin Cardani wrote:
I have turned on debug libraries when debugging my Cocoa app, and
I'm seeing some odd assertions. (This is in XCode 1.5, where I've
set the executable's "Use xxx suffix when loading frameworks" to
"debug".) I don't know if they're actually the fault of something
my app is doing, or if they're harmless. For example, in my
document's [-MyDocument setupWindowsAndControllers] method, I have
the following:
movieWindow = [movieWindowController window];
According to the stack trace, this call causes the window
controller to load the window from the .nib file. In doing so, it
eventually calls down into InvalWindowRect (), which calls
RemoveEventFromQueue (), which calls operator delete (void*). It is
in operator delete (void*) that I get the following assertion:
DebugAssert: HIToolbox: data != NULL
exception_ValidateWindowRgn_InvalidWindowPtr [line 1368, file
Windows/Source/WindowRegions.cp]
What exactly is this telling me? Is this anything I need to be
concerned about?
I think you can ignore this.
My guess is that the QuickTime movie controller is attempting to
invalidate a portion of a window, but it's passing an invalid window
to the InvalWindowRect API. The warning is telling you about the
invalid window.
Probably the movie controller isn't properly handling the case where
it's in a Cocoa window (which has no Carbon WindowRef in most cases)
rather than a Carbon window.
If you can reproduce this in a test app, you could file this as a bug
and the QT folks could take a look at it.
-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