[IGN-9684] Perspective radio group not first reading from indirect tag

Ignition
1

I have a view with a radiogroup with 4 selections. The "index" is bi-directionally bound 'indirect'.

It seems the behavior in perspective is not to first read from the indirect tag to initially set the radio buttons but instead, on loading the view, to write to the tag with whatever state it was saved in in designer.

2

yea this is a bug. It works fine with 'dropdown' component. I just pasted the binding.

3

What version are you using? I just tried this on 8.1.39 and could not replicate.

4

8.1.35

Sorry I should have included that

5

I have had similar issues, but for me only when I have something bound to the text props. IA created a ticket and said it was a bug.

6

I do also bind to the text of 3 of the selections.

7

Then that is most likely your issue. Remove those bindings and it will probably work.

8

I will confirm but unfortunately, I'd really like to keep them. Is there a way for me to see the status of that ticket? If its fixed in some more recent version I would upgrade.

9

Ticket #107388. Not sure how you can add yourself, might need to contact support.

I tried some workarounds, even writing to the props in a script didn't seem to work. So, for now the only option I see is don't bind or write to them.

Edit, I can respond to the ticket and see if they can add you.

10

I cut the line and opened an internal ticket to get this looked at. Tags actually don't directly play into this behavior as the same issue can be seen when using a Session property.

1 Like
11

Thank you sir.

I probably should be able to figure this out but how do I see the status of tickets like #107388 referenced above?

12

You would have to contact Support and reference that number. Our internal ticketing systems (Support and Development have separate ticketing systems) are not exposed to the public.

13

Would that ticket number appear as fixed in version release notes or something?

Is there a way for me to know when its fixed without bugging anyone?

14

Without contacting Support and getting attached to that ticket, you can monitor this thread. We do try to notify documented interested parties (forum links in our Dev tickets), though I will admit we don't always have time. We also publish changelogs here on the forum, but it's not always easy to translate a changelog fix to your particular issue.

15

Support did show a workaround. On the PARAMS, where you are passing in the tag path, set this to a working tag, then save the view. All bindings need set to persistent.

This worked for me.

1 Like
16

selecting 'Persistent' does seem to work for me

1 Like