[SOLVED] Infistar - Notifiy text doesn't go away

[Rob 5]

Hello,

I've set up some single display connection notifys with Infistar 56 that worked well.
Only some lines aka
{-1, -1, 10, 0.6, 0, 0, "#FF0000", "Text"},
last line without comma. Double checked. It works well in 56.

However, I've now updated to 60 and now 61 but the last notify message stay on the screen forever.
I've noticed, the display code has changed from 56 to 60. Can it be that the end condition is not working well, yet?
Any ideas?

BR
Rob

[infiSTAR 1112]

Hey

what display code has changed?

You say the last message stays forever no matter what you set it to?

[hogansheroes 200]

I've set up some single display connection notifys with Infistar 56 that worked well.
Only some lines aka
{-1, -1, 10, 0.6, 0, 0, "#FF0000", "Text"},

as his message states here he has a coma , at the end of the only 1 message he needs to remove it like this 

{-1, -1, 10, 0.6, 0, 0, "#FF0000", "Text"}

v61 does work with messages as i use with mine perfect

 

 

 

Edited September 26, 2016 by hogansheroes

[kuplion 1195]

11 hours ago, infiSTAR said:

Hey

what display code has changed?

You say the last message stays forever no matter what you set it to?

I've had this happen to me too, since updating to v61. The last InfiSTAR toast stays on the screen until another one is displayed and then that one stays on the screen instead.

I didn't notice it with v59 (and was barely online with v60 installed so didn't get a chance to see it).

[Rob 5]

OK, my setup, that was working well in v56 is:

ENABLE_NOTIFICATION_MESSAGES = true;
NOTIFY_MSG_ARRAY[] =
{
    {-1, -1, 10, 0.6, 0, 0, "#1900FF", "Text1"},
    {-1, -1, 10, 0.6, 0, 0, "#FF0000", "Text2"},
    {-1, -1, 10, 0.6, 0, 0, "#FF0000", "Text3"},
    {-1, -1, 10, 0.6, 0, 0, "#FF0000", "Text4"},
    {-1, -1, 10, 0.6, 0, 0, "#1900FF", "Text5"}
};

Since updating to 60/61, Text5 doesn't go away. Same problem kuplion seem to have.

The code behind "if(_ENABLE_NOTIFICATION_MESSAGES)then.." has changed from 56 to 60 according a simple diff, so I assume, here could be a problem and/or the last message get not cleared properly.

BR
Rob

Edited September 26, 2016 by Rob

[GolovaRaoul 51]

Can confirm, same issue

[infiSTAR 1112]

done my changes that will fix it in the next update which will probably be tomorrow

[hogansheroes 200]

im thinking why its staying on maybe because you are running a time that shows once only  not a time that runs diffrent times as well

[infiSTAR 1112]

also has a nice fade in/fade out now since somebody else asked for that