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

Corrupted "Base Study On" labels

action_vote_minus_faded.png
3
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

It appears when I have many plot windows in a workspace (eg, 6) and I turn off the Status Line" in Format Window, I see corrupted text in Format Studies -> Format -> Properties. I've attached two sample pictures showing what I mean. When I re-enable the Status Line the problem goes away.

Steps to reproduce this issue

Create a workspace with one plot. Add the Fast Stochastic Indicator. Format Windows -> Status Line, then uncheck the Enable Status Line check box. Copy and Paste the window 5 times to end up with six plot windows of the same time. Save the workspace. Exit MC. Restart MC and for each plot do: Format Indicators -> Format -> Properties. One or more of them will have corrupted text for the "Base Study On". Check the Enable Status Line in Format Windows and the corruption is no longer there.

Comments (1)
#0
user-offline.png  janus (janus)
Oct 07, 2011 - 22:16

Well, I can reproduce it on two computers.  One is a Windows 7 Pro 64-bit, the other a Windows 7 Starter 32-bit.  I'm using instrument root code YN (mini DOW futrures) on exchange ECBOT.  I've attached the workspace named aaa.wsp.

History
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    MultiCharts 7.2 (RELEASED)
  • Status
    Released
  • Priority
    Not determined
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
  • Reproducability
    Not determined
  • Severity
    Critical
Attachments (3)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates