issue call instruction of an indicator with DRAWTEXT

• 08/26/2017 at 12:01 AM #44656
  mmichael

  Hello,

  I am developping a screener based on a custom indicator. this is used by the call instruction from the screener.

  The screener does not return any result, so I I investigated and it seems to be due to the use of drawtext() in the indicator.

  When I remove the drawtext in my indicator, the screener works.

  Is this a known bug? is there a workaround?

  Many thanks in advance for your help

  

  mmichael

  Participant

  Topics: 4

  Replies: 36

  Been thanked: 4 times
  08/26/2017 at 12:13 AM #44657
  mmichael

  Code of the indicator: “myindic”

  myindic

  if close >= average[50](close) then trendstate = 1 //DRAWTEXT("•",barindex,0,monospaced,standard,11) coloured(40,200,0,190) else trendstate = -1 endif RETURN trendState coloured(255,160,40,0) style(Point,1) as "trend"

  1 2 3 4 5 6 7 8

  if close >= average[50](close) then trendstate = 1 //DRAWTEXT("•",barindex,0,monospaced,standard,11) coloured(40,200,0,190) else trendstate = -1 endif   RETURN trendState coloured(255,160,40,0) style(Point,1) as "trend"

  Code of the screener that calls the indicator:

  myscreener

  TIMEFRAME(4 hours) trendValue = CALL "myindic" screener (trendValue as "trend")

  1 2 3

  TIMEFRAME(4 hours) trendValue = CALL "myindic" screener (trendValue as "trend")

  if we decomment the line drawtext in the indicator, the screener stops working

  

  mmichael

  Participant

  Topics: 4

  Replies: 36

  Been thanked: 4 times
  08/26/2017 at 2:57 PM #44669
  AVT

  I assume that all those DRAWxxx commands are proBuilder only commands, something like “bring that value somehow into my window”.

  Flatly spoken I think of 2 different kind of caches, one keeping the calculated value (which in a “normal” RETURN indi as “myindi” command is used by the return funcion directly) and one for the drawings (which is additionally used by DRAWxxx to insert the calculated value into the x/y axis values). And as a DRAWxxx indicator ends with a simple RETURN, the value (which a “normal” indicator would use now) is empty and cannot be accessed any longer (cause it was inserted into the drawing cache and is then gone).

  Your way of changing the last line of the indicator seems the only workaround for me. Just my 2c.

  1 user thanked author for this post.

  mmichael

  

  AVT

  Participant

  Topics: 17

  Replies: 186

  Been thanked: 58 times
  08/27/2017 at 1:27 AM #44683
  mmichael

  thx AVT for your answer.

  if I understand well, the presence of DRAWxxx functions in an indicator make it impossible to call it from a screener.

  This is a weird bug / regression.

  

  mmichael

  Participant

  Topics: 4

  Replies: 36

  Been thanked: 4 times
  08/27/2017 at 1:32 PM #44710
  Nicolas

  Very interesting, never seen this problem myself… and I can replicate it, thanks for let us know. While I’m still away from my office, could you please send a bug report to prorealtime to let them know about this problem please (CTRL+M)? I will track this one once I come back for good. You can add the link to this topic, I think it is sufficient to explain the bug.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4774 times
  08/29/2017 at 11:27 AM #44824
  Nicolas

  I got news about this problem. The “coloured” instruction creates a problem that does not return the right value when the indicator is CALL(ED). A quick fix would be to delete the COLOURED of your DRAWTEXT line. This issue should be fixed quickly by PRT dev team. Thanks for reported it 🙂

  2 users thanked author for this post.

  mmichael, AVT

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4774 times
  08/31/2017 at 4:13 AM #44972
  mmichael

  thank you Nicolas for the workaround.

  I am not sure to understand. What is the result of the indicator call?

  • is it the value of the RETURN statement?
  • or is it the drawtext (this would be strange…)

  In my case the drawtext –> DRAWTEXT(“•”,barindex,0,monospaced,standard,11) –> this would give 0 I guess

  the RETURN statement gives 1 or 0. It makes more sence that the call takes these values and not what is in the drawtext.

  

  mmichael

  Participant

  Topics: 4

  Replies: 36

  Been thanked: 4 times
  08/31/2017 at 2:09 PM #45042
  Nicolas

  Returned values are only ones in RETURN instruction line of your code.

  1 user thanked author for this post.

  mmichael

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4774 times
  09/12/2017 at 3:59 AM #45981
  mmichael

  Hello Nicolas, any new for this wheather if it is fixed or not?

  Again, I am sorry but it is an ugly bug!

  

  mmichael

  Participant

  Topics: 4

  Replies: 36

  Been thanked: 4 times
  09/18/2017 at 7:46 AM #46444
  Nicolas

  All bugs are ugly IMO 🙂 I don’t know if it has already been fixed (did you try recently?) but I know for sure it will be very soon.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4774 times
• Author
  Posts