Hi-
I've been enjoying this program immensely and I really appreciate how quickly you have addressed my questions.
There are some rules functions I do wish WLP had and would like to know if these may become available in the future.

Also if you may, can you help me with one item on a strategy I'm working with.

Thank you - Mike

pressing:
1. (code?) Sell at stop; I would like to specify the conditions for exit. (Specifically: if condition x, then sell at yesterdays low. If I'm correct, sell at channel low registers from the point of entry and not at the point the condition for sale is made. )

Wish list for WLP:
For rules: basic operators for price( also external symbols) and indicators ( of price and external symbols)such as abs value,>,<,=,+,-,/ and *; also, ability to set conditions for stop orders, e.g. as per my initial request for sell stop at yesterdays low.

1. We're struggling just to keep up with the releases, but please create a Support Ticket and select the Wizard Request category. We'll get to it eventually.

2. On the wish list, of course you can do all of this in code. The Wizard has limitations and combining series using DataSeries operations is one of them.

Cone- Thanks. done.

I'd appreciate if you can help me out with replacing - sell at market order with a sell at stop order; specifically If condition x then sell at yesterday's low.
I've tried to follow like examples e.g.cut and paste from "Two Bar Breakout"

CODE:
Please log in to see this code.

but I am not getting it to work.
I realize this may be straight forward stuff, but being new to learning this makes it a struggle.
It would be doing me a great service if you can.

If you post the code, we can help. Otherwise, whatever we give you may not work with the rest of the code around it and you'll be even more confused.

Can't imagine being more confused but here it is:
BTW: Advise- Best way to start getting a handle on this?

CODE:
Please log in to see this code.

For starters, if the condition to exit isn't actually based on data from the position and therefore is the same for "All Positions", then you don't have to test each Position separately to exit. Therefore:

CODE:
Please log in to see this code.

What's the condition that you want to add to this to sell at stop at yesterday's low? And, should it really be sell at Trailing stop at yesterday's low?

Yes Yes..

Two things.
1. I would like the stop exit to be trailing. Sell at stop at yesterday's low. ( Not at entry.)
2. The sell at close is NOT what I want. I only want to use this (trailing sell at yesterday's low) order, but only first after this condition is met.

CODE:
Please log in to see this code.

Thanks

1. Does the CumUp condition only have to be true once to enable the Trailing stop forever until exit?
2. Is there an exit if the CumUp condition is never true? An initial stop?

The CumUp condition only has to be true once to enable the trailing stop till exit.

If position is older than 30 days (second signal), sell at trailing stop from yesterdays low.

Cone- Basically I'm looking to let my profits run by not selling out at the market right away. That's why I'm looking to replace the sell at market with this trailing sell at yesterday's low stop.

It doesn't matter to me why you're doing something, but you have to understand that you must relate precise specificiatoins for programs, otherwise: 1) you won't get what you want, and, 2) you'll be asking me for continual changes, which we don't have time for.

QUOTE:
The CumUp condition only has to be true once to enable the trailing stop till exit.

See? This was not previously specified.

QUOTE:
If position is older than 30 days (second signal), sell at trailing stop from yesterdays low

Now we have to work on this ambiguous requirement. The design of your script tells me that you want to add a new Position at every new 5-day low, but sell all Positions at the same time. So, in the event that you put on, say, 10 consecutive Positions without having implemented a stop, from which one of those Positions should the 30-days be? I'll assume the oldest Position.

CODE:
Please log in to see this code.

Cone- I would have preferred to be more specific for you in order to avoid any ambiguity and resulting frustration. I,m trying my best and I realize you have allot to tend to and hate to think I'm wasting your time. You did ask for clarification on 8/10 which I believed I provided. I've been looking forward to getting this figured out. I thank you for your assistance and yes your assumption is correct, it is from the oldest position. Mike