Multiple sessions or workspaces: feature request or clever hack?<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />I have a user asking about an easy way to basically save multiple sessions. We can save a single session, but can we save multiple sessions? I think he might be using projects, but finds it cumbersome. He wanted to just pick up where he left off on another project.
Re: Multiple sessions or workspaces: feature request or clever hack?Byron - yes, item #1 is one of the lacking features that I've heard complaints about!
Re: Multiple sessions or workspaces: feature request or clever hack?In response to Jeff's request for details and feedback:
I've used the Save Session quite a bit, especially when I thought a system crash was about to happen, or when a admin's "update software and reset in 30 sec" message pops up (used to happen more frequently outside of SAS.)
There are two things I would like it to do.
1. I would like it to automatically insert the exact date-time into the file name so that it won't overwrite the last saved session.
2. I would like it to save the table script for tables that have not been saved.
Re: Multiple sessions or workspaces: feature request or clever hack?Hi Laura,
To be clear, I suggested the Journal option because I like the flexibility it gives me to pick and choose which windows I pick up when I come back. I don't disapprove of Save Session Script... and I'm not recommending against it.
As for what Save Session Script does, as far as I know, it does exactly the same thing that saving a session on quit does.
It goes to each open window and gets the script to recreate that window and it's position.
There is nothing in JMP that will record everything you do in a session and then save a script to redo it all.
Can you provide any details on either the negative feedback you've received on the session scripts or the differences between the save session on quit and File->Save Session Script...?
-Jeff
Re: Multiple sessions or workspaces: feature request or clever hack?Thanks Jeff -
They had used the journal option, and projects, and wanted something different (hence the feature request ).
They want to pick up where they left off. The kind of solution sounds like "save session script", which they said other software offers (Origin software was the example they mentioned).
I'd like to understand what is different between these two versions of session saving (the built in one on quitting JMP versus the save session script command). I've had negative feedback on the "save session script" from users, and you are not recommending it either. In contrast, the built in "save session" that happens on quitting JMP works great.
For the "save session script", does that save everything a user has done while running JMP for that session? For example, if a user runs JMP all day, then saves the session script, does it capture the entire day's script? Or it is end point capture?
Any insight here? Thank you!
Re: Multiple sessions or workspaces: feature request or clever hack?You can choose File->Save Session Script... to save multiple session scripts, but I'd suggest opening a new journal and then right clicking in the journal and Add All Open Files.
That'll give him a nice organized place to pick up his work.
-Jeff
