LinuxCNC Features - a kind of NGCGUI

More
11 years 4 days ago #64372 by FernV
Replied by FernV on topic LinuxCNC Features - a kind of NGCGUI

fixer wrote: ... there is a wrong header value in mz_engrave for PARAM_YOFF. The error only shows up when showing sub groups in master tree.


Line 290 of mz_engrave.ini under '[PARAM_YOFF]' should be 'header = h3' insead of 'h4'

That will correct everything

Fern

Please Log in or Create an account to join the conversation.

More
11 years 3 days ago - 11 years 3 days ago #64426 by FernV
Replied by FernV on topic LinuxCNC Features - a kind of NGCGUI
Hi Mit

There is another correction to do in fv_entry-angle,ngc :

replace line 17 that says
Code:
o<comp00> if [#<opt> EQ 2] (no compensation)

with
Code:
o<comp00> if [[#<opt> EQ 2] OR [#5410 EQ 0]] (no compensation)

line 42 tries to divide by tool radius, it was OK when adding a small number but not multiplying 0 * 0.501

It should also be corrected in fv_entry-arc.ngc (line 21) though there is no such division

Regards
Fern
Last edit: 11 years 3 days ago by FernV.

Please Log in or Create an account to join the conversation.

More
11 years 1 day ago - 10 years 11 months ago #64531 by FernV
Replied by FernV on topic LinuxCNC Features - a kind of NGCGUI
Hi Mit

fixer wrote: -I would replace top features with features history.

Top Features is allready history. It changes with time bringing the most used the leftmost. It can be resetted by deleting catalog/mill/top.lst I think the problem lies in the fact that icons are not clear enough, I mean we do not have enough icons or the wrong one is selected, I admit that I did overlook that. However what is your idea on this ? Do you think of having the last one used placed on far left or ... ?

I am currently finallizing 'polyline' and some parts are very difficult to implement. Hopefully in a couple of weeks it is ready to release. Not sure I will have time to review the way it creates pockets but it is on my todo list

Regards
Fern

EDITED...
Finally, I modified TopFeatures and renamed to History and it will be possible to have 2 blocks of buttons or only one. When you select a number of most popular features, the left block will show them over time since the last time you deleted catalog/mill/top.lst. If none are selected, you will have only buttons sorted with last feature used at the left.

ALL configuration options will be done in the preference dialog (not in feature.py anymore) and the preference file will not be updated with new release, meaning you will not have to do it again.

I also checked if I could debug engrave-feature but I found that TABS and SPACES were both used for indentation. I tried to replace all TABS with 4 spaces but it messes up the indentations and it would not run anymore. I finally downloaded engrave-lines and found it only uses SPACES and I was able to reset the indentation OK. I will be able to debug and hopefully have it ready for next release.

Fern
Last edit: 10 years 11 months ago by FernV.

Please Log in or Create an account to join the conversation.

More
10 years 11 months ago #64771 by fixer
Replied by fixer on topic LinuxCNC Features - a kind of NGCGUI
what do you need to debug on engrave-feature? Have you found any more bugs? sorry for the indetation problem, it doesnt show in my editor.
do you have the latest version? (check a few posts above).

Please Log in or Create an account to join the conversation.

More
10 years 11 months ago #64775 by FernV
Replied by FernV on topic LinuxCNC Features - a kind of NGCGUI
Hi,

fixer wrote: what do you need to debug on engrave-feature?(check a few posts above).


I am going to fix the mirror issue. The indentation problem is caused by your editor that insists to use tabs instead of using a number of spaces. I do not know if in preferences you have this option but gedit has. Python works best with spaces.

Fern

Please Log in or Create an account to join the conversation.

More
10 years 10 months ago #66440 by fixer
Replied by fixer on topic LinuxCNC Features - a kind of NGCGUI
Hi Fernand,
Another idea:
I would like to have "save as default template" called just before app is closed. So the current work gets automatically saved, and reopened on restart. How can I achieve this? Should be simple, calling actionSaveTemplate in exit handler, but I don't know the proper syntax....

Please Log in or Create an account to join the conversation.

Time to create page: 0.477 seconds
Powered by Kunena Forum