Jerky Jogging (QTPlasmaC)
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 18562
- Thank you received: 6218
23 Dec 2020 18:55 #193003
by tommylight
Replied by tommylight on topic Jerky Jogging (QTPlasmaC)
Yup, had a run at it also, but to no avail. This is the state of Python on my main PC after a night of trying to get thins going:I have found that different distros may install qt in directories different from what pyqt expects. Sometimes, you need to figure out where python is searching for it's libraries. No doubt a huge PITA but not necessarily qt's fault.
Attachments:
Please Log in or Create an account to join the conversation.
23 Dec 2020 19:44 #193008
by hottabich
Replied by hottabich on topic Jerky Jogging (QTPlasmaC)
Sorry, see your file qtplasmac_handler.py is possible?I added it at line 318. If that's correct, it's not the issue as it didn't change the jog behavior.
Thanks though!
Please Log in or Create an account to join the conversation.
- snowgoer540
-
Topic Author
- Offline
- Moderator
-
Less
More
- Posts: 2362
- Thank you received: 763
23 Dec 2020 21:19 #193027
by snowgoer540
1. It does have the issue with the GUI jog arrows on the MAIN tab.
2. Everything works fine in Axis, and I believe the preview stuff is essentially the same.
You can find it here: github.com/LinuxCNC/linuxcnc/tree/master...cp/screens/qtplasmac
Replied by snowgoer540 on topic Jerky Jogging (QTPlasmaC)
That was my initial thought, because it doesnt do it when you're off the MAIN tab. However, I dont think so... for two simple reasons (albeit maybe bad logic):Does it coincide with graphics display and keyboard jogging?
The graphics display takes a lot of processing power.
1. It does have the issue with the GUI jog arrows on the MAIN tab.
2. Everything works fine in Axis, and I believe the preview stuff is essentially the same.
Sorry, see your file qtplasmac_handler.py is possible?
You can find it here: github.com/LinuxCNC/linuxcnc/tree/master...cp/screens/qtplasmac
Please Log in or Create an account to join the conversation.
- snowgoer540
-
Topic Author
- Offline
- Moderator
-
Less
More
- Posts: 2362
- Thank you received: 763
23 Dec 2020 21:20 #193029
by snowgoer540
Replied by snowgoer540 on topic Jerky Jogging (QTPlasmaC)
I definitely didn't have this problem... i used one of beagle's 19.2 iOS's from probably a year ago. QTVCP just worked.
Yup, had a run at it also, but to no avail. This is the state of Python on my main PC after a night of trying to get thins going:I have found that different distros may install qt in directories different from what pyqt expects. Sometimes, you need to figure out where python is searching for it's libraries. No doubt a huge PITA but not necessarily qt's fault.
Please Log in or Create an account to join the conversation.
23 Dec 2020 21:52 #193032
by hottabich
Replied by hottabich on topic Jerky Jogging (QTPlasmaC)
Try to replace this piece of codeor add the bottom line.
if flag:
if isinstance(receiver2, EDITOR):
# if in manual do our keybindings - otherwise
# send events to gcode widget
if STATUS.is_man_mode() == False:
if is_pressed:
receiver.keyPressEvent(event)
event.accept()
return True
elif is_pressed:
receiver.keyPressEvent(event)
event.accept()
return True
else:
event.accept()
return True
if event.isAutoRepeat():return True
The following user(s) said Thank You: snowgoer540
Please Log in or Create an account to join the conversation.
- snowgoer540
-
Topic Author
- Offline
- Moderator
-
Less
More
- Posts: 2362
- Thank you received: 763
23 Dec 2020 22:46 #193035
by snowgoer540
Replied by snowgoer540 on topic Jerky Jogging (QTPlasmaC)
a little confused about the tabbing.
Is this right:
Is this right:
if flag:
if isinstance(receiver2, EDITOR):
# if in manual do our keybindings - otherwise
# send events to gcode widget
if STATUS.is_man_mode() == False:
if is_pressed:
receiver.keyPressEvent(event)
event.accept()
return True
elif is_pressed:
receiver.keyPressEvent(event)
event.accept()
return True
else:
event.accept()
return True
if event.isAutoRepeat():return True
Please Log in or Create an account to join the conversation.
24 Dec 2020 02:06 #193051
by phillc54
Replied by phillc54 on topic Jerky Jogging (QTPlasmaC)
I had a bit of a look at this today and the qtplasmac code was a bit different to qtdragon. I modified the code so it was similar to qtdragon and it is now also similar to qtaxis.
It seems that the event.isAutoRepeat() is a bit hit and miss in its capturing of repeats. At random times it will pass through a continuous stream of keypresses when a jog key held down.
It seems that the event.isAutoRepeat() is a bit hit and miss in its capturing of repeats. At random times it will pass through a continuous stream of keypresses when a jog key held down.
Please Log in or Create an account to join the conversation.
24 Dec 2020 02:23 #193052
by cmorley
Replied by cmorley on topic Jerky Jogging (QTPlasmaC)
try;
if event.isAutoRepeat():
event.accept()
return True
Please Log in or Create an account to join the conversation.
24 Dec 2020 02:25 #193053
by phillc54
Replied by phillc54 on topic Jerky Jogging (QTPlasmaC)
Still the same.
![:( :(](/media/kunena/emoticons/sad.png)
Please Log in or Create an account to join the conversation.
24 Dec 2020 02:33 #193054
by phillc54
Replied by phillc54 on topic Jerky Jogging (QTPlasmaC)
I played around with the repeat delay and repeat speed in the system keyboard settings and that had no effect.
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.177 seconds