The point is mostly that we have a brand new shiny version of Cura that does things differently. We see the issue with wanting to modify / make plugins for Cura, so we redid pretty much everything and made sure that this would be possible.
So with the old Cura you could pretty much change only the g-code, with the new one you can change a lot more (view modes, tools, input / output devices, etc)
Recommended Posts
eldrick 65
You are asking the wrong guy. Try asking the Cura developers. I'd love to know the answer too.
Link to post
Share on other sites
nallath 1,124
You would have to ask @Daid
Link to post
Share on other sites
Cyberchipz 3
If they're looking to see if there's interest, then I'm replying because I would like to have a list of these tokens also. As a programmer, knowing tokens is a must, and how they operate is a requirement. Internally, from existing code we can see this is valuable information. As a developer it's priceless. I would like to have a list of tokens also. So far, people keep telling me there are other slicer printers to use; but, I'm stubbornly continuing to use Cura because I produce nice prints with simple tweaking of parameters. I've only been printing a week, and already my starting and ending gcode is growing for more control and better results with verious profiles for various behaviors. The longer I do this, the less the likelihood I'll migrate. I see they're quick to add changes, so far, to keep customers satisfied; I hope this will be one of them.
So, I would love to see a set of tokens or internal fixed variables that I could use in developing GCODE in Cura!
Link to post
Share on other sites