+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
bug_report_small.png
Open Bug report MC-235

barstatus(2) blocks orders

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

I have a chart with two instruments.  If I use the print statement to print barstatus, and then submit an order it works fine.  If I also print barstatus(2) the order is ignored.

Steps to reproduce this issue

Insert two instruments to a chart.  Use the following code.  Comment out the appropriate print statement and uncomment the other one to toggle between the two scenarios.
[IntrabarOrderGeneration = True]
variables:
    intrabarpersist ntick(0);
if LastBarOnChart_s and getappinfo(aiStrategyAuto) = 1 and getappinfo(aiRealTimeCalc) = 1 then begin
//    print (ntick," ",barstatus);                    // this does not block the order
    print (ntick," ",barstatus," ",barstatus(2));    // this blocks the order
    if barstatus >= 0 then begin
        ntick = ntick + 1;
        if ntick = 3 then print ("sellshort #1");
        if ntick >= 3 then sellshort ("#1") 2 contracts next bar at market;
    end;
end;

Comments (1)
#0
user-offline.png  Guest (Guest)
Apr 29, 2011 - 12:05

Hello,
any clue when a MC release will solve this issue? Very criticial for some strategies...
thanks

History
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    MultiCharts 7.0 (RELEASED)
  • Status
    Released
  • Priority
    Not determined
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
  • Reproducability
    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