And still going strong, Version 0.9.5 is there, as usual also including sources !
I posted this new version at the bottom of this post: GRBL v1.1 Machine Control and GCODE sender Plugin
Fixes this time:
- Re-did the sources to remove "using static". Pre 2015 Visual Studio's compilers do not understand that...
- Animation is again smoother than before. It proved that the Windows timer is not always
ticking at the same rate ( +15, - 0 ms
) so compensation is built in for that
- When the tool does not move, refreshrate is 10 times slower than while moving. Saves precious CPU cycles
- When switching away from the 'Machine' tab, the tool tracking is hidden ( so one can work on the drawing )
- Since I started testing and using plain, elsewhere generated GCODE files ( Eagle in this case )
I saw that these imports do not contain any elements, only toolpaths. The plugin however is
tracing them perfectly, there is no problem. And I can use them. However CamBam also does
not fill it's 'Outfile'. GRBLMachine is adapted to now see also the GCODE file that was imported.
Maybe some might consider it as 'CamBam-mis-use' but it's very handy for me. Working in this
mode CamBam is for me THE GCODE Sender DeLuxe
- As while tracking the machine, it is very nice to see the drawing in 3D, now when pressing
the 'Play' button, the View is set to 3D and 'Zoomed to Fit'
- But... 'Zoom To Fit' does not take toolpaths into account... So, I wrote an extension
called 'GetScreenExtentsEx', which in addition to the standard call also measures toolpaths
when present. 'ZoomToFitEx' is the logical consequence... this has also been written
- Some namespaces have been renamed, so that they may also be used by other pluginners
I hope your problem is solved by the changes in this release.
Grtzz and please keep me informed about what you think of GRBLMachine,