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

Unable to Change Instrument on Chart with 2 linked series of same instrument

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

On a chart with two data series of same instrument, llinked to each other, using exchange time, it is not possible to change to a different instrument from a different exchange/Time zone. The error message says: 
"Instruments from different time zones cannont be mixed. Please select local Time Zone on all instruments"
However, it is not possible to select local Time Zone on all instruments as requested.
This is related to issue MC-227 and issue MC-747 and is present in MultiCharts Standard Edition up to 8.5.

Steps to reproduce this issue
  1. Create new chart window
  2. add instrument @ES# from IqFeed (say 30 min bars), set to Exchange Time
  3. add instrument @ES# from IqFeed (say Daily bars), set to Exchange Time
  4. In Chart Window Link the two instruments together
  5. Format instruments and change instrument #1 to @NQ# from Iqfeed and verify that it works as expected.
  6. Format instruments and change instrument to either @NG# or @QM# or AAPL from Iqfeed. Verify that it doesn't work and you get an error message.
  7. Now try to selectthe time zone to Local Time. Verify that it is impossible to do this. No matter what you try.
  8. Verify that the only way to change the instrument is to remove everything and start from scratch or create a new chart window.
Comments (1)
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Oct 02, 2013 - 03:10
Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 8.8 (RELEASED)
  • Status
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
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