Help for screener, period in code

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #170871 quote
    UgurhanUgurhan
    Participant
    New

    Hello,

    I have a piece of code which works fine as indicator on the graphs but it doesn’t in screener code. Below is the problematic part:

    A = Close – Average [60](Close)
    B = Highest [360](A)
    Above only works in the screener if I reduce 360 to 196 and below.
    Any idea how I can get over with this?
    Many thanks
    Ugurhan
    #170872 quote
    JC_BywanJC_Bywan
    Moderator
    Master

    Current proscreener version is limited to 254 bars, so 360 is too much for the moment. I add “for the moment” because we are told the limit will increase in next version, but to anticipate the next question: no we haven’t been informed yet of a date release for it. It will most likely be significant news in proscreener forum when it’s out.

    (edit: topic moved on your behalf from “platform support forum” to “proscreener forum”, please see yellow box below, thanks)

    #170874 quote
    UgurhanUgurhan
    Participant
    New

    Many thanks!

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.
ProRealAI ProRealAI New

Stuck on this ProBuilder code?

Describe what this topic is trying to build, in plain English, and ProRealAI writes the ProRealTime™ indicator, screener or system for you.

Available in 7 languages
Try ProRealAI

Help for screener, period in code


ProScreener: Market Scanners & Detection

New Reply
Author
author-avatar
Ugurhan @ugurhan Participant
Summary

This topic contains 2 replies,
has 2 voices, and was last updated by UgurhanUgurhan
5 years, 3 months ago.

Topic Details
Forum: ProScreener: Market Scanners & Detection
Language: English
Started: 06/01/2021
Status: Active
Attachments: No files
ProRealCode ProRealCode
Loading...