MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+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-2687

Portfolio Trader cannot set 1 max contract/position

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

In the newest MultiCharts64 Version 14.0 Release (Build 21357) in the Format Settings of a strategy in Portfolio Trader, the Maximum shares/contracts per position cannot be set to 1 (one).
If this is by design then why can't a futures strategy be limited to only holding one contract per position like every other version? If you try to set this value to one then a dialog box displays an error message that says the maximum number of shares/contracts per position must be greater than 1 and less than or equal to 1000000000.

Steps to reproduce this issue
  1. Add a new strategy to Portfolio Trader.
  2. Add an instrument.
  3. Add a signal.
  4. In the strategy format settings, open the Properties tab and set Trade Size to 1 Fixed Shares/Contracts.
  5. Uncheck Allow up to x entry orders in the same direction as the currently held position.
  6. Set the Maximum shares/contracts per position to 1 (one)
  7. Try to save the Format Settings window.
Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Investigating
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
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