Re: NSLayoutManager exception

FROM : Douglas Davidson
DATE : Thu Jun 08 22:48:11 2006

On Jun 8, 2006, at 8:19 AM, David Dunham wrote:

> Just noticed this in the console -- I think I was printing at the 
> time:
>
> 2006-05-31 17:44:02.410 Opal[10907] <NSATSTypesetter: 0x385e70>: 
> Exception *** NSRunStorage, _NSBlockNumberForIndex(): index (0) 
> beyond array bounds (0) raised during typesetting layout manager 
> <NSLayoutManager: 0x3d4e40>
>    1 containers, text backing has 373 characters
>    selected character range {0, 0} affinty: downstream 
> granularity: character
>    marked character range {373, 0}
>    Currently holding 0 glyphs with 1 glyph holes and 1 layout holes.
>    Glyph holes: (Glyph hole at: 0 for chars: {0, 373})
>    Layout holes: (Hard layout hole for chars: {0, 373})
> , glyph range {0 10}. Ignoring...
>
> Is this anything I have control of? (I don't think it's repeatable.)
>


This means that a call to the typesetter has resulted in a request 
for non-existent glyph information.  Without at least a backtrace 
it's difficult to say anything more.  If it isn't repeatable, there's 
a good chance it isn't something you have control over.  If you make 
direct calls to the layout manager, you might examine those to see 
whether they seem reasonable; you might also look to see whether you 
use a single layout manager from more than one thread at once.

Douglas Davidson