the_fisher Posted September 17, 2021 Share Posted September 17, 2021 It seems that there is an issue when using %g and a text representation of device socket in a cable numbering schema. When matching for Src_Skt_Name or Dst_Skt_Name and using as %1, %g will not increment. For example: Src_Dev_Name^=%g %1 will produce a unique incrementing number along with a source device name in text form for each cable. However, Src_Skt_Name^=%g %1 will not increment the unique number and will produce the number 1 followed by the source socket name for each cable. At the same time, %u seems to work fine. Quote Link to comment
Vectorworks, Inc Employee Conrad Preen Posted September 20, 2021 Vectorworks, Inc Employee Share Posted September 20, 2021 @the_fisherInteresting. Can you give me a more complete example to try? If you Edit As Text... you'll be able to copy the complete rule e.g. Src_Dev_Name^?JF_&Src_Skt_Name^PORT=%s#1#2 That way I can try it out and let you know. Conrad Quote Link to comment
Vectorworks, Inc Employee Conrad Preen Posted September 21, 2021 Vectorworks, Inc Employee Share Posted September 21, 2021 @the_fisher Well I have checked out what I can glean from the above and %g seems to work as designed. %g looks at the entire cable number and checks that it is unique. So if the sockets in your device all have unique names (a good thing) then %g will not need to increment because each combination of <socket name>+ number is unique. If you want a number that increments each time the tag is used then you should use the %u tag. Hope I've answered the question. Let me know if I have missed something. Best Conrad Quote Link to comment
the_fisher Posted September 21, 2021 Author Share Posted September 21, 2021 @Conrad Preen Thanks for the reply! This answers my question. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.