NativeCAM is Features renamed

Hi Fern,

I have played a bit more with nativecam and noticed a few issues:
1. I've switched to G95 to use feed per revolution so I've noticed I cannot enter 0.05 for example...when I type the 5, it trims the zeros and remains 5. However I was able to overcome this by typing 0.1 / 2
2. The calculator screen, remains orphaned, you can see in the image below, I have one on each space/desktop..I don't know how to call those boxes in the upper right corner. Those can't be closed..can you at least add a close button to it so that I can close it when its ignoring outside click events.
3. When turning Taper ODL for example, the values for X Begin and X End (when turning a taper with the smaller diameter towards the tailstock) seem to be reversed. I had to enter 14 for X begin and 11 for X end in order to get a taper that grows towards Z- . Are these really reversed or I'm not interpreting them correctly. Alternatively they could be renamed to something more meaningful.

Regarding multi start threading, I've done an attempt, it didn't came out as expected, but I will do some more experiments and then come back with some conclusions.

PS: when using feed per revolution mode (G95 i guess), what does feed override do? Does it changes the feed rate?

vmihalca wrote: ... I cannot enter 0.05 for example...when I type the 5, it trims the zeros and remains 5

Do you mean you entered ',' then '0' then '5' ?

...The calculator screen, remains orphaned, you can see in the image below, I have one on each space/desktop

No images show the calculator dialog

..I don't know how to call those boxes in the upper right corner.

What boxes ?

Those can't be closed..can you at least add a close button to it so that I can close it when its ignoring outside click events.

An orphan window does not respond to any input. However I think it can be killed by the system.

Taper ODL for example, the values for X Begin and X End (when turning a taper with the smaller diameter towards the tailstock) seem to be reversed. I had to enter 14 for X begin and 11 for X end in order to get a taper that grows towards Z- .

Begin X is the position where it starts cutting and End X where it stops. Maybe it should renamed with Large and Small but is it Diameter or Radius ? It think most of the time it would be diameter even if someone it working in radius mode. I will make it diameter

Regarding multi start threading, I've done an attempt, it didn't came out as expected, but I will do some more experiments and then come back with some conclusions.

PS: when using feed per revolution mode (G95 i guess), what does feed override do? Does it changes the feed rate?

For G95
linuxcnc.org/docs/html/gcode/g-code.html#gcode:g93-g94-g95

Regards
Fern

Do you mean you entered ',' then '0' then '5' ?

I have entered 0 then . then 0 then 5

No images show the calculator dialog

You can see one here: photos.app.goo.gl/BDYu1jMey3y6X5Ih2

..I don't know how to call those boxes in the upper right corner.

Those white squares are those orphan windows that I was unable to dismiss them, so I moved linuxcnc to a different space.
Here are some images: photos.app.goo.gl/mfKoNAXk131KEPzc2

An orphan window does not respond to any input. However I think it can be killed by the system.

If I kill the process, will that kill linuxcnc also? If so I will have to re-home on each linuxcnc restart. So basically each window that can't be dismissed would lead to another homing procedure.

Taper ODL for example, the values for X Begin and X End (when turning a taper with the smaller diameter towards the tailstock) seem to be reversed. I had to enter 14 for X begin and 11 for X end in order to get a taper that grows towards Z- .

Begin X is the position where it starts cutting and End X where it stops. Maybe it should renamed with Large and Small but is it Diameter or Radius ? It think most of the time it would be diameter even if someone it working in radius mode. I will make it diameter

What I'm saying is that these are reversed, in order to work as you say I have to reverse the values between these two.
You can see in these images: photos.app.goo.gl/tPb2gAxxZvUcb2j83

Hi Vasi

After trying for more than 1 hour, I could not reproduce any of your issues.
What is your Linux distribution ? What is the language code you are using ?

vmihalca wrote: I have entered 0 then . then 0 then 5

Did it happen only once or on a regular basis and on what Subroutine (Facing, Boring,...) and parameter ?

You can see orphaned dialog here...

Does it also happen with a single desktop space ?

If I kill the process, will that kill linuxcnc also? If so I will have to re-home on each linuxcnc restart. So basically each window that can't be dismissed would lead to another homing procedure.

You would not kill linuxcnc process but the orphan window ... if you can identify it in the list of processes

It could help if you record your screen and create a video of what happened 10 seconds or more before the window became orphan.

I had to find many work around to pygtk issues and I had to drop some interesting ideas because of them. It could take weeks or months before I identify the cause of your issues. Some cases can simply not be debugged.

Regards
Fern

P.S. Enter a 'Init thread depth' large enough to avoid cutting air in the first pass

Hi Fern,

this error can easily be reproduced if you click several times on a value in native cam.

Regards

Niko

Hi Vasi

The new version has a new class for the calculator dialog, units can be changed on the fly and only the subroutine for threading was not actually tested. I hope it solves a lot of problems.

I tested the new input dialog by clicking a value for about 3 minutes, some times as fast as I could and some times about normally as someone would work. It always worked as expected and closed.

There are also many other changes like some dialog that appear to give a cue to new users. When you do not want to see them again, check the box.

Best regards
Fern