I am trying to use the escape button on client event to go back to the previous page.
I have the escape button scripted in the client events that has system.nav.goback().
This doesnt seem to work. Is there another way to do this?
Thank you
I am trying to use the escape button on client event to go back to the previous page.
I have the escape button scripted in the client events that has system.nav.goback().
This doesnt seem to work. Is there another way to do this?
Thank you
Hi Brian,
To clarify, do you mean the 'esc' button on a keyboard or is this a button on the client window? Could you post the script you have and where it is set up in your project?
Under client events
Escape (Released)
system.nav.goBack()
Button on keyboard
Hey Brian,
Have you tried using any other keys besides escape to test this functionality?
Yes i have. Backspace and spacebar. Also just tried B just to make sure.
It seems that this question should have been tagged as "vision" specific. You can edit the title to add the appropriate tag to attract the right experts.
I use the key released event handler to close popups with the escape key, and I've never had a problem, but I don't use system.nav.goback() for backwards navigation. It seems like I tried this some time ago and didn't get the results I wanted.
In any case, I just set up an experiment, and no matter where I navigate, I get this in my diagnostic console whenever I call system.nav.goback from the escape key:
Nevertheless, I do have a strategy in place for reverse navigation that works quite well. I use templatized navigation buttons that simply add the windows they call to a dataset client tag. Then a back button can retrieve the previous window from the dataset and open it. Furthermore, this allows the client can access the full session history in a power table and navigate directly to any previous window with a mouse click.
Sorry for the late response. I was shifted to another project for a while but am back on ignition.
Can you provide an example. I move multiple parameters between windows.
Thanks
Well, that certainly complicates things. All I do is use a client dataset memory tag, and I use templatized navigation buttons that add the window path to the dataset to create a history for the client session. The templatized back button navigates that history in reverse. I don't use the history for parameterized windows, but I suppose parameters could be saved along with the window path by simply adding columns to the dataset.