Hi Dean, when you change PixelCNC over to metric it changes how the workspace and grid are scaled in the render. Tool sizes are relative to the project, so if you’re in metric then a 10mm tool diameter will be 1/10th the size of a 100mm project. Feed rates only determine what number is output in the G-code and doesn’t affect anything visually - but in the feeds it will still say ‘IPM’, that will be fixed in the next version that should be out this weekend.
Setting PixelCNC to inches/metric doesn’t take affect until a new project is created via File->New. The only situation with creating a metric project is that you’ll have to re-enter all the parameters from scratch because they’ll still have the stored imperial defaults/previously used values. There are a few values that are stored independently per imperial/metric, such as the project dimensions. Once you set it up with metric feeds and stepsizes and such it will remember those for next time you create an operation.
Converting between metric/imperial could have an automated element to it, but it will only be able to do so much. For instance, the previously used tool dimensions aren’t something that can be mapped one-to-one because a 0.25" tool doesn’t have an exact counterpart in metric (i.e. 6.35mm tool? that would just be called a 1/4" end mill ). Perhaps what I should do is allow intermixing of metric/imperial project dimensions, operation parameters, and tools, instead of requiring that everything be either one or the other. That way you could use an imperial tool in a metric project and vice-versa. I’ll have to mull over that a bit before I decide what to do exactly.
Let me know if you have any further questions/comments/concerns and I’ll do what I can to work things out and get PixelCNC to where you need it to be.