GetTimeFrame not working for TimeFrame(Default)

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #184833 quote
    JS
    Participant
    Senior

    GetTimeFrame returns always -1 when applied to TimeFrame(Default)

    #184839 quote
    Nicolas
    Keymaster
    Master

    yes that’s still the case for IG, it has been fixed already in software version. I think that version will come very soon for IG users.

    JS thanked this post
    #184841 quote
    robertogozzi
    Moderator
    Master

    This topic has already been delt with at https://www.prorealcode.com/topic/help-with-gettimeframe-and-timeframe/#post-184824.

    Please do not double post. Thank you 🙂

    JS thanked this post
    #184851 quote
    pableitor
    Participant
    Master

    Besides the default TF, I think GETTIMEFRAME has   yet another bug in the monthly TF !   For example if we run this code:

    timeframe(1 month)
    c = gettimeframe/(60*60*24) // days per month
    return c
    it should return the number of days of the actual month but it will return 30 days for every month no matter what.  I guess this bug will propagate to the quarterly  and yearly TFs,  but I didnt test those.
    #184856 quote
    robertogozzi
    Moderator
    Master
    1 month is always 1 month, no matter if 28, 29, 30 or 31 days are in it. The GetTimeframe keyword is only used to let you know what TF you are using, not how many days are in it.
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.

GetTimeFrame not working for TimeFrame(Default)


ProBuilder: Indicators & Custom Tools

New Reply
Author
author-avatar
JS @js Participant
Summary

This topic contains 4 replies,
has 4 voices, and was last updated by robertogozzi
4 years, 1 month ago.

Topic Details
Forum: ProBuilder: Indicators & Custom Tools
Language: English
Started: 01/07/2022
Status: Active
Attachments: No files
Logo Logo
Loading...