When using the eachLink function, the link type gets changed to one with double quotation marks.
The agree link type changes to "agree".
eachLinkTest.tbx (232.7 KB)
I can’t reproduce this. given the lack of description of the test, I made:
- two notes, ‘A’ and ‘B’.
- I added two, differently typed links from a to B. One type
*untitled(so no link label), the other typeagree.
This is the result:
I then:
- selected note ‘Log’ and deleted any $Text there.
- selected note ‘A’ and applied the stamp ‘link’.
The result:
i.e. no change! The 'Log note has this text:
alink: source:"/A";dest:"/B";destination:"/B";isFirst:true;isLast:false;sourceID:1745752958;destID:1745752962;sourceIDString:tbx:BoDhN+;destIDString:tbx:BoDhOC;type:*untitled;class:;title:;target:;url:"";comment:;anchor:;visible:true;broad:false;dashed:false;dotted:false;linear:false;bold:false;outbound:true;basic:true;
alink: source:"/A";dest:"/B";destination:"/B";isFirst:false;isLast:true;sourceID:1745752958;destID:1745752962;sourceIDString:tbx:BoDhN+;destIDString:tbx:BoDhOC;type:agree;class:;title:;target:;url:"";comment:;anchor:;visible:true;broad:false;dashed:false;dotted:false;linear:false;bold:false;outbound:true;basic:true;
So, this would suggest the cause of your problem is something else or you have not accurately described the steps leading to the error.
Please can give step-by-step instructions to reproduce the error? I’m sore to ask, but it is very difficult to diagnose an un-reproducible problem. 
This is corrected in the current backstage version. If you need it, I can provide it to you even if you’re not part of the backstage program.
Thank you for trying it out. 
And I’m sorry for the lack of explanation.
When you select the Test note and execute the link stamp, double quotation marks are added to the link type.
Each time the eachLink function is called, additional double quotation marks are appended.
So, the reason the bug cannot be reproduced might be because you are using the backstage version.
1 Like
If there will be a gap until the next release, it would be helpful if you could provide the backstage version.
Oops, thought I was in the main release but I do see the issue—my sincere apologies. 
No worries, thanks for taking the time to check.
1 Like
This was reported to @Eastgate shortly after v10.1.2 was released. I can confirm that this problem was resolved with the latest Backstage b711 release. It looks like @mwra has also confirmed that the latest Backstage release resolves the problem. From my testing, it appears that most of the other useful enhancements included in the official 10.1.2 release are working in the b711 release as well.
3 Likes