On Sun, May 31, 2009 at 7:30 PM, Kyle Sluder wrote:
> On Sun, May 31, 2009 at 4:08 PM, Seth Willits wrote:
>> Alright, well, either way I know it's not happening because it's not in the
>> console log.
>
> You don't know it's not nil unless you check yourself. Set a
> conditional breakpoint; it'
On Sun, May 31, 2009 at 4:08 PM, Seth Willits wrote:
> Alright, well, either way I know it's not happening because it's not in the
> console log.
You don't know it's not nil unless you check yourself. Set a
conditional breakpoint; it's the only real way to reason about your
code.
And FWIW, clic
On 31 maj 2009, at 16.08, Seth Willits wrote:
On May 31, 2009, at 3:49 PM, Joar Wingfors wrote:
If [self title] were nil, I'd get an exception when creating the
attributed string, not a crash when calling -size. There's nothing
fancy going on with the string. The only thing I can think of
On May 31, 2009, at 3:45 PM, Kyle Sluder wrote:
On Sun, May 31, 2009 at 3:36 PM, Seth Willits
wrote:
If [self title] were nil, I'd get an exception when creating the
attributed
string, not a crash when calling -size. There's nothing fancy going
on with
Not on Leopard you don't. You do g
On 31 maj 2009, at 15.36, Seth Willits wrote:
For some reason that I have yet to discover, calling -
[NSAttributedString size] is causing a crash. It's rare, but it's
happening. I can't yet repeat it on my system.
If [self title] were nil, I'd get an exception when creating the
attribut
On Sun, May 31, 2009 at 3:36 PM, Seth Willits wrote:
> If [self title] were nil, I'd get an exception when creating the attributed
> string, not a crash when calling -size. There's nothing fancy going on with
Not on Leopard you don't. You do get a warning, but not an exception.
This is the warn
