+1 888 340 6572 GET STARTED
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-1114

AutoLoad Workspaces based on Command Line Parameters

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

Many power users open multiple instances of MC on their computer (one for each monitor), its better to do this than to detach a chart and move it because MC itself acts as a container.
Anyway, Its bad for 2 instances to have the same open workbook. So, users must open each instance of MC then by hand open whichever Workbooks they want in each instance. 
It would be great if you can have a command line paramater that can list the workbook names for it to autoload. Then I can have a different command line for each instance on each monitor.

Steps to reproduce this issue

see above

Comments (1)
user-offline.png  MultiCharts Support (MultiCharts)
Jun 18, 2013 - 08:44

Create an additional MC icon on your desktop to have 2 icons of Multicharts. Make a right-click on the first one and click on "Properties". In the "Target" field you should have the the path in quotes to MultiCharts exe and paths (with a spcae and in quotes) to the workspaces you want to be opened with this insctance. The same for the second MC icon. Example:
For the first MC icon: Target: "C:\Program Files\TS Support\MultiCharts64\MultiCharts64.exe" "c:\Temp\workspace1.wsp" "c:\Temp\workspace2.wsp"
For the second MC icon: Target: "C:\Program Files\TS Support\MultiCharts64\MultiCharts64.exe" "c:\Temp\workspace3.wsp" "c:\Temp\workspace4.wsp"

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