- Posts: 319
- Thank you received: 0
Error in tool_offsetview.py
1 year 10 months ago #316131
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
The script calculates fairly correctly if g54 z0 is set to the A-axis rotation axis, and Y0 is above the A-axis center.
This is just a rough idea, to calculate the speed at the tool tip completely correctly, a few corrections would have to be made.
The script does not have a loop, so I run it like this: "watch -n0.2 ./new_vel.py"
This is just a rough idea, to calculate the speed at the tool tip completely correctly, a few corrections would have to be made.
The script does not have a loop, so I run it like this: "watch -n0.2 ./new_vel.py"
Please Log in to join the conversation.
1 year 5 months ago #328476
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
Hi Cmorley
I like the MacroTab Widget, you can easily make your own simple macros, but I think it needs some fixes.
I can save the current parameters to a file, but there is a problem with restoring the settings from the file.
The "set_style" function also does not work. I tried to fix it, but so far without success.
Could you look at this problem?
I like the MacroTab Widget, you can easily make your own simple macros, but I think it needs some fixes.
I can save the current parameters to a file, but there is a problem with restoring the settings from the file.
The "set_style" function also does not work. I tried to fix it, but so far without success.
Could you look at this problem?
Please Log in to join the conversation.
1 year 5 months ago #328509
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
You bet. I will look at it as soon as I can.
Please Log in to join the conversation.
1 year 5 months ago #328561
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
Can you give more detail of the load problem?
I'm guessing you want it to autoload at startup?
set_style is old code from a slightly different version.
IIRC if you use it then you can't override the style with the style editor.
Here are some of the things you can change from the style sheet editor:
I think it needs a way to change styles per macro as it's hard to get sizes to work with different macros.
If there is interest I can develop it more.
I'm guessing you want it to autoload at startup?
set_style is old code from a slightly different version.
IIRC if you use it then you can't override the style with the style editor.
Here are some of the things you can change from the style sheet editor:
Code:
MacroTab CustomButton{
width: 20px;
height: 40px;
}
MacroTab QPushButton {
width: 80px;
height: 40px;
}
MacroTab QLabel {
font: 24pt "Lato Heavy";
}
TouchSpinBox LineEdit {
font: 12pt "Lato Heavy";
}
TouchSpinBox QPushButton {
width: 60px;
height: 100px;
}
I think it needs a way to change styles per macro as it's hard to get sizes to work with different macros.
If there is interest I can develop it more.
Please Log in to join the conversation.
1 year 5 months ago #328564
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
I did push some work to fix an error I found.
Please Log in to join the conversation.
1 year 5 months ago #328586
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
It's almost good.
Setting the style in the qtdragon file is quite sufficient.
Restoring settings from the file works well, but only if they are integers.
If it's a floating-point number, then an error appears as in the screenshot.
Another problem (request, proposal) is the "RadioButton" element. It works like a switch and in some macros this is the desired behavior, but in others it is not.
If I want more items to check a logical condition, then there is a problem. That's why a new "CheckBox" element would be useful.
Setting the style in the qtdragon file is quite sufficient.
Restoring settings from the file works well, but only if they are integers.
If it's a floating-point number, then an error appears as in the screenshot.
Another problem (request, proposal) is the "RadioButton" element. It works like a switch and in some macros this is the desired behavior, but in others it is not.
If I want more items to check a logical condition, then there is a problem. That's why a new "CheckBox" element would be useful.
Please Log in to join the conversation.
1 year 5 months ago #328593
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
Ok fixed floating point problem.
added new default commands:
for a radio button (with exclusive behavior)
radiotrue
radiofalse
for a checkbox (independent):
checktrue
checkfalse
true and false now will show a checkable pushbutton
Chris
added new default commands:
for a radio button (with exclusive behavior)
radiotrue
radiofalse
for a checkbox (independent):
checktrue
checkfalse
true and false now will show a checkable pushbutton
Chris
Please Log in to join the conversation.
1 year 5 months ago #328604
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
Great.
Everything works fine, that's what I wanted. Thanks a lot.
It would be good to update the documentation, because old ngc files with "MACRODEFAULTS=true,false" settings will stop working for some users after updating "MacroTab".
Marek
Everything works fine, that's what I wanted. Thanks a lot.
It would be good to update the documentation, because old ngc files with "MACRODEFAULTS=true,false" settings will stop working for some users after updating "MacroTab".
Marek
Please Log in to join the conversation.
1 year 5 months ago #328611
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
I did update the docs but..
Maybe I should set true/false to be radio buttons too and add buttontrue/false.
Maybe I should set true/false to be radio buttons too and add buttontrue/false.
Please Log in to join the conversation.
1 year 5 months ago #328614
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
Maybe leave it as it is now, but add so that radioButton also works with true/false string for backward compatibility ?
Please Log in to join the conversation.
Time to create page: 0.213 seconds
