Consider using WaitCursor, when busy
Posted: Sat Sep 21, 2019 6:43 pm
When getting used to the software, I remember getting stability issues if I went ahead and started to do other things before the previous action was finished.
So I thought it might be useful to suggest use of the WaitCursor to signal when the system is busy and the user should wait.
Unfortunately, I didn't capture exact situations for you to reproduce.
For example, when a job is running...I presume users shouldn't go to other tabs and start re-configuring things.
Use of the Wait cursor, when the system is busy might improve the UX.
Some good starting points, might be whenever the machine is moving, re-measure, camera functions.
I am not sure if LP knows from TinyG when buffered moves are finished, which could pose a challenge.
Similarly, stopping users from changing Tabs when LP is busy, might be helpful in some situations.
So I thought it might be useful to suggest use of the WaitCursor to signal when the system is busy and the user should wait.
Unfortunately, I didn't capture exact situations for you to reproduce.
For example, when a job is running...I presume users shouldn't go to other tabs and start re-configuring things.
Use of the Wait cursor, when the system is busy might improve the UX.
Some good starting points, might be whenever the machine is moving, re-measure, camera functions.
I am not sure if LP knows from TinyG when buffered moves are finished, which could pose a challenge.
Similarly, stopping users from changing Tabs when LP is busy, might be helpful in some situations.