I wouldn't bring commission into this discussion, but setting a trade entry on the day after an exit surely would account for some slippage if the closing price on day two could be regarded as the next tick compared to the closing price on day one. But of course this would only be the case if you don't have intraday prices and/or the open, high, and low. That's why I thought the File/Preferences/Tick Slippage could be a solution to the problem mentioned above.
In my case a trade signal is given when the price series crosses all defined Moving Averages: A long(short) position is exited and a short(long) position is entered.
This signal appears on the same day, so why is the entry for the new trade set for the next bar by default? (This is a Rule-Based / Drag+Drop designed strategy).
I'd gladly attach a screenshot of the rules if someone could give me a hint on how to do this. And yes, I've noticed the IMG button...
A suggested solution under "How to create a stop-and-reverse system in a Rule-based stratety" was to allow for Multiple open Positions under Position Management, but as mentioned this does not work well for strategies with multiple conditions. What happens for multiple conditions is that a new long(short) position is entered each and every day the price series is above(below) the averages. Though that sounds like a lot of fun, it's not what I'm looking for.
One of my last options seems to be the suggestion under "WealthScript Techniques | Creating a Stop-And-Reverse (SAR) system" that states that [...the very first trade should be processed individually by making a check for Positions.Count equal to zero.] Unfortunately I'm not sure how to do this although the code looks pretty simple. I've included it at the end of the post.
Being that script editing is the only solution to this problem I find it hard to understand why The Stop-And-Reverse option which existed in legacy versions of Wealth-Lab was removed for the purpose of simplification...
I'm grateful for any suggestions, and I hope you'll forgive me for the extreme length of this post.
CODE:
Please log in to see this code.