+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
Closed Feature request MC-1575

Real-time data in Market scanner from data source Metastock

action_vote_minus_faded.png
2
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
icon_info.png This issue has been closed with status "Declined" and resolution "Not determined".
Description

Its not possible to scan a market feed by the datasource Metastock.
Thats is really an issue for me beacuse I am on my way to move from Metastock to MultiCharts.
I still have my old Metastock datafeed which I have planned to use in the future.

Steps to reproduce this issue
  1. Add instruments from the Metastock datasources to scanner window.
  2. You will not see any close, volumes, etc. values
  3. But you values for rsi, rate of chg will show up, perhaps because they are calculated.
    The same behavior is for the datasource Free Quotes but here there is a real work around that hope really is remove in a new version.
    If you create an indicator that holds  like Plot1(Close); and add it to the window.
    But this doesn't work for Metastock.
Comments (1)
#1
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Jul 27, 2017 - 11:15
The values you are referring to are taken from the Status Line and received from the data source in real-time. MetaStock can only be used as a data provider for historical data by design.
History
Issue basics
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
    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