Annoying persistent erroneous message boxes.
-
@deckingman
I have my timeout at 3 seconds.
If I run this macrowhile iterations < 10 echo "Loop count:",iterations G4 S3I get this in DWC
Not the "ghost" readings showing up again which I presume are due timeout vs queue time
If I reduce the G4 time to 2 seconds I get this.
The echos appear every two seconds as expected, but note the reverse countdown effect at the end.
If I go to 3.2 seconds per loop allowing the timeout to expire
-
@OwenD Thanks. Not sure I fully understand. Are you saying that if the G4 in the "while loop" is greater than the DWC time out delay then all is well, but if the G4 time is the same or shorter than the DWC timeout setting, then strange things happen?
-
@deckingman said in Annoying persistent erroneous message boxes.:
@OwenD Thanks. Not sure I fully understand. Are you saying that if the G4 in the "while loop" is greater than the DWC time out delay then all is well, but if the G4 time is the same or shorter than the DWC timeout setting, then strange things happen?
Pretty much
-
@OwenD My print finished and I changed the time out delay in DWC to be 3 secs (2 secs less that the G4 wait in the while loop) and that seems to have cured the annoying persistent messages. So this is a work around but maybe it might bear some further investigation by @chrishamm or whoever?
-
@deckingman said in Annoying persistent erroneous message boxes.:
@OwenD My print finished and I changed the time out delay in DWC to be 3 secs (2 secs less that the G4 wait in the while loop) and that seems to have cured the annoying persistent messages. So this is a work around but maybe it might bear some further investigation by @chrishamm or whoever?
Yes I agree.
If you look in the console everything is in order.
It's only the "pop up" that gets confusing as the queue appears "out of order" at times.
I'd be happy if the pop up just shows the most recent message received (and omitted any more received before it timed out) but others may disagree. -
@OwenD The other thing I find strange is that when I get the persistent pop up, the actual numbers being shown don't reflect what is purported to be the thing that is being echoed. In the case that I illustrated, the pop up is showing an ever decreasing bed temperature, yet the main DWC page shows the bed temperature as being rock solid. I can't think of anything that starts at current bed temperature and decays over time while the bed temperature itself remains constant, so what the hell are the numbers being shown in the pop up?
-
@deckingman said in Annoying persistent erroneous message boxes.:
so what the hell are the numbers being shown in the pop up?
Hard to be 100% sure but I suspect you may be seeing "old" pop up boxes showing the old values... Because of the way the various boxes timeout, you see the boxes in reverse order of them being created... I think one of @OwenD examples showed this. I agree it is very confusing and as mentioned above, just having the most recent message might be better.
@deckingman said in Annoying persistent erroneous message boxes.:
so what the hell are the numbers being shown in the pop up?
-
@gloomyandy That sounds like a feasible explanation - at least, I can't think of a better one.
-
@deckingman I still have plans to change the notification system but no ETA at this point. If you're worried about notifications stacking up, consier using persistent display messages (M117) instead - that should be overwritten whenever the message changes.
-
@chrishamm Thanks. I'll stick with the shortened DWC timeout work around because I have a lot of macros which use multiple instances of "echo" so it would be a bit of a pain to change them all.
Another piece of info which may or may not be relevant is that the pop up echo message box sometimes shows two instances of the echo command. You can see that in my first post where the Bed temp is shown as both 46.13 and 46.58. As the bed temperature was rising, the upper value in bold is actually a previous measurement.
-
@deckingman That overlapping text content may be expected in standalone mode, because RRF concatenates messages that are not fetched frequently enough. You may get around that by increasing the poll interval in the DWC settings.
