+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
Closed Feature request MC-1038

[PowerLanguage Editor] Show contents of .pla file before importing

Go to the next issue (open or closed)
Go to the next open issue
icon_info.png This issue has been closed with status "Released" and resolution "Not determined".

Currently if the user wants to import a PowerLanguage file that contains functions, signals, or indicators that are the same as already existing files, these old files needs to be overwritten if the user want to import the new files.

This is very user unfriendly, very annoying, and honestly, also quite unprofessional (hence the 'critical' status). Since by not being able to see the code BEFORE importing it, we'll just have to trust that the new code (that overwrites the old one) is correct. Since we can't see what we're actually importing (aside from the name of the PowerLanguage file), we just have to belief that it will be a good idea to override existing files. Worse yet, there's no undo option, after overriding the existing files.

So, I'd like to suggest a feature that shows us the contents of .pla file before importing it. That way we can actually see what we're importing and will be able to copy-paste the code to another file so nothing needs to be overwritten.

Steps to reproduce this issue


Comments (2)
user-offline.png  LRP (LRP)
Sep 11, 2012 - 05:10

Very usefull idea!

user-offline.png  Smokless (Smokless)
Feb 09, 2014 - 09:00

another idea always have 'Date'  field to select pla file ;)

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 10.0 (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