+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-542

Multiple data series with tick data in same bar space for Tick, Contract, Point, and Renko charts

Go to the next issue (open or closed)
Go to the next open issue

When one use minute bars/candles with a three or two series chart setup both the Trade, Bid, and Ask is within the same bar/candle space. This makes analysis with Bid/Ask volume indicators look the same as when only using the Trade field with price indicators.
But, when using Tick, Contract, Point, or Renko charts with a multiple data series chart setup the bars/candles for the different series, I am tempted to say are all over the place ;) , gets painted side by side making the chart messy. This makes the indicators look incoherent. Another thing with the instrument itself is that it takes a lot of space compared to a single field chart setup, making it difficult to have a good overview and good feel for price behaviour.
Could you please make it so that Tick, Contract, Point, and Renko charts with multiple series from the same instrument with the same resolution settings comes within the same bar space just as with minute bars?

Steps to reproduce this issue

Insert both the trade, bid, and ask on a Tick, Contract, Point, or Renko chart with the same instrument and resolution settings with a real time feed. The bars for the different fields is painted side by side. Do the same with a 1 minute chart, and all three fields is within the same bar space as normal.

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