I have a pipes configuration in a view of my perspective application where all of the links are configured the same with the exception they each look at a different bit of a status work for visibility. If the bit is true the link visibility is set to true, if the bit is false the link visibility is bond to a tag that is alternating off and on, blinking. This works great in preview mode but if I launch a perspective session certain links disappear when they should be blinking. The links all appear fine when the condition is true. In the screenshots below link 5 works properly while link 4 does not. Any idea why?
The way that you set up right now, your visible field is only updated when your tag changes, and it will grab a snapshot of the view.custom.Blink_Plus at that time.
A couple things that you can do:
- Move the tag binding to another custom property, something like
view.custom.linkStateso you don't read the same tag multiple times - Use Expression Structure binding that look at both
view.custom.linkStateandview.custom.Blink_Plus
Something like
"linkState": {view.custom.linkState},
"blink": {view.custom.Blink_Plus} - Then transform it to
if(getBit({value}["linkState"], 4), true, value["blink"])
I'm not near a designer right now, so might need to check the syntax.
Also, haven't played with pipes recently, but might want to check if you can give the pipe segment a class instead of using the visible property.
The video above shows the Session on the left and the preview of the right. I would really like to know why the two are different and why what I'm doing isn't working. As far as reading a tag multiple times, is there a limit to the number of times tags can be read from?