Problem with forms they disapear

Classic Servoy
1

Hello, I noted a problem with Servoy.

When my solution start I open a form with an tabPanel where I put all my forms.
I have the “start” form that contain the menu, when i start to open a lot of forms my principal Start form, and also others forms, disaper.
I can see it on the form list but when I open the principal form that contain panels with sub forms I can see only one blank screen.

Is there any way to block servoy to delete my forms? It happen also when i have an edited foundset connected to a form, it just disapear.

Any suggestion?

Can i refresh the form?

thanks

2

UP

3

Are you loading the same form more than once?

4

No, every form is loaded one time only

5

Break it down and add one form to the load process at a time. I’m willing to bet you somehow use the same form twice somewhere. Even if not, this process will narrow the issue down.

6

If you open up a lot of forms that older forms that are not used for a while are unloaded
When you show them again they should just be reloaded again (onload called)

Servoy can’t just keep all forms in memory that would kill the client or server.

You can control it a bit, but be careful with that, that is keeping a form reference to a global (array) variable. so scopes.globals.mykeptform = forms.myform;

7

Thanks for answers.

jcompagner:
If you open up a lot of forms that older forms that are not used for a while are unloaded
When you show them again they should just be reloaded again (onload called)

Servoy can’t just keep all forms in memory that would kill the client or server.

You can control it a bit, but be careful with that, that is keeping a form reference to a global (array) variable. so scopes.globals.mykeptform = forms.myform;

when servoy destroy my form is there any way to call any methods? onUnLoad or something similar that i can intercept?

8

onUnload is called then yes.

9

so…if I do something like

function onUnload(event) {
     return false
}

if I interrupt the unLoad function?

10

no that will not work. Because onUnLoad is already processed when it is being destroyed.
in onUnload you could store state and that kind of stuff that you can reuse again in onLoad