Macros, errors messages, and touchscreens
-
This isn't really a bug but an annoyance that has now hit me a few times.
I have error messages not timing out, so I can leave, do stuff, then come back and see what happened. What this means is that I have to manually remove error messages and when I do that by clicking the close X button on my touchscreen I miss the X sometimes and instead it runs whatever random macro is underneath my finger because the macros display in the same screen area as the error messages.
Is there any way something there could be changed? Running a random macro when I want to close an error message isn't great.
Thanks. Mark
-
That's a good point. Thanks. I'll bring it to @chrishamm attention.
-
@Phaedrux are you sure he doesn't mean when using a paneldue?
-
@jay_s_uk said in Macros, errors messages, and touchscreens:
@Phaedrux are you sure he doesn't mean when using a paneldue?
I dunno.. he posted it in the DWC forum, but I guess it could apply for either.
-
@Phaedrux missed the category!
-
Sorry, yes, I definitely meant DWC.
-
While I get the issue you're highlighting, solving the source of the errors might be a good approach as well.
Maybe DWC should disable the jog controls when VIN is not in range or axes are not homed?
And making the whole error message clickable to dismiss might make sense on touch devices, should help with aiming.
-
@bearer I just used these voltage errors as examples in the picture because they were easy to cause (my 24V supply is turned off).
My experience is that usually the errors are caused by my tweaking stuff manually before starting a print - so I'll do a G30 before homing XY is the most common error. Or I'll run a macro that needs stuff homed before I remember to home. Or... you get the idea.
-Mark
"Making the whole error message clickable" would be an ok solution
-
You could put some conditional g-code in your macros or even G28 in your config.g while waitng for the UI to be improved.
-
@bearer I've had some issues getting conditionals to work correctly in the macros in current RRF so I've avoided them but that's a good idea.
