Screen Confusion... Which one to use and why

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!

Dora, you will be proud of me…

May be you will feel trouble after compiling app or during compiling or while opening the app. Sorry to say this.

(PS:If nothing happened as i said above then you are lucky)

1 Like

you might want to follow tip 1

Taifun

2 Likes

Thanks for that.

Unfortunatly I didnt begin that way som stuck with what I have… :frowning:

Can you imagine using one screen to handle the equivalent of 30 screens. Finding stuff will be an absolute nightmare… unless you have vays undt means, ja?

but provided one closes and opens every screen properly I can see no reason for any “memory” problems.

That is of course if the Kodular method of closing a screen has been well coded as to flush not simply close a screen

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