sheetcam.com

I have both english and french options in machine type options.

I have bug in few recent patches. When I try to print background became black and I will print black area which I don't want.I'm using 6.1.74 because this version works fine yet.

Jolbas wrote: ↑Wed Dec 16, 2020 10:29 pm I have both english and french options in machine type options.

That can happen if you run SheetCam in English then switch to French or vice-versa. I'll see what I can do about it.

piotr1951 wrote: ↑Thu Dec 17, 2020 6:40 am I have bug in few recent patches. When I try to print background became black and I will print black area which I don't want.I'm using 6.1.74 because this version works fine yet.

Thanks for letting me know. I'll fix it for the next release.

Jolbas wrote: ↑Wed Dec 16, 2020 10:29 pm I have both english and french options in machine type options.

Are you using the Linux version?

Les Newell wrote: ↑Fri Dec 18, 2020 1:51 pm

Jolbas wrote: ↑Wed Dec 16, 2020 10:29 pm I have both english and french options in machine type options.

Are you using the Linux version?

No it's windows version using Wine on Mac. I don't think I ever changed language to french. I did now and then I got double french version.

Hey Les,

Is there any way you can do something about the negative overcut bug sometime soon? It is one of my top 3 pet peeves of bugs. We found it what seems like over a year ago and its an issue for us almost every day.

Don't know if this is a "bugs" item or not but here goes!
Is there a way using looped outside corners with tangent lead-in selected to ignore the loop at the start point? It seems to work with arc lead-in like I think it should but not tangent... or am I missing something?!
Thoughts?
Thanks, Steve

Try it without a overcut, that's probably what's causing that.

That worked! I completly overlooked that one, Thanks.

It would be very nice if the simulation would highlight the current line of code in the code editor - follow the bouncing ball - so that anything odd could be debugged.

The simulator isn't running from your code. It uses an internal data format that looks nothing like g-code.

Machines vary a lot. To reliably simulate the code I would have to have a sort of reverse post processor to read the code back and interpret it. The reverse post would be different for each machine. That's an awful lot of work and a maintenance nightmare.

It would be nice (if possible and practical) if the tabs as displayed on the screen were centered on the toolpath centerline instead of centered on the source vector. It would serve as a visual confirmation that I'm asking for a cut on the correct side of the vector.

This just came to me now, don't know if it's possible or not?

When selecting layers it selects wherever the cursor is touching, would it be possible to have the edit start point mode do the same thing, it would speed things up no end if you didn't have to select the layer to edit them all the time.

SeanP wrote: ↑Wed Jan 13, 2021 2:54 pm When selecting layers it selects wherever the cursor is touching, would it be possible to have the edit start point mode do the same thing, it would speed things up no end if you didn't have to select the layer to edit them all the time.

The problem is that you could have multiple operations on the same layer. Admittedly that probably isn't an issue if you are plasma cutting but it's quite common for milling/routing.