component is not in the same session as the parent form.

Post any questions you have about using the Verj.io Studio, including client and server-side programming with Javascript or FPL, and integration with databases, web services etc.

Moderators: Jon, Steve, Ian, Dave

xren
Ebase User
Posts: 272
Joined: Fri Dec 14, 2012 2:55 pm
Location: Ottawa

component is not in the same session as the parent form.

#1

Postby xren » Tue Mar 19, 2013 3:32 pm

Hi,

I have a component with menu in it. Then I insert it into my forms in a project. The menu click should navigate to some forms in my project.

However, it seems that the session is new session after the click. E.g. my login user information disappeared.

Is that how component works?

What I really want to do is share and reuse the menu and have all the navigation share the same session? How can this be done?

Thanks,
Xiaoli
0 x

Steve
Moderator
Moderator
Posts: 423
Joined: Fri Sep 07, 2007 3:44 pm
Location: Sandy, UK
Contact:

#2

Postby Steve » Tue Mar 19, 2013 3:49 pm

Hi Xiaoli,

How are you navigating to the other forms?

Using goto form will create a new session and terminate your current form.

You might want to use call form instead.

Steve
0 x

xren
Ebase User
Posts: 272
Joined: Fri Dec 14, 2012 2:55 pm
Location: Ottawa

#3

Postby xren » Tue Mar 19, 2013 7:24 pm

Hi Steve,

It is my mistake on the script. It works fine now.

I have a question: will callForm cause performance issue if use it too often?

Thanks,
Xiaoli
0 x

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

#4

Postby Jon » Wed Mar 20, 2013 8:36 am

Call form uses more memory because it keeps all the state from the original form, because it's anticipating that you will return at some point. If you use call form repeatedly you will be stacking up lots of forms and using more memory. Exactly how much memory depends on your app and how much dynamic data it uses.

Goto form is OK to use. The differences between goto and call are that goto form will release the original form's memory, but the user cannot use the back button to go back to it.

Another possibility might be goto page - depends on your app. Then you just have lots of pages within a simple form. Only one set of state (memory) is created and the back button works throughout.

Regards
Jon
0 x


Who is online

Users browsing this forum: No registered users and 42 guests