Screen Confusion... Which one to use and why

Try like this

2 Likes

nocando

tat would be nice, if you could but you CANNOT

It doesnt accept both???

Pls ref the 3rd post. Both blocks will not accept at a time. But we can do it in procedure. Try the procedure given in the above link

Sorry Dora, io dont understand


?

I know how to call procedures - no problem

so when I want to change screens I call the close_screen procedure. Ok so far

but where is the block you use with the place for the “result”

and what calls the smaller close_screen and why both?

t

animation20

1 Like

there goes Dora, Making her own blocks. Brilliant

never in a million years would I ever have thought to do that :grinning:

1 Like

Put this procedure and screen name in
When. BtCancel click

where is this “GET” block

T

Click the mutator :gear: and add add input

Thanks, silly me :slight_smile:

1 Like

yes, did that but the red block, I cant find it anywhere?

DONE :slight_smile:
done

oops Sorry got it

1 Like

Thanks

Now I get it.

Guess a there are a LOT of apps out there with millions of open screens :slight_smile:

Thanks Dora, you are too kind! :slight_smile:

2 Likes

No so fast…

What if you need to send a START_VALUE to the new screen?

Modify procedure

1 Like

Brilliant!

Thank you so VERY VERY MUCH

What would I do without you???

t

(PS. Im keeping those blocks in my “backpack”, FOREVER)

but you do realise what this means… Ive got to go though the entire app and change EVERYTHING, AGAIN??? :-((

1 Like

If you do with procedure then you will less pressure

yes, the app is coming out to around 30 screens and each screen calls another screens, so EVERYTHING AGAIN!