• 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: strange "lockFocus sent to a view whose window is deferred" error with an NSOutlineView on Tiger
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: strange "lockFocus sent to a view whose window is deferred" error with an NSOutlineView on Tiger


  • Subject: Re: strange "lockFocus sent to a view whose window is deferred" error with an NSOutlineView on Tiger
  • From: Martin Redington <email@hidden>
  • Date: Mon, 17 Mar 2008 17:45:40 +0000


On 17 Mar 2008, at 17:07, Michael Nickerson wrote:


On Mar 17, 2008, at 9:06 AM, Martin Redington wrote:


I'm seeing the following error

2008-03-17 12:42:11.916 MyApp[11155] *** Assertion failure in - [MyOutlineView lockFocus], AppKit.subproj/NSView.m:3248
2008-03-17 12:42:11.917 MyApp[11155] lockFocus sent to a view whose window is deferred and does not yet have a corresponding platform window



You usually run into this error when a view tries to draw to a window that hasn't been displayed at all yet. I don't know if this is the case for you, since you're talking about swapping views, though - are you actually swapping out windows when you do this?


Anyway, you can try to make the window non-deferred (you can deselect the checkbox for that in IB) and see if you get the error then. Doing that makes the window make a connection to the window server when it's created rather than when it's first displayed.

The window is a single window app. Making the window non-deferred makes no difference.



If that doesn't help, is the scroll view you're adding the outline view to part of the view hierarchy when you do that? Maybe there was a bug in Tiger where the scroll view tried to display the document view immediately when it's set and if it's not actually part of a window I suppose this might pop up. That's all just a guess, though.

Yep. The scrollview is the place holder for the views, so that's always in place.


I'll try and get a test case together - with a bit of luck I'll find a workaround while I'm doing that.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: strange "lockFocus sent to a view whose window is deferred" error with an NSOutlineView on Tiger
      • From: Martin Redington <email@hidden>
References: 
 >strange "lockFocus sent to a view whose window is deferred" error with an NSOutlineView on Tiger (From: Martin Redington <email@hidden>)
 >Re: strange "lockFocus sent to a view whose window is deferred" error with an NSOutlineView on Tiger (From: Michael Nickerson <email@hidden>)

  • Prev by Date: NSTreeController & NSOutlineView bindings w/ Core Data
  • Next by Date: Apple Events and automatic AutoReleasePool managment
  • Previous by thread: Re: strange "lockFocus sent to a view whose window is deferred" error with an NSOutlineView on Tiger
  • Next by thread: Re: strange "lockFocus sent to a view whose window is deferred" error with an NSOutlineView on Tiger
  • Index(es):
    • Date
    • Thread