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

Display number of charts and memory in a workspace

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

I am sure a large number of MC users have workspaces with overlapping charts. Many users have experimental workspaces, where we open/close and resize new charts all the time. It can become very difficult to remember all the open charts and such workspaces can become messy. Such charts can remain hidden for months, all this time wasting computer resources.

It will be very helpful if MC can display the number of open charts for a workspace. The best place to have such information displayed is the title bar of Multicharts. currently, it displays information like "Multicharts - Untitled Desktop - ES" when I am on my workspace with the name ES.

Typically, a workspace will have only 1 scanner and only 1 order and position tracker window, so specifying number of these in the title bar is not required. For completeness, title bar can also show number of DOM and number of time and sales window, along with number of charts.

So something like
"Multicharts - Untitled Desktop - ES - 4C - 2D - 0T&S"

if name of workspace is ES, and it has 4 charts, 2 DOM and 0 T&S open.

It would be great if title bar also displays the amount of memory used by a particular workspace.

So, maybe something like
"Multicharts - Untitled Desktop - ES - 4C - 2D - 0T&S - Memory 320MB"

Steps to reproduce this issue

New Feature Request

Comments (1)
user-offline.png  JoshM (Jura)
Oct 25, 2014 - 03:19

A valuable suggestion related to this feature request has been made by MichaelS: http://www.multicharts.com/discussion/viewtopic.php?f=1&t=46254&#p109623

Seeing the CPU usage might help locate performance issues.

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Under Review
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 (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates