Panels vs Screens

Haskell shared this question 4 years ago

I'm a newbie so I'm still wrapping my head around JIM but I have been trying to save a screen state into memory and was suggested to use Panels instead. Now it appears that Panels do work, since they are all within the same screen, but is there any drawbacks about using panels like screens?

It appears the functionality is the same, i.e. create next button to go to next panel vs create button to go to next screen.

Just want to make sure I'm not heading down a rocky road if I use multiple Panels instead of multiple screen. Any words of wisdom?

Thanks in Advance!

Comments (1)


You won't be able to navigate through the panels like you would with the screens (by using the Screens pallete).

Personally, I would store the values you want to keep into variables 'OnPageUnload' and 'OnPageLoad' write the values in the screen.

You can use either option. Yours can work if you have a small amount of screens and have to keep track of the state of lots of screens.

The one I like is best if there are a small amount of things to keep track of.

I hope this helps you decide.