MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+1 888 340 6572 GET STARTED
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-585

Add Broker/data feed connection status on the status line of the main window

action_vote_minus_faded.png
6
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 would be very helpful to see the Broker/data feed connection status on the status line of the main window. In the case that a Broker/data feed connection makes any trouble, a trader wishs to know this critical issue immediately. Furthermore it is very informative to know to which Broker/data feeds someone is currently connected without opening the menu option File -> Broker Profiles. By the way, NinjaTrader displays the broker/data feed connection status on the status line of their application.

Steps to reproduce this issue

Use MCDT 7.0.66.400 (final release from 15.07.2011).

Comments (1)
#0
user-offline.png  JoshM (Jura)
Dec 10, 2011 - 13:21

This is an excellent idea, especially for traders who, like me, have the TradeBar closed and thus cannot see the "connection color lights". It would be very helpful if these can be displayed in the statusbalk.

Thanks for making this request Disputin.

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
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