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

Allow Reload in Real-Time Market Scanner

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

When using MC with eSignal, for example, there is no easy way to update the Real-Time Scanner once the after-market close becomes available. At present, to get the windows to updatte you need to either delete all your symbols and re-insert them, or delete all the historical data for each symbol through Quote Manager - neither of which is a good solution.
The usefullness of the Real-Time Market Scanner would be improved if reload functionality was added.

Steps to reproduce this issue


Comments (4)
user-offline.png  orad (orad)
Jan 07, 2013 - 15:57

Voting up this feature suggestion. Totally makes sense to have Reload option for Market Scanner similar to reloading charted instruments (CTRL-R).
For now, this might be a workaround:
Close and reopen the Workspace that has Market Scanner

user-offline.png  Michael (Id2)
Aug 25, 2013 - 04:33

To close the workspace and open it again, doesn´t match the problem. We need a Refresh-Function for the Scanner. like ctrl-r in the Chart.

user-offline.png  David.Wong (fledgetrade.com)
Sep 16, 2013 - 00:53

Hope that the CTRL-R feature in market scanner will be available soon

user-offline.png  Michael (Id2)
Sep 16, 2013 - 13:05

You are welcome to learn about how new scaneer will work.

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