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

Expand color chart linking choice to unlimited please

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

Currently we only have 12 choices for chart linking colors. I have many identical workspaces for all the different currencies and other future markets that I may wish to open at any time. So if I happen to open a workspace with the same linked colors then both these workspaces change to the same symbol. Clearly a problem. I would suggest the following changes need to take place ASAP to overcome a fundamental flaw in the MC design:

  1. Expand the chart linking color choices dramatically;
  2. Make sure that when a symbol is changed in a workspace, that it does NOT result in any changes to OTHER workspaces;
  3. Allow a use to change the linked color on ALL charts (including hidden) within a single workspace only.

These changes are URGENT and very powerful. It will eliminate the current issues I am having and also save hours upon hours of having to unhide all my hidden data on each of a zillion charts in each workspace, change the linked color, then rehide all the data again. I cannot impress enough just how beneficial and time saving the above changes would be to end users.

Steps to reproduce this issue

N/A

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • 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