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-770

Create a TradeTime_s reserved word

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

Currently, the TradeTime reserved PowerLanguage word only returns the time of the last update in minutes (i.e. 9:23 am).

For more active strategies it's important to have the time of the last update with seconds included (i.e. 9:23:42 am).

For example, if the user uses TradeTime to monitor the connection with a data feed, in the current situation it can take up to 59 seconds before the TradeTime reserved word signals that there hasn't been an update for a while.

Steps to reproduce this issue

n/a

Comments (2)
#0
user-offline.png  JoshM (Jura)
Feb 23, 2012 - 06:55

Andrew, am I correct in saying that the Q_Time_s reserved word does the same as this feature request asks for?

If so, then this request can be closed since it's already there. :)

#0
user-offline.png  PatrickSocal (PatrickSocal)
Oct 17, 2014 - 07:17

Yes, I think this can be closed... q_Time_s gives you second resolution, and q_Time_Dt gives you millisecond resolution. In both cases, it takes the time from the datafeed, not from the bar or from the computer clock. 
So a nice application is measuring data lag... you can write: 
if GetAppInfo(aiRealTimeCalc) = 1 AND LastBarOnChart then begin
ClockDiffSec = (computerdatetime - q_time_dt) * 86400;
end;
And unless I'm mistaken it will compute the clock offset (in seconds) between your computer and the datafeed (but only during real-time trading).

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
    Critical
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates