Hi,

in WLD4 there was an open positions tab with a list of all the positions that were open on the last bar of the run. Is there a reason why this tab is no longer available in WLD6? I used this tab very much and would like to still use it in WLD6.

Whenever there isn't an obvious reason, the answer is "simplification".

I'd agree that it's a good Scans feature that the Strategy Monitor really does need. I'll put it on my wish list.

----
Just thinking out loud of how that would look -
The only thing that makes sense to me at the moment is that it would have to be a tabbed page that shares the Alerts pane. That way you could filter Open Positions by clicking on a Strategy or "Show All", just like Alerts.

What say you?

Hi Cone,

yes, good idea for the Strategy Monitor.
I would make it also available as a performance visualizer tab just like it was done in WLD4.

The Portfolio Inspector already does that job as a visualizer, for the current strategy. It's on the "Portfolio By Position" view.

If you mean to group open positions between separate strategies, then such kind of aggregation is not possible in performance visualizers (perhaps, unless you go out of your way devising workarounds).

@Eugene
There are mainly two reasons why the Portfolio Inspector does not work for me:

1. Open Positions in WLD showed Stop and Profit Target Levels; the tab is a very convenient way for dealing with daily trading since 5 years now.
2. The script runs slowly with > 500 stocks when PI is selected.

1. Displaying a position's stop and profit target levels, if assigned, may be an interesting addition to the PI. I'll put that on my long term list.

2. By the time the PI (and any visualizer) comes into play, your script has already finished working.

given that the PI would include stop and pt levels that would be okay with me then. However....long term. What do you mean by that?

This idea is now on my list of enhancements to consider or work on. There are lots of ideas, fixes and requests in the works but our manpower is limited. Usually I might know right away when some request can be implemented but not currently.

On second thought, it's not possible at all because WL6 doesn't expose the dynamic profit target and stop loss levels of a Position object. If the developers decide to expose these values, then it will be possible to use them in your own performance visualizer -- but not the Portfolio Inspector. Here's why.

The TrailingStop property, although already exposed, in performance visualizers (only) displays just the last assigned value. Showing just the final value might be just what doctor ordered for a custom "Open Positions" tab but would not be in line with the Portfolio Inspector's logic, because the stop actually could have been changing on each bar.

QUOTE:
On second thought, it's not possible at all because WL6 doesn't expose the dynamic profit target and stop loss levels of a Position object.

Do you discuss with the developers then? This is really a needed enhancement and the Alerts tab does provide that information anyway, so I dont see why those values are not exposed.

There are lots of more urgent, prioritized, and pending fix issues on the developers' schedule than this one. Fact: no one needed those values in performance visualizers up until yesterday. Since you're in control of your bar-by-bar stop/limit levels, Wealth-Lab only needs them for PlotStops. There's no urgent reason for exposing these properties.

What would work for your custom "Open Positions" visualizer is passing those values via the Position.Tag property in one shot just like instructed yesterday, HERE. It would work for the current Strategy window only, as aggregation of this data between different strategies would require you create a different design.

Okay, I´ll try it on my own.

This is the second tab that I added to my Visualizers. The first one appears in the list, however the OpenPositions one does not show. I know this is guess-work, but can you think of anything that is wrong here?
Edit:
I have found the problem. The reason was a minor error that did not show up when I created the dll.

Glad you found it. Some ideas to explore for other users with a similar issue:

1. public string TabText - if cloned another visualizer, make sure it's edited.
2. Targeted .NET 4.0 instead of .NET 2.0/3.5.
3. public VisualizerAppliesTo AppliesTo. Refer to API doc here.
4. Less likely w.r.t. visualizers yet worth taking a look: Wiki FAQ on Extension development

Three days ago I asked for the OpenPositions tab. I have almost finished it now, 1 Day after I decided to do it as my own visualizer.
Obviously I have to praise the developers of WLD for making the APIs available. This makes WLD a powerfull tool.
I wish they would open the other APIs as well.

Any particular one?

The Broker Adapater API.