QtPyVCP Widget Rules
- strahlensauger
- Offline
- Elite Member
Less
More
- Posts: 195
- Thank you received: 65
01 May 2020 13:27 #166310
by strahlensauger
Replied by strahlensauger on topic QtPyVCP Widget Rules
Hello Kurt,
I encountered an error in Probe_screen. If I go to tools and enter a new tool and in the comment I use a german
Umlaut key (Ä), I get an error message and I only can restart the whole program. (Not a big deal, if you know,
but maybe the screen could catch "faulty" characters...)
'ascii' codec can't encode character u'\xe4' in position 6: ordinal not in range(128)
Traceback (most recent call last):
File "/home/joe/qtpyvcp/qtpyvcp/widgets/input_widgets/tool_table.py", line 30, in displayText
return "{}{}".format(self._padding, value)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 6: ordinal not in range(128)
Not an issue but maybe a "user bug" , when I started using probe_screen I could jog continously, now I only can jog according to the buttons (max 5mm), which is a bit annoying if you want to go long distances and have jog 20 times.
Maybe you know what happened, or how I can easily come back to continous jogging (I could maybe add a button "continous" like in axis...)?
cheers
Joerg
I encountered an error in Probe_screen. If I go to tools and enter a new tool and in the comment I use a german
Umlaut key (Ä), I get an error message and I only can restart the whole program. (Not a big deal, if you know,
but maybe the screen could catch "faulty" characters...)
'ascii' codec can't encode character u'\xe4' in position 6: ordinal not in range(128)
Traceback (most recent call last):
File "/home/joe/qtpyvcp/qtpyvcp/widgets/input_widgets/tool_table.py", line 30, in displayText
return "{}{}".format(self._padding, value)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 6: ordinal not in range(128)
Not an issue but maybe a "user bug" , when I started using probe_screen I could jog continously, now I only can jog according to the buttons (max 5mm), which is a bit annoying if you want to go long distances and have jog 20 times.
Maybe you know what happened, or how I can easily come back to continous jogging (I could maybe add a button "continous" like in axis...)?
cheers
Joerg
Please Log in or Create an account to join the conversation.
02 May 2020 13:44 #166403
by KCJ
Replied by KCJ on topic QtPyVCP Widget Rules
Thank you for the bug report!
Unicode should be valid in the tooltable remarks section, I will fix this.
Try adding JOG to the beginning of your jog increments in the INI. This should give you a continuous jog option.
The jog increments widget needs to be reworked to make it more flexible..
Cheers,
Kurt
Unicode should be valid in the tooltable remarks section, I will fix this.
Try adding JOG to the beginning of your jog increments in the INI. This should give you a continuous jog option.
The jog increments widget needs to be reworked to make it more flexible..
Cheers,
Kurt
The following user(s) said Thank You: strahlensauger
Please Log in or Create an account to join the conversation.
- strahlensauger
- Offline
- Elite Member
Less
More
- Posts: 195
- Thank you received: 65
02 May 2020 19:58 #166423
by strahlensauger
Replied by strahlensauger on topic QtPyVCP Widget Rules
That was easy - if you know... Now I can jog around again...
If error messages pop up I'll keep you informed.
You still have the YAML file for configuring keys in mind?
Thanks again
If error messages pop up I'll keep you informed.
You still have the YAML file for configuring keys in mind?
Thanks again
Please Log in or Create an account to join the conversation.
Time to create page: 0.795 seconds