Text content doesn't change when using variables.

[AW]

I have a checklist with about 10 items. Each item has an info icon to explain how to perform the check. Rather than creating multiple screens or layering multiple text boxes, I added many textboxes on an unused screen and then used variables to references those text boxes. For example, Textbox1 = "ABC", Textbox2 = "123", etc. Whenever Infoicon1 is seledted, a single information text box displays variable X which displays Textbox1 (ABC). If Infoicon2 is selected, variable X is updated to display Textbox2 (123), etc.

This all works fine when testing in the builder, but when I open the actual app (browser or iOS - haven't tried Android), the textbox is blank. Not sure why it works in the builder if my code is wrong. Anyone have a solution?

[DBO_DV]

Why do you update your variable to display the text. you would improve the perfomance of your app by updating the variable directly with the text instead of referencing an Textinput from another screen.

[AW]

Thank you for the reply, but I don't quite understand your response. To clarify, I'm not using a Textinput. I just have labels - textbox placeholders for the predefined text. I may have not accurately described that in my original post. The only purpose of the variable is to simplify the action from the 10 different info clicks. 

[AW]

FYI, I found a solution, but I cannot understand the logic to it. While testing using a Context Variable vs a Global Variable, I was able to get the functionality to work. The confusing part is I didn't really change anything to the objects in the app. 

Originally, I had this: Onselect (Info Icon), Set(InfoText, BackDoorPolicyLabel)
This changed the label with InfoText as the variable to display the paragraph of text I had in the BackDoorPolicyLabel label.

I then tested with a Context Variable and changed the Onselect to
Set(InfoText, BackDoorPolicyLabel); UpdateContext( { InfoContext: BackDoorPolicyLabel.Text } )
(I left the original Set variable just as I was testing and didn't mind it being there.)

The icon button then worked, and the variable label worked, but I noticed that all icon buttons worked, even though the Context Variable applied only to the first item tested (Back Door Policy). Even in that example, the Context Variable didn't reference the InfoText variable, so it really made no sense.

So as long as the UpdateContext is initiated, the Set variables work - even though the Context Variable references nothing and doesn't match the other set variables. 

[DBO_DV · Accepted solution]

Okay I still don't understand why you set your variable to be a Textlabel when you could instead just update your variable directly. 

Set(varVariable,"Text") instead of Set(varVariable ,TextLabel.Text)

Referencing controls that are on other screens is not a great way to build your app performance wise. 

Also using a context variable that isn't used, is also not great for the performance of your app. 

If it works for you that's fine but be aware, that if you want to expand the app further you could encounter performance issues. Depending on the device you're using your users could already encounter them now.

[AW]

I appreciate that perspective, and in this case, it may be an acceptable solution. I'll check and verify. The main reason for the concept though, is thinking to future management of this app and its modifications. I do all of the design work and programming, so when I'm rolling to the field, I consider how they can self-maintain. In the event the item checked or instruction box changes, it's easier for a non-programmer if I provide an input or obvious text box, vs going into the code of the button. I actually considered using a data source so it could be changed without even going into the designer, but I didn't want to add another source and separate location of information for this one. It's unlikely this will change often (and why I'll try your suggestion), but it's just a general concept I use for these purposes. Thanks for your follow-up. I'll mark yours as the solution if it resolves the problem.

[DBO_DV]

Calling a data source is a great solution for what you just described. 

I do it as well like this when I want to give my clients the possibility to change the variables themselves. 
To keep the amount of calls to a reasonable level I collect the whole table on start and use the collection as reference afterwards. That way I don't have to worry about internet connection while updating a variable.