From: Matthias T. <th...@ei...> - 2002-08-08 07:45:53
|
Hello Haejoong, Haejoong Lee wrote: > Matthias, > > Thank you for reporting the bug! > It's now fixed for the next release. Fine :) so I assume it's fixed in the CVS? I'm working with the CVS because of the extended Tcl wrapper and the validation functions. By the way, could you remove the debugging output from the validation functions, especially Line 199 of Validation.cc floods my terminal ;) >>I have a similar problem when unsetting anchor offsets using >>AG::UnsetAnchorOffset, but no solution. > > > I'm not sure about the above problem. It will be a great help > if you can give us a little more details. Yes, certainly. I am building an AG where all anchors have an offset first, and then try to unset all anchor offsets except for the start and end anchor of the AG. It seems to work until the third or so AG of my test data, then an exception occurs: AGExceptionAG Exception caught when calling UnsetAnchorOffset: Anchor not found! while executing "AG::UnsetAnchorOffset $anchor" I also noticed that before the exception occurs, [AG::GetAnchorSet $agId] returns the anchor set in a different order than before, which is the correct topological and chronological order. Maybe this problem is related to the sorting of the anchors? As I understood from the papers, an AG is a directed acyclic graph, so that a topological sorting would be possible regardless of the anchor offsets. But as I understand from the sources, the sorting of the anchors is only done chronologically, i.e. if all anchors have an offset. So apart from the problem above, wouldn't the topological sorting of the anchors be a nice feature for the AG library? >>Maybe one of the developers could check the sources with respect to the >>Identifier management, in case more of these problems exist? > > I hope Xiaoyi can work on this when he gets back. Ok. > Thank you. > > Haejoong Thank you for your quick reply and fix :) Regards. Matthias |