- Posts: 7368
- Thank you received: 2181
Error in tool_offsetview.py
- cmorley
- Offline
- Moderator
-
Less
More
2 years 5 months ago #301178
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
Curious - AXIS uses the same code.
Could you add some prints to the code and see if system_memory_bytes get set differently on AXIS vrs QtDragon?
Could you add some prints to the code and see if system_memory_bytes get set differently on AXIS vrs QtDragon?
Please Log in or Create an account to join the conversation.
- MarkoPolo
- Offline
- Elite Member
-
Less
More
- Posts: 319
- Thank you received: 90
2 years 5 months ago #301181
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
ah, ok. You're right, there is no preview in axis either. (first I doubled the value in glcanon.py and then checked in axis)
Please Log in or Create an account to join the conversation.
- MarkoPolo
- Offline
- Elite Member
-
Less
More
- Posts: 319
- Thank you received: 90
2 years 5 months ago #301257
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
Chris. If the 20mb limit should remain, could you add an option to the ini that would disable this limitation?
I don't want to modify glcanon.py after every system update.
Another topic.
I'm looking for a reason why the progress bar doesn't work when loading a gcode file. In qtdragon_hd the progress bar works and the code seems to be the same as in qtdragon.
Could you check it?
(I'm not sure but the "updateProgress" function is not used at all, qtdragon_hd does not have this function)
I don't want to modify glcanon.py after every system update.
Another topic.
I'm looking for a reason why the progress bar doesn't work when loading a gcode file. In qtdragon_hd the progress bar works and the code seems to be the same as in qtdragon.
Could you check it?
(I'm not sure but the "updateProgress" function is not used at all, qtdragon_hd does not have this function)
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
Less
More
- Posts: 7368
- Thank you received: 2181
2 years 5 months ago #301273
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
In case you are interested how this came along:
github.com/LinuxCNC/linuxcnc/pull/2896
In fact I said it should be set-able and then never followed up.
You must load very big files - do you see the bounding box show?
There is a signal missing from gcode_graphics to MainWindow - I'll add it back soon.
github.com/LinuxCNC/linuxcnc/pull/2896
In fact I said it should be set-able and then never followed up.
You must load very big files - do you see the bounding box show?
There is a signal missing from gcode_graphics to MainWindow - I'll add it back soon.
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
Less
More
- Posts: 7368
- Thank you received: 2181
2 years 5 months ago #301321
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
Dragon loading progressbar should be fixed now.
[DISPLAY]
GRAPHICAL_MAX_FILE_SIZE = -1
Should allow maximize usage of the memory for graphical display.
or set it to any integer MB of system memory (default would be 20 MB)
Should work with Qtvcp/GMoccapy/AXIS
Pushed to master
Chris
[DISPLAY]
GRAPHICAL_MAX_FILE_SIZE = -1
Should allow maximize usage of the memory for graphical display.
or set it to any integer MB of system memory (default would be 20 MB)
Should work with Qtvcp/GMoccapy/AXIS
Pushed to master
Chris
The following user(s) said Thank You: tommylight, MarkoPolo
Please Log in or Create an account to join the conversation.
- MarkoPolo
- Offline
- Elite Member
-
Less
More
- Posts: 319
- Thank you received: 90
2 years 5 months ago #301330
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
Great. I tested it and everything works fine. Thanks
One more thing needs to be fixed and qtdragon will be completely usable...
One more thing needs to be fixed and qtdragon will be completely usable...
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.137 seconds