How to open multiple Stata

[wawa-wahoonito]

I would like to run multiple programs at a time. For example, if I open two ST3 windows (not two tabs) under two different directory for two projects, I would hope ST3 would initiate two Stata windows and run them simultaneously. However, project #2 will cut #1 short on the same Stata window. Is there any way to work around this? Thank you!

[mattiasnordin]

Unfortunately, that is not possible at the moment. See also issue #25.

[fredericky123]

Is there any update? I really hope this function can be realized.

[flcong]

I am thinking about adding this feature in StataEditor. The following is my plan for the intended features:

• Create two modes for executing Stata commands: the lock mode and the free mode. If there is only one Stata session running, then there is no difference between the two modes and Stata code will be sent to the unique Stata session. If there are more than one Stata sessions running, then:
  • in the lock mode, for the first time to send code, the user is asked to select a Stata session to lock into. Stata sessions are identified by the title of their main window. Typically, the first Stata session has title "Stata/MP 17.0", the second one has title "2 - Stata/MP 17.0", etc. and the title does not change afterwards. Hence, the user can easily identify which session to send code to and choose accordingly. After that, all commands will be sent to the locked session. The user is also allowed to change the locked session.
  • in the free mode, any time the user is executing commands, he/she will be asked to select a Stata session to send code.
• In my opinion, for a typical user, the lock mode will be preferred, especially for step-by-step data processing or analysis. For the free mode, I only see an application when the user has to switch between different sessions frequently. So I think the default one should be the lock mode.

However, there is a choice to make about the implementation. There are two ways to implement, but both have their pros and cons:

• Use Stata Automation: This is similar to the current version, but users are allowed to launch multiple Stata sessions from Sublime Text through a command. The cons are:
  • Only Stata sessions launched from Sublime Text are identified. I have not found a way to get the COM Object of existing Stata sessions that are not launched from Sublime Text, e.g. launched by double-clicking on the short-cut or any dta file.
  • By launching Stata using Stata Automation, a COM Object is returned, through which commands can be sent and various information can be retrieved. However, I have not found a way to get the title of the Stata window through the COM Object. (All supported functionalities are listed here). It means that users have to remember the launching order of Stata sessions, which seems very user infriendly.
• Use Win32 API: In this approach, existing Stata sessions are identified by Win32 APIs that searches for processes with executable path matching stata_path in the settings. The titles of the Stata main windows (excluding Viewer or Data Editor windows) can be retrieved as well. Commands are sent to Stata sessions through sending messages to the Command Window in Stata. However, the con is that we are unable to benefit from extra features of Stata Automation, especially variable completion since Win32 API cannot be used to get variable list from Stata. (Maybe this can be achieved by secretly open the Data Editor and get variable names from the Variables panel. I need to check.)

If I cannot successfully get variable names through Win32 API, I think the optimal way is a hybrid of the two approaches:

• Use Win32 API to identify all Stata sessions and allow users to send code to any of them. However, among those launched through Sublime Text, users can benefit from extra features such as variable completion.
• When launching Stata from Sublime Text using Stata Automation, use a loop to detect any new Stata process with Win32 API. In this way, the title of the new Stata session can be retrieved.

If this sounds good, I'll try to implement and make a pull request. Any discussions or ideas are welcomed.

[fredericky123]

It's inspiring if this function can be implemented!