+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
bug_report_small.png
Open Bug report MC-2280

Signal setting made in PLEditor is lost in signal on chart.

action_vote_minus_faded.png
1
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
Two sissus

1. Settings set in PLEdior is lost.

2. Recompling signal clears "Use as Default" settings.
Steps to reproduce this issue
  1. create signal _s_test2, the template signal (File->new-new signal...), compile

  2. apply the signal.

  3. at the chart right button click -> Format signal -> format -> Entries

You will see Buy Entry -> Arrow as blue color, Size thin line.

  1. Cancel the Format Signal Window

  2. Remove _s_test2 signal from Format Object window and close the window.

  3. In PLEdior , s_test2 signal, right button click -> Properties

  4. Change Buy Entry-> Arrow to green color, Size the most thick. and click OK

  5. compile

  6. apply the signal to chart

you will see small blue arrow, it should be big green arrow.

At this moment, Properties at PLEditor has green thick, Chart has blue thin.
First issue, Settings set in PLEdior is lost have been proved.

Now, Second issue

  1. at chat, format the signal, Buy Entry -> Tick to Yellow, Tick Size to the most thick, Check "Use as Default", then click OK

  2. In Format Object windows Remove_s_test2, and click close

  3. apply the signal once more

You can see big yellow right arrow.
The "Use as Default" is alive.

  1. remove the signal from chart

  2. in PLEditor, right button click -> Properties

  3. recompile the signal

  4. apply the signal

Now,

Comments (3)
#1
user-offline.png  Khitan (chi jeongki)
Jul 26, 2017 - 08:37

Last part of my report was lost.

Now, the big yellow tick has disappeared.
This proves the second issue, Recompling signal clears "Use as Default" settings.

Two issue is related in that,

If there is no issue1, issue2 might be interpreted as precedence of "Use as Default" and "setting in PLEditor"

I see no "Use as Default" check box in PLEditor "Signal Properties" window.
People may interpret it as setting in PLEditor has higer precedence than current "Use as Default", so you have no choice, it will be the new "Use as Default" whether you want or not.

Then if I want to preserve my current "Use as Default" setting, I have to apply the signal to a chart and format it to pop up "Format Signal" window and compare these two properties windows. Very inconvienient situation.

I think "Use as Default" should have higher precdeence, when it is changed it should be reflected in properties in PLEditor.

Another opinion, the "Signal Properties" windows from PLEditor has nothing to do with the signal, there's no Inputs tab, its all about the shape and color common to all signals.
How about make check box "Use as Default" here and when I make a new signal, the colors and shape I check "Use as Default" come up, instead of MC's installtion default? I always change it, since my chart window background color is white, MC's installation default characters are white.

Version Info:

Version: MultiCharts .NET64 Version 11.0 Beta 2 (Build 14589)
Licensed: (Evaluation Copy)
UserID: 277941611

OS: Winows Server 2012 R2 English x64

#2
user-offline.png  Khitan (chi jeongki)
Jul 27, 2017 - 09:26
A file was uploaded. issue.aviicon_open_new.png
#3
user-offline.png  Khitan (chi jeongki)
Jul 27, 2017 - 09:59
A file was uploaded. issue.wmvicon_open_new.png
History
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    MultiCharts 11.0 (RELEASED)
  • Status
    Confirmed
  • Priority
    Not determined
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
  • Reproducability
    Not determined
Attachments (2)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates