+1 888 340 6572 GET STARTED
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-662

wrong order reverse position

action_vote_minus_faded.png
5
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Reverse the order is placed on all orders, sales.
Ts2000i did not see the same behavior gif

Steps to reproduce this issue

open 5 minutes chart and enter the following code with the values ​​of buy and sell just below and above the current ones.Make sure you are long or short position.
I used the following code and place the result in reverse position and buy

if time >900 then begin
buy("buy1") next bar 1215 limit;
buy("buy2") next bar at 1212 limit;
buy("buy3") next bar at 1212 limit;

end;
if time >900 then sellshort next bar 1230 limit;
if time >900 then sellshort next bar 1231 limit;
if time >900 then sellshort next bar 1232 limit;

setexitonclose;

Comments (6)
#0
user-offline.png  MultiCharts Support (MultiCharts)
Oct 19, 2011 - 15:07

"Sellshort" is used to reverse. if you want to close long position, use "sell".
Buy -> Sell
Sellshort -> Buytocover

#0
user-offline.png  fibdax (fibdax)
Oct 19, 2011 - 16:32

My intention is to reverse a position at a determined level, the position can be sized with a different number of contracts, from your answer it seems I need to give both instructions for every single contract to be closed (sell) and to be then reopened short (sellshort), this logic is not present in TS as the entry instruction (sellshort) is sufficient to close all long positions and to leave the specified quantity short, I also had a try with the double instruction but, as you can see from attached gif, it does not work either

#0
user-offline.png  MultiCharts Support (MultiCharts)
Oct 20, 2011 - 19:03

I have transformed this bug report into a feature request.

In TS it works different way than in MC:

Assume, that a signal entered long by 2 with 2 contracts and reverse orders are generated.
The script generates following reverse orders:
If Marketposition > 0 then
begin
 Sell short("sell1") 1 contract next bar at 28 limit;
 Sell short("sell2") 2 contract next bar at 29 limit;
 Sell short("sell3") 3 contract next bar at 30 limit; 
end;

MC will send to broker the following:
sell 3 contracts @ 28 limit
sell 4 contracts @ 29 limit
sell 5 contracts @ 30 limit
TS will send the following:
sell 1 contracts @ 28 limit
sell 2 contracts @ 29 limit
sell 3 contracts @ 30 limit
sell 2 contracts @ 28 limit

#0
user-offline.png  fibdax (fibdax)
Oct 20, 2011 - 20:47

From your words I understand you are asking to transform the procedure as it is in TS, actually MC solution leaves some doubts as to place the same additional quantity at every level is sort of nonsense, in case of fast move of the market all contracts would be executed leaving an excessive quantity of contracts in the market

#0
user-offline.png  MultiCharts Support (MultiCharts)
Oct 21, 2011 - 12:50

We understand your point, Sir. We are planning to implent a feature in one of future versions of MC that will allow you to choose between how it works now in MC and and how it works in TS. There is no eta yet, but according initial estimation it may be implemented in 2-3 months, Sir.

#1
user-offline.png  MultiCharts Support (MultiCharts)
Aug 01, 2018 - 19:57
Changes:
  •   icon_milestone.pngMilestone changed: MultiCharts Future Releases => MultiCharts 8.0 (RELEASED)
  •   icon_status.pngStatus changed: Confirmed => Released
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    MultiCharts 8.0 (RELEASED)
  • Status
    Released
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (3)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates