+1 888 340 6572
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-1497 » Open Feature request MC-724

Allow to give a specific price to orders from code (Orders)

action_vote_minus_faded.png
12
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

Once my stratgy order is sent, i want to automatically send a stop loss and target profit at the same time on the same bar but not in dollar value. I want it to be based on price....multicharts shoult have this option available.
 
Please update this

Steps to reproduce this issue

There is no reserved word or option. You can ask support and they said to post it here so people can vote on it and get it fixed.

Comments (1)
#0
user-offline.png  Guest (Guest)
Oct 06, 2014 - 15:30

Following coding style is a workaround and will work fine for end of bar strategies.
I code such that after the line "buy next bar at EnterPr stop" On the next bar, I confirm if the price has breached the condition to enter into an order and if it has then I send stop and limit orders. So, I code something like
if H >=EnterPr then sell next bar at EnterPr + 20 limit;

if H >=EnterPr then sell next bar at EnterPr - 30 stop;

Above style of coding works when it is ok to set a limit/stop price on next bar, after the entry has happened. An example would be : if you are trading ES using a 5 minute bar and can afford to set stop and limit beyond 7-8 points, then this strategy will work. Because ES seldom makes a 7-8 point move within a 5-minute bar. However, this will not work with tight stops and targets like 1-3 points.
Hope above helps someone.

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Postponed
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 (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates