On 06/05/2011, at 10:29 AM, Indragie Karunaratne wrote: > This message keeps getting logged when trying to run my app (OS X 10.6.7): > > "No current point for control point bounds" > > This does *not* happen on newer versions of OS X, only 10.6.7. It happens > almost as soon as the app opens and renders it totally useless as the window > will not respond. The worst part is that I have no clue where it is coming > from. I put a breakpoint on NSLog() but it breaks at NSApplicationMain() when > that message is logged, which gives me no clue as to what could be causing it. > > Does anyone know why this occurs and how to go about debugging it?
It comes from NSBezierPath. It typically means either: a) you are calling -bounds on an NSBezierPath object when the object is empty, or b) you are calling -lineToPoint: or curveToPoint: on NSBezierPath without calling moveToPoint: first. --Graham _______________________________________________ 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-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
