Hi, I have a weird situation. I used Density_Button to call up my Virtual_Calculations screen but, at some point, it began calling up the Virtual_BLE_Scaning_Page screen, which I had not requested. I then switched that buttons' contents to what is shown below. Now, the Pressure_Button does bring up the Virtual_Calculations screen UNTIL I click the Density_Button. Once I do that, both the Density_Button and the Pressure_Button bring up only the Virtual_BLE_Scanning_Page.
How could one button click control the contents of another? Is there some hidden code I am not aware of or am I doing something incredibly stupid here?
I (think I) am simply hiding and revealing screens so I don't know what could be happening. Any ideas?
When wrangling multiple Arrangements' visibilities, it is simplest to have them all siblings, none enclosing the other, and use a common procedure HideEverything to make them all invisible.
In the Button Click event to show an Arrangement, call the HideEverything procedure then expose the desired Arrangement.
That saves you from having to remember every Arrangement name in every Button, reducing block counts for n Arrangement switching from n^2 to 2n.
I couldn't find or create that procedure so I simply created a set_this_screen.visible tag for every arrangement and made all but one false. It still cleared out the bug. Thanks, again.
