Calling an indicator from a system

• 02/21/2021 at 6:48 PM #162266
  umebon

  I have tried a couple of things and it is when i add Timeframes in the indicator that the parsing-problem appear… anyone with a solution?

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 7:47 PM #162269
  Vonasi

  umebon wrote:

  When i change in my indicator it doesnt update, how do I save? Isnt autosave?

  Any changes will be saved if you add the indicator.

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
  02/21/2021 at 7:52 PM #162270
  Vonasi

  umebon wrote:

  it is when i add Timeframes in the indicator that the parsing-problem appear

  You said that you get the parsing problem with your ‘suck’ indicator but now you are saying that it only happens with TIMEFRAME in the indicator. I think you need to be a little clearer in exactly what the issue is.

  In the French topic that I gave a link to Nicolas clearly said that it was linked to the use of TIMEFRAME.

  https://www.prorealcode.com/topic/probacktest-error-parsing/#post-151414

   

  1 user thanked author for this post.

  umebon

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
  02/21/2021 at 7:59 PM #162272
  umebon

  Thanks for the help and I tried too code it with only indicators and no timeframes in the indicator file and then call them too timeframes in the system and got it too work. You guys are the best and I really like the way you support us newbies, keep up the good work!

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/22/2021 at 8:59 AM #162300
  Nicolas

  Avoid CALL ing indicators with TIMEFRAME in their codes. Embed their codes into the strategy instead. This is a current workaround until the MTF indicators is fully supported with CALL.

  1 user thanked author for this post.

  umebon

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20828

  Been thanked: 4739 times
• Author
  Posts