On 6 May 2011, at 7:24 PM, Indragie Karunaratne wrote:
> I'm hesitant on filing a bug for this because it appears that there is no
> such check on *later* versions of OS X ;-)
Always file. It won't hurt their feelings. If, hypothetically, you don't find a
diagnostic in prerelease software, it m
After painstakingly going through my code line by line, I managed to find the
issue. I was using a custom NSScroller subclass, and the rect returned by
rectForPart: was an empty rect, which caused NSBezierPath to freak out. The
sanity check is a good idea, but a) the log message should provide i
I'm assuming it is, because as soon as I click "Continue" after it breaks, the
message is logged. Once the message has been logged once, the entire window
stops responding and any attempt to click on anything will just result in the
message being logged over and over again.
On 2011-05-05, at 7:
On Thu, May 5, 2011 at 5:49 PM, Indragie Karunaratne
wrote:
> I will check my NSBezierPath code to see if I'm doing anything of that sort,
> but like I said, this only happens on 10.6.7. And Kyle, indeed the only code
> of mine that is in the stack trace is NSApplicationMain(). The stack trace
> c
I have gone through and checked my code to make sure that I wasn't doing the
things you mentioned earlier with NSBezierPath. This is a real pain to solve
seeing as the debugger isn't giving me a single shred of useful information.
On 2011-05-05, at 6:56 PM, Graham Cox wrote:
> Maybe because som
On 06/05/2011, at 10:49 AM, Indragie Karunaratne wrote:
> but like I said, this only happens on 10.6.7
Maybe because some additional asserts/sanity checking was added in 10.6.7. It
doesn't mean the bug isn't there on earlier OS, it just means it was keeping
quiet about it.
--Graham
___
Thanks for all the replies,
I will check my NSBezierPath code to see if I'm doing anything of that sort,
but like I said, this only happens on 10.6.7. And Kyle, indeed the only code of
mine that is in the stack trace is NSApplicationMain(). The stack trace
confirms this:
thread #1: tid = 0x2d0
On Thu, May 5, 2011 at 5:29 PM, Indragie Karunaratne
wrote:
> 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
> f
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
> alm
On May 5, 2011, at 7:29 PM, 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"
>
Check NSBezierPath usage. A message like that shows up when -relativeXXX is
used with
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 re
11 matches
Mail list logo
