Thank you so much for developing the excellent gSender CNC program! It is my favorite software for running my hand-made PrintNC (with pure GRBL). I am using it on a powerful notebook DELL Precision 7680, if that matters.
In the past, I really enjoyed v.1.4.11. After installing v1.5.2, I see many improvements, but also that
- the continuous jogging is enabled after the “long” press of both the mouse and the corresponding key combinations. This was disabled in v.1.4.11, and i did not know about this feature.
a) It may be useful to explain it in the documentation / release notes.
For the CNC exact movements, I prefer to use the keyboard, since the touchpad or external mouse might accidentally produce a double click, moving CNC twice as far as wanted. Alternatively, one can use the external mouse with the optical switch, which solves the problem). However, after trying v.1.5.2 today, the keyboard click (I assume the touchpad would behave similarly) was recognized as a “long” click about 5 times, thus enabling continuous jogging. Once this led to the broken bit.
Very unfortunately, because of this problem, v1.5.2 is not usable for me.
After reading, I now understand that the long click is not natively recognized by the JavaScript. This might imply that there is no safe, 100% certain way to distinguish it from the single click. The exact movements are necessary in the close proximity of the stock, clamps or model, so such mistakes are dangerous. At least my powerful PrintNC does not forgive any: it just moves regardless of obstacles…
Sorry for my potential ignorance of the subject, I would naively propose several suggestions.
The simplest is to revert to v.14.11 behavior and ignore long clicks (note that because of this problem, for me v.1.5.2 is currently not usable, forcing me to revert anyway). Another possibility is to implement long clicks as a configurable option. Or assign the right mouse button for the continuous jogging , or use the left button but with the key modifier? Alternatively, for advanced users, one may even configure the time delay for the recognition of the long clicks.
- For X,Y-probing, by default after the first touch, if I am not mistaken, the travel for the second cycle has currently the same length, even though after the touch the expected travel (=retract distance, eg. 4 mm) should be much shorter. Can one use for the second travel by default eg. the retract distance + 1 mm? Otherwise, the probing is not possible (=fails) in the proximity of the hard/soft limits. Eg. often I clamp the model close to PrintNC front, which is close to its range end, and probe its X,Y-coordinates. Or, one may want to use the maximal CNC area and also fix the model close to the edge. In this case, one could start the probing sufficiently far from the edge, so that the full first probe travel is inside the allowed range. However, the second one fails, since the start of this travel is closer to the edge and it has the same long length.
Many thanks for reading !
