Re: [agtk-devel] lost anchor identifier at AG::splitAnnotation

[Matthias T. <th...@ei...>]

Hello Xiaoyi,

Xiaoyi Ma wrote:
 > I couldn't replicate the problem you encounted when with
 > AG::UnsetAnchorOffset. Do you have some sample code I can use to 
figure out
 > what went wrong?

Yes, I have attached some sample code, and a sample AIF File. When
calling "test.tcl Text.xml", you should get something like this:

trying to unset anchor Test:AG-901-1.3.1:Anchor10, offset 147.313241
Test:AG-901-1.3.1:Anchor1 Test:AG-901-1.3.1:Anchor2
Test:AG-901-1.3.1:Anchor3 Test:AG-901-1.3.1:Anchor4
Test:AG-901-1.3.1:Anchor5 Test:AG-901-1.3.1:Anchor6
Test:AG-901-1.3.1:Anchor7 Test:AG-901-1.3.1:Anchor8
Test:AG-901-1.3.1:Anchor10 Test:AG-901-1.3.1:Anchor11
Test:AG-901-1.3.1:Anchor12 Test:AG-901-1.3.1:Anchor9
AGExceptionAG Exception caught when calling UnsetAnchorOffset:
Anchor not found!
     while executing
"AG::UnsetAnchorOffset $anchor"


Have you also noticed my mail from the 8th of August, where I wrote:

 > 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?

Regards.
Matthias