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

Kagi charts do not process orders on the forming bar.

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

!!!FIRST - FIX THIS PAGE TO SAVE WORK IN PROGRESS ---IF YOU CHANGE ANY OF THE CATEGORIES ABOVE IT DELETES WHAT YOU HAVE TYPED!!!!!!!!!!!!!!!!!!!!!

Typing this for the second time--- I wrote a script to trade using a Kagi chart. Buying when that chart reached its low and selling short when the chart reached its high. Though the bar had reached its low or high point it would often "whipsaw" to the new bar several times before becoming fixed. Only on rare occasions do I recall the bar going below the low or high once this occurred.

However, sell/buytocover and buy/sell orders will not activate until the new bar is fixed. By this time the price is usually (above the low)/(below the high) when this occurs resulting in bad entry pricing.

Also, on the rare occasions when the new bar whipsaws back and forth below the entryprice the stoploss order to sell when the close is less than the entryprice will not execute---causing a loss.

The chat room people told me that Kagi will not issue orders until the bar is set. I thought that using a "marketiftouched" order would be a work-around to solve this problem but was told that this function does not work in MC.

I would like to use Kagi charts in automated trading, but it is essential to have the orders execute at the HIgh/Low and have the Stoploss execute to limit losses.

Steps to reproduce this issue

Just run the Kagi in an active market at any resolution and you should see it.

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Performance
  • Targeted for
    Not determined
  • Status
    Not Reviewed
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
    Critical
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