Error in tool_offsetview.py
25 Apr 2024 20:29 #299081
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
I had to copy the files to /usr/share because it was starting with errors in the machine's directory.
In /usr/share it works fine.
A very cool functionality could be with MPG. I currently don't have physical MPG.
I wanted to run the virtual MPG sim_panel but it doesn't want to work, so I haven't tested how it works yet.
When it comes to buttons, the old style is probably best. There could be a delay in displaying the menu, although it can be irritating when pressed frequently (although these functions are not used very often).
The button on the Z axis on the touch panel may be inconvenient.
It's nice that the menu is bigger (maybe even a little too big, but these are only preliminary solutions)
Overall, it's a nice idea, I think it's worth working on.
In /usr/share it works fine.
A very cool functionality could be with MPG. I currently don't have physical MPG.
I wanted to run the virtual MPG sim_panel but it doesn't want to work, so I haven't tested how it works yet.
When it comes to buttons, the old style is probably best. There could be a delay in displaying the menu, although it can be irritating when pressed frequently (although these functions are not used very often).
The button on the Z axis on the touch panel may be inconvenient.
It's nice that the menu is bigger (maybe even a little too big, but these are only preliminary solutions)
Overall, it's a nice idea, I think it's worth working on.
Please Log in or Create an account to join the conversation.
- snowgoer540
- Offline
- Moderator
Less
More
- Posts: 2388
- Thank you received: 779
25 Apr 2024 21:10 #299083
by snowgoer540
Replied by snowgoer540 on topic Error in tool_offsetview.py
Apologize for potentially derailing any discussion...
I was wondering what the use case for the max velocity slider is. I know of another GUI that uses it in place of a rapid slider (which is really unintuitive as they are definitely not the same thing), but I was just curious to hear what the use case is when also given a rapid and feed slider.
I was wondering what the use case for the max velocity slider is. I know of another GUI that uses it in place of a rapid slider (which is really unintuitive as they are definitely not the same thing), but I was just curious to hear what the use case is when also given a rapid and feed slider.
Please Log in or Create an account to join the conversation.
25 Apr 2024 21:21 #299085
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
What didn't work with sim_panel?
I used thwsw command after qtdragon started in another terminal:
qtvcp sim_panel &
halcmd net MPG qtdragon.mpg-in sim_panel.MPG-s
I used thwsw command after qtdragon started in another terminal:
qtvcp sim_panel &
halcmd net MPG qtdragon.mpg-in sim_panel.MPG-s
Please Log in or Create an account to join the conversation.
25 Apr 2024 21:46 #299086
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
ok, I missed this "halcmd net MPG qtdragon.mpg-in sim_panel.MPG-s"
Please Log in or Create an account to join the conversation.
27 Apr 2024 17:04 #299197
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
I like the "max velocity slider" slider, but it should immediately limit all speeds, including manual movements, but it does not limit manual movements.
I added 4 lines to the handler file, as in the screenshot. Only the first slider setting "MAX_VELOCITY_OVERRIDE" works, I don't know why the other slider settings don't work.
ps. I'm working on a more extensible qtdragon. I will upload the file soon.
It will be possible to stretch it to 4K (3840x3840), it doesn't look very nice at such a high resolution, but it is possible.
I added 4 lines to the handler file, as in the screenshot. Only the first slider setting "MAX_VELOCITY_OVERRIDE" works, I don't know why the other slider settings don't work.
ps. I'm working on a more extensible qtdragon. I will upload the file soon.
It will be possible to stretch it to 4K (3840x3840), it doesn't look very nice at such a high resolution, but it is possible.
Please Log in or Create an account to join the conversation.
28 Apr 2024 14:49 #299257
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
Try adding this function:
def before_loop__(self):
# set defaults lower then max if wanted
DEFAULT_RAPID_OVERRIDE = float(INFO.get_error_safe_setting("DISPLAY", "DEFAULT_RAPID_OVERRIDE", .5)) * 100
ACTION.SET_RAPID_RATE(DEFAULT_RAPID_OVERRIDE)
DEFAULT_VELOCITY_OVERRIDE = float(INFO.get_error_safe_setting("DISPLAY", "DEFAULT_MAX_VELOCITY", 1800))
ACTION.SET_MAX_VELOCITY_RATE(DEFAULT_VELOCITY_OVERRIDE)
The following user(s) said Thank You: MarkoPolo
Please Log in or Create an account to join the conversation.
28 Apr 2024 18:50 #299269
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
Thanks, it works fine this way.
I only changed the settings for "max_velocity_override" so that it took the max speed from the "MAX_LINEAR_VELOCITY" value
FACTOR_VELOCITY_OVERRIDE = float(INFO.get_error_safe_setting("DISPLAY", "DEFAULT_VELOCITY_OVERRIDE"))
DEFAULT_VELOCITY_OVERRIDE = float(INFO.get_error_safe_setting("DISPLAY", "MAX_LINEAR_VELOCITY", )) * FACTOR_VELOCITY_OVERRIDE * 60
ACTION.SET_MAX_VELOCITY_RATE(DEFAULT_VELOCITY_OVERRIDE)
Try qtdragon with the ability to stretch to 3840x3840
I only changed the settings for "max_velocity_override" so that it took the max speed from the "MAX_LINEAR_VELOCITY" value
FACTOR_VELOCITY_OVERRIDE = float(INFO.get_error_safe_setting("DISPLAY", "DEFAULT_VELOCITY_OVERRIDE"))
DEFAULT_VELOCITY_OVERRIDE = float(INFO.get_error_safe_setting("DISPLAY", "MAX_LINEAR_VELOCITY", )) * FACTOR_VELOCITY_OVERRIDE * 60
ACTION.SET_MAX_VELOCITY_RATE(DEFAULT_VELOCITY_OVERRIDE)
Try qtdragon with the ability to stretch to 3840x3840
Please Log in or Create an account to join the conversation.
28 Apr 2024 22:09 #299275
by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
It's v e r y stretchy! I see what you mean about the look of the controls for instance when stretched.
try my rough changes to your changes
try my rough changes to your changes
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
28 Apr 2024 22:49 - 28 Apr 2024 22:51 #299280
by MarkoPolo
Replied by MarkoPolo on topic Error in tool_offsetview.py
It's hard to find a perfect solution, these empty spaces aren't the best either. I only have a 2560 screen, if anyone has a 4K screen, please try it, I'd love to see such a screenshot. In fact, I don't think anyone uses 4K screens for the machine. I don't see any side effects, so such a high resolution is not a problem.
Last edit: 28 Apr 2024 22:51 by MarkoPolo.
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19188
- Thank you received: 6433
28 Apr 2024 23:28 #299281
by tommylight
Replied by tommylight on topic Error in tool_offsetview.py
I have a 4K that does not get much use since i got a 34" ultrawide, so i might make some time to test it, so what would that entail?
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.121 seconds