Follow-up Comment #11, bug #43454 (project gnustep):

I finally managed to reproduce the descriped behaviour with a slight variation
of my code:


  [text insertText: @"Hola program"];
  NSLog(@"inserting text");
  [text setSelectedRange: NSMakeRange(5, 7)];
  [textStorage beginEditing];
  [text replaceCharactersInRange: NSMakeRange(5, 7) withString: @"programa"];
  NSLog(@"glyphAtIndex");
  //[lm glyphAtIndex: 13 isValidIndex: &valid];
  [lm _generateRunsToCharacter: 13];
  NSLog(@"endEditing");
  [textStorage endEditing];
  NSLog(@"didChangeText");
  [text didChangeText];
  NSLog(@"inserted text");

With this I get an ifinit loop and the glyph dump just looks like yours:

--- dumping runs
0x22014d0 13 chars, 13 glyphs, 1 complete, prev 0x206dea0 next 0x222a268
         level 0, continued 0
glyphs:
    0 0048 u0048      1 006f u006f      2 006c u006c      3 0061 u0061      4
0020 u0020      5 0070 u0070      6 0072 u0072      7 006f u006f      8 0067
u0067      9 0072 u0072     10 0061 u0061     11 006d u006d     12 0061 u0061 

0x222a268 1 chars, 0 glyphs, 0 complete, prev 0x22014d0 next    (nil)
         level 1, continued 0
- structure
    head: 0x22014d0 1   0   0|0x222a250 1  13  13|   (nil) 0  14  13|   (nil)
0  14  13|   (nil) 0  14  13|   (nil) 0  14  13|   (nil) 0  14  13|   (nil) 0 
14  13|   (nil) 0  14  13|   (nil) 0  14  13|   (nil) 0  14  13|   (nil) 0  14
 13|   (nil) 0  14  13|   (nil) 0  14  13|   (nil) 0  14  13|
0x22014d0: 0x222a268 1  13  13|
0x222a268:    (nil) 0   1   0|   (nil) 0   1   0|
--- done

With the commented out line,
[lm glyphAtIndex: 13 isValidIndex: &valid];
I get no glyph dumps and the following message: 

Problem posting notification: <NSException: 0x20c2640> NAME:NSGenericException
REASON:Glyph generation was triggered for a layout manager while the text
storage it was attached to had unprocessed editing. This is not allowed. Glyph
generation may be triggered only at points where calls to -beginEditing and
-endEditing are balanced. INFO:(null)

Now with this in place I should be finally able to track down what is going
wrong.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?43454>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/


_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep

Reply via email to