run multiple Atlantis sessions (instances) simultaneously?

[Leopoldus]

Hi!

Many (AFAIK actually the most) Windows applications let a user run multiple instances of the all simultaneously (say, being installed in different folders or using different INI-files etc). Some others, say, Mozilla FireFox, need to use a special keys in the command-line in order to get the second instance started.

Is there some trick to make Atlantis to run multiple sessions at once? I've tried, but starting the second atlantis.exe only activates the existing window of already running instance of Atlantis.

Thanks!

[Robert]

You can install different versions of Atlantis into different folders and run them concurrently. You can launch two or more instances of the same version of Atlantis with different command-line switches, and run them concurrently. For a description of the available switches, have a look at Command-line Parameters

But be careful which switches you are using (they might have conflicting aims), and which running instance you are shutting down last. The running instance that you will close last will generally be the one saving any information to the Windows registry or to an INI file if you have chosen that mode.

Are there any particular reasons why you want to run several instances of Atlantis concurrently? If you told us what you are trying to achieve, we might help you more appropriately.

[Leopoldus]

You can install different versions of Atlantis into different folders and run them concurrently. You can launch two or more instances of the same version of Atlantis with different command-line switches, and run them concurrently. For a description of the available switches, have a look at Command-line Parameters

Hm... Which specific parameter do you mean? I've just reviewed every command-line switch at the page you have referred to and was not able to find any proper key.

The running instance that you will close last will generally be the one saving any information to the Windows registry or to an INI file if you have chosen that mode.

Thus the only reasonable working solution (if any) would be to run every Atlantis app instance from different folders and/or with different INI-files and not to use Windows system registry at all.

(BTW, some application use another approach, they let a user to specify in the command-line or Windows shortcut properties, which system registry branch to write in and read from. So I can use the both with system registry, what is generally better and faster way to handle settings, than INI-file on a storage device. It works this way:
C:\Program Files\App\app.exe /reg:mytest01
C:\Program Files\App\app.exe /reg:mytest02
etc)

Are there any particular reasons why you want to run several instances of Atlantis concurrently? If you told us what you are trying to achieve, we might help you more appropriately.

There are two independent reasons for me to run several Atlantis instances simultaneously, the both are quite obvious.

One is for testing purposes. When I wish essentially change Atlantis settings, say, the look, hotkeys, interface etc, it is very convenient to have the second (or more) Atlantis running with its default or my previous settings to decide, which configuration is actually better. As my monitor is large enough, I'd even like to tile the both Atlantis' windows on the screen side by side to compare the look.

Another purpose is caused by the fact, that I use Atlantis both for private remarks and for work documents. Up today I was forced to have private and work documents share the same window and the same defaults settings. But actually it is not reasonable nor convenient, especially in my case, where tasks, templates, storage folders, even used languages set, file formats, fonts being used, etc etc - in a word, everything is very different with my private and my work documents. Now I have to have the single configuration for all cases, thus I need in the beginning of work with every my document to waste my time in order to review and change some settings. So you should understand my wish to have a separate Atlantis instance for private and work documents handling.

[DaleDe]

I didn't seem to have any problems running

Atlantis -lsi

and Atlantis -lsr

although the -lsi needs a ini file. I didn't run it long.

You could even make two shortcuts with different options to avoid using the command line.

Dale

[Leopoldus]

I didn't seem to have any problems running
Atlantis -lsi
and Atlantis -lsr
although the -lsi needs a ini file. I didn't run it long.

Ah, I see now too, thanks.

Did you use it with the single atlantis.exe or run several different exe-files from different folders?

[Robert]

One is for testing purposes. When I wish essentially change Atlantis settings, say, the look, hotkeys, interface etc, it is very convenient to have the second (or more) Atlantis running with its default or my previous settings to decide, which configuration is actually better. As my monitor is large enough, I'd even like to tile the both Atlantis' windows on the screen side by side to compare the look.

To launch Atlantis with its default “out-of-the-box” settings, you can use the “Launch a test copy of Atlantis with factory settings” command as available from the “Tools | Factory Settings…” dialog. You’ll get two running instances of Atlantis, the first with your current settings, the second with the Atlantis “factory settings”. Please have a look at Factory Settings

Another purpose is caused by the fact, that I use Atlantis both for private remarks and for work documents. Up today I was forced to have private and work documents share the same window and the same defaults settings. But actually it is not reasonable nor convenient, especially in my case, where tasks, templates, storage folders, even used languages set, file formats, fonts being used, etc etc - in a word, everything is very different with my private and my work documents. Now I have to have the single configuration for all cases, thus I need in the beginning of work with every my document to waste my time in order to review and change some settings. So you should understand my wish to have a separate Atlantis instance for private and work documents handling.

Here is how I would go about this.

A. Atlantis Word Processor for private work.

1. Have only one instance of Atlantis running. Adjust its settings as suitable for your “private” work.
2. Press the “Save To File…” button at the bottom left of the “Tools | Options…” dialog.
3. Give this INI file any suitable name (e.g. “PrivateAWP.ini”), and save it.
4. Close Atlantis.
5. Create a shortcut on your Windows Desktop, Start Screen, Start Menu, Quick Launch Bar, or anywhere convenient, with the following command-line:

Code: Select all

"C&#58;\Program Files\Atlantis\Atlantis.exe" /dss /lsi /sfn "C&#58;\Users\<User Name>\Documents\Atlantis\PrivateAWP.ini"

The “/dss” switch means “DontSaveSettings” on close. In this way, you’ll be able to change settings on-the-fly during a session, and keep these changes temporarily. If, on the contrary, you want to save your setting changes more permanently, simply press the “Save To File…” button at the bottom left of the “Tools | Options…” dialog, and save the changes to “PrivateAWP.ini” (with overwrite).
The “/lsi” switch means “LoadSettingsFromIni”, and combines with the “/sfn” switch which means “SettingsFileName”. In this way, Atlantis will both read and write settings from/to the "C:\Users\<User Name>\Documents\Atlantis\PrivateAWP.ini" file.
Note that, depending on your personal Windows setup, you might have to adjust the paths in the above command-line. You will also need to replace “<User Name>” with the appropriate value.
6. You can then use this shortcut to launch Atlantis with your “private” settings. These “private” settings will remain unchanged until you choose to do so yourself if you overwrite your “PrivateAWP.ini” file. This Windows shortcut could be named “Private Atlantis”.

B. Atlantis Word Processor for public work.
The procedure is the same. You only need to save adequate settings to a different INI file.

1. Have only one instance of Atlantis running. Adjust its settings as suitable for your “public” work.
2. Press the “Save To File…” button at the bottom left of the “Tools | Options…” dialog.
3. Give this INI file any suitable name (e.g. “PublicAWP.ini”), and save it.
4. Close Atlantis.
5. Create a shortcut on your Windows Desktop, Start Screen, Start Menu, Quick Launch Bar, or anywhere convenient, with the following command-line:

Code: Select all

"C&#58;\Program Files\Atlantis\Atlantis.exe" /dss /lsi /sfn "C&#58;\Users\<User Name>\Documents\Atlantis\PublicAWP.ini"

The “/dss” switch means “DontSaveSettings” on close. In this way, you’ll be able to change settings on-the-fly during a session, and keep these changes temporarily. If, on the contrary, you want to save your setting changes more permanently, simply press the “Save To File…” button at the bottom left of the “Tools | Options…” dialog, and save the changes to “PublicAWP.ini” (with overwrite).
The “/lsi” switch means “LoadSettingsFromIni”, and combines with the “/sfn” switch which means “SettingsFileName”. In this way, Atlantis will both read and write settings from/to the "C:\Users\<User Name>\Documents\Atlantis\PublicAWP.ini" file.
Note that, depending on your personal Windows setup, you might have to adjust the paths in the above command-line. You will also need to replace “<User Name>” with the appropriate value.
6. You can then use this shortcut to launch Atlantis with your “public” settings. These “public” settings will remain unchanged until you choose to do so yourself if you overwrite your “PublicAWP.ini” file. This Windows shortcut could be named “Public Atlantis”.

Finally, note that there is an alternative solution to the use of INI files. You could log on to Windows under a different user name depending on whether you want to do “public” or “private” work. In this way, the settings used by Atlantis would be different depending on which Windows user is currently logged on.

HTH.
Cheers,
Robert

[Leopoldus]

Robert

Thank you very much for your detailed and fantastically clear (as always!) explanation or I'd rather say short manual. I'll try to arrange my work this way.

Thanks!