Qtlathe
23 Jul 2020 07:23 #175472
by cmorley
a circle with a line though it usually means no or negative - I would remove the line - green circle is good.
I'm not sure I understand:
Q-orientation tool cannot the number, it can beat R, L, N.
orientation is a number:
linuxcnc.org/docs/2.8/html/lathe/lathe-u...e_tool_orientation_a
I'm not sure I understand:
Q-orientation tool cannot the number, it can beat R, L, N.
orientation is a number:
linuxcnc.org/docs/2.8/html/lathe/lathe-u...e_tool_orientation_a
Please Log in or Create an account to join the conversation.
09 Aug 2020 20:11 #177775
by cmorley
I pushed some work based on yours...
I did change the html setup widget to autoload setup pages if they are present and to mention if they are not.
Loading files in filemanager can only be done with the load button - works better with touch screens.
Didn't get a change to add camview but is it sed much with lathes?
Chris
I did change the html setup widget to autoload setup pages if they are present and to mention if they are not.
Loading files in filemanager can only be done with the load button - works better with touch screens.
Didn't get a change to add camview but is it sed much with lathes?
Chris
Please Log in or Create an account to join the conversation.
10 Aug 2020 07:22 #177800
by cmorley
I missed the edit mode
I was thinking it would be nice to for the user to make a setup page if there was not one included.
I experimented with an editable HTML page - it seemed to have promise.
It would be nice if it could scan the gcode and collect the tool numbers then pre fill data from the tooltable into the setup page.
Then a section for notes.
But I haven't written HTML code much so will need to learn a bit.
Chris
I was thinking it would be nice to for the user to make a setup page if there was not one included.
I experimented with an editable HTML page - it seemed to have promise.
It would be nice if it could scan the gcode and collect the tool numbers then pre fill data from the tooltable into the setup page.
Then a section for notes.
But I haven't written HTML code much so will need to learn a bit.
Chris
Please Log in or Create an account to join the conversation.
14 Aug 2020 16:34 #178197
by cmorley
There is a man button on the latest version.
It's not that I don't like your version.
It's a bit of a pain to convert it each time to be in the installed location.
Mostly the image files need to be fixed.
It's usually easier to add your changes to the existing screen.
There are a few choices you make that I wouldn't be nothing I feel strongly about.
Your screen gets better and better - Don't stop!
Chris
It's not that I don't like your version.
It's a bit of a pain to convert it each time to be in the installed location.
Mostly the image files need to be fixed.
It's usually easier to add your changes to the existing screen.
There are a few choices you make that I wouldn't be nothing I feel strongly about.
Your screen gets better and better - Don't stop!
Chris
The following user(s) said Thank You: hottabich
Please Log in or Create an account to join the conversation.
15 Aug 2020 14:33 - 15 Aug 2020 14:59 #178284
by hottabich
In home/dev(name)/linuxcnc/configs unarhive G71 and sim.qtvcp..... . Start G71 open file dxf of G71/ngc export
ngc run - see error. To see the patron you need AXIS blank rename qtlathe blank. On my computer there is no open GL that's why I can't see it works or not. I don’t know how to arrange it with a widget as in the video.
ngc run - see error. To see the patron you need AXIS blank rename qtlathe blank. On my computer there is no open GL that's why I can't see it works or not. I don’t know how to arrange it with a widget as in the video.
Last edit: 15 Aug 2020 14:59 by hottabich.
Please Log in or Create an account to join the conversation.
16 Aug 2020 04:38 #178350
by cmorley
I am concerned about the G71 etc routines - are they open sourced?
I don't want to pull in copyrighted code.
I have pushed work on lathe macros that should fix them for imperial/metric entry.
And they now use the calculator widget.
they need to be tested of course - for instance chamfer seemed weird in simulation.
i have not dived into the graphics openGL code yet.
I adjusted how the graphics button works - it was annoying me when doing the macro work testing.
I pushed the work but only into 2.8 - there are merge conflicts i can't figure out to get it to master.
Chris
I don't want to pull in copyrighted code.
I have pushed work on lathe macros that should fix them for imperial/metric entry.
And they now use the calculator widget.
they need to be tested of course - for instance chamfer seemed weird in simulation.
i have not dived into the graphics openGL code yet.
I adjusted how the graphics button works - it was annoying me when doing the macro work testing.
I pushed the work but only into 2.8 - there are merge conflicts i can't figure out to get it to master.
Chris
The following user(s) said Thank You: hottabich
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.087 seconds