Hi,

I am currently performing a backtest on a large dataset with evolving watchlist etc.
It is already running 24 hours and I guess it will take some more days to complete.

Since WL5 can only be opened once, backtests run in conflict with my realtime day-to-day work in WL5.
I cannot open workspaced for example without stopping the backtest.

Therefore, the ability to run WL5 in more than one instance is a feature that is essential for working with WL5 in realtime.

regards,
dansmo

QUOTE:
I cannot open workspaced for example without stopping the backtest.

No, you can.

QUOTE:
the ability to run WL5 in more than one instance

FAQ | "Missing" features

QUOTE:
No, you can.

Hmm. We just did the test.
Running a backtest in one window and open a workspace will definitely close the backtest window.

QUOTE:
Running a backtest in one window and open a workspace will definitely close the backtest window.

Something new. How exactly did you open a workspace (there are several options)? Which stage the backtest was in?

P.S. Please do me a favor, don't shout with "!!!", thank you.

QUOTE:
Something new. How exactly did you open a workspace (there are several options)? Which stage the backtest was in?

Workspaces --> Open Workspace
The backtest was - in this case- running on one symbol and executing.

It was a new, blank workspace window that close down an executing strategy window without a trace? Hard to believe, never seen anything like that in 3 years. Or your description is missing something.

I have a saved workspace with two charts. I opened that one resulting in the other window being closed.

Obviously, "Open workspace" loads a saved Workspace, closing all the stuff in the current workspace window. What'd you expect?

You should have created a new Workspace window and loaded the saved workspace there, leaving the strategy window in the first workspace running. This way, nothing gets closed in the first workspace.

I inserted a Thread.Sleep() delay in a Strategy running in the first workspace to simulate a slowly executing code and -- exactly as expected -- creating a new one and loading a saved workspace did nothing to the first one.

Eugene, believe it or not:
(maybe because I am sometimes still used to think in v3 terms)

I did not even notice that there is something like "New Main Workspace Window".
I am very sorry for taking your time on this one!

No problem Daniel. Now you know there's more flexibility.