+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-1657

Set commission/comission rules and slippage programmatically
action_vote_minus_faded.png
35
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

Currently we can define the commission (rules) and slippage in the Strategy Properties. However, it would be beneficial if we can also define these settings programmatically.

One of the benefits of that is that we can set the slippage depending on the time of day (backtest with 1 tick slippage during RTH, and with 2 ticks after hours, for example). This can also help with backtesting a portfolio.

(Based on the following topic: http://www.multicharts.com/discussion/viewtopic.php?f=19&t=46546 )

Steps to reproduce this issue

n/a

Comments (3)
icon-mono-settings.png
#0
user-offline.png vindiou (vindiou)
Jun 15, 2015 - 13:42

Changing the slippage from the code would be great.
According to the current instrument, current market conditions, volatility...

#1
user-offline.png KingCobra (kingcobra)
Oct 05, 2017 - 15:48

Excellent idea

#2
user-offline.png Mark Simms (Mark Simms)
Sep 14, 2022 - 19:07

This is a great idea.....please implement.

History
sidebar_collapse.png sidebar_expand.png
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
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