MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+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
feature_request_small.png
Open Feature request MC-1021

Allow sorting of columns in the Order and Position Tracker

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

I'd like to have the option to sort the OPT columns based on the instrument name, or the current strategy position (which is then, for example, resorted every 15 seconds).

This way, when the user has multiple strategies enabled, the sorting of the OPT will make the information better and quicker readable. For example, if you have a strategy active on 15 symbols, you'll currently need to make an OPT window at least 15 rows high. But if it would be possible to sort on the Strategy Position of a signal, a lot less cluttering space is needed and it will be possible to see at a quick glance which symbol has an open position and which not.

(Note: this feature request is for MC 8.0, not 7.4, but 8.0 can't be selected yet when making a feature request).

Steps to reproduce this issue

N/a

Comments (1)
#1
user-offline.png  MultiCharts Support (MultiCharts)
Aug 08, 2017 - 16:04
You can select filters to view positions for the required instruments only.
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Partially Implemented
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
  • Resolution
    Not determined
  • Severity
    Normal
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