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

Let PLEditor->Properties...->"Signal Properties" default setting to follow user's default setting.

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

Every time I make a signal, one of time consuming task is to change "Signal Properties" setting.
Current setting is targeted to black background color.
For example, in Entries tab "Signal label" is white, "# of contracts" is white.
in Exits tab, "Arrow" is white, "Tick" is white, "Signal label" is white, "# of contracts" is white.

There are users who prefer white background color in chart window.
They have to change all those mention above items from white to black or other colors, since white in white background hides their existence.

Users behavior might be using one setting for all signals, which is best targeted their chart background color.
Their "Use as Default" settings should be the one.

Please make a way for users to define their default setting of "Signal Properties" for all the signals they will make.

One of implementation would be, to remember last "Use as Default" setting of user, and use that setting for initial "Signal Properties" setting instead of MC installation default setting targeted to white background color of chart.

That should be the one which is best targeted to his chart background color.
Actually, I use only one setting for all of my signals.

Comments (0)
There are no comments
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
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