Simple virtual screen file doesn't work

Might someone please point out what I have done wrong in the attached example? I am trying to learn how to create virtual screens. I (thought I) followed some examples correctly but, I guess not. Knowing myself, this is a simple and stupid mistake but I am blind to my error.

Screen 1 shows up in blue with button 1 at the top. Pressing button 1 takes me to a whited-out screen of death from which I must close out of. I never see screen 2.

1 Like

image

Virtual Screen 2 ended up inside Virtual Screen 1.

See the indentation?

The have to be brother and sister, not uncle and nephew.

3 Likes

Ah, It's all about family. Thanks, it works now!

Good Morning,

Might I ask for a little more guidance. I have "successfully" stacked multiple screen contents into virtual screens. When I properly code the blocks, I can see data generated from one virtual screen in another so TinyDB is fine. I have a few problems, though, that I do not understand. Perhaps the following images will tell the story better than I.

The biggest issue (and one that just appeared) is that my first screen no longer "slides up" or scrolls to reveal the big "ATMO" button (seen at the bottom of one of the All Components list. When I had multiple "real" screens, this was not an issue. Instead, when I scroll up, I scroll through the virtual screens, even though I have "Don't show hidden content in viewer" checked. I have all virtual screens sized at 100% height and width. When I uncheck the "Scroll" box, I no longer can scroll and my virtual page 1 cannot show the ATMO button and label.



So . . . I have a handle on everything except isolating the additional virtual screens, preventing them from scrolling, and returning the scroll function (ONLY) to my first virtual screen so I can see the ATMO button. Thank you to ABG or anyone who can point out my problem.

As an added detail: The first image shows the top half of virtual screen 1.

The second image shows what happens when I scroll - other (I thought hidden) virtual screens show up.

The third image shows the scrolled first page before I tried to go virtual. The end result is that I can no longer scroll virtual page 1 without scrolling through all other virtual pages.

  1. Why do you need to see that button in the designer? You know it is there.
  2. if you really need to see it, in the designer, just temporarily change the visibility of some of the arrangements above it.

There's visibility in the Designer, and there's .Visible attribute of each of those Arrangements, which you must juggle at run time.

Sample app:

Good Question! The problem is that I build .apk files to test on my Android phone. That is where the button should show but doesn't. When I had separate fixed screens, I could scroll to the ATMO button. Now, when I scroll (if I allow it in the designer), I scroll into supposedly hidden virtual screens.

make sure to have the virtual screens n the same level, see again

Taifun

For run time Screen management, you always need to have something visible somewhere to control visibility, otherwise you'd be lost in the dark.

There are different approaches to this:

  • The Tabbed approach: An always .Visible Horizontal Arrangement of Buttons, each of which hides everything below and exposes only one Vertical Arrangement. This looks visually like folder tabs sticking out in a filing cabinet, but it's constrained by Width.
  • The WormHole approach: Like a science fiction wormhole, this individual Button appears in random places, and will take you who knows where, closing all Vertical Arrangements and opening a target Arrangement.
  • The EXIT sign approach: Like the EXIT sign in well designed corridors, these Buttons hide the current Arrangement and expose another Arrangement with an EXIT button leading closer to your lobby Arrangement. Eventually you may EXIT the app.
  • The Elevator: This List Picker is atop the screen, allowing you to Select your target Arrangement directly.

I guess I am a little confused by your comment. When I open virtual screen 1, all the other virtual screens are present below if I choose to scroll, but I am unable to scroll to the ATMO button clearly on virtual screen 1. According to the blocks I am attaching, all virtual screens are at the same level and when the actual Screen1 is initialized, I disappear every virtual screen except for virtual screen 1. Why is this not working? I know my logic is flawed but I don;t see where. This is an Elevator approach in my limited understanding.


In the designer you have to set Virtual Screen 1 visible to true and all other vertical arrangements to false

Taifun

1 Like

Way Cool! Thank you so much! I thought those block commands would work in and of themselves. I was able to reduce the height of some arrangements in the virtual screen 1 so I no longer require a swipe or scroll to reach everything.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.