- Posts: 6803
- Thank you received: 0
Learning to work with new QTVCP screens and handler
5 years 10 months ago #191908
by cmorley
Replied by cmorley on topic Learning to work with new QTVCP screens and handler
The problem with MDI_CALL_WAIT is it blocks the ui while it waits - so keep it short as practical
Please Log in to join the conversation.
5 years 10 months ago #191924
by Pro_El
Replied by Pro_El on topic Learning to work with new QTVCP screens and handler
I find something i think is a problem with QTDragon build in Linuxcnc 2.9 with buster.
I run MDI Program and just i select with mouse from older commands in MDI and place cursor in MDI box it stops the MDI Execution. In Axis window it didn't stop and even if i execute second program in AXIS it finished first command and then go on with second command. I do not now if this is expected operation or not.
Thank you
I run MDI Program and just i select with mouse from older commands in MDI and place cursor in MDI box it stops the MDI Execution. In Axis window it didn't stop and even if i execute second program in AXIS it finished first command and then go on with second command. I do not now if this is expected operation or not.
Thank you
Please Log in to join the conversation.
5 years 10 months ago #191928
by cmorley
Replied by cmorley on topic Learning to work with new QTVCP screens and handler
What version of linuxcnc are you using?
Was the AXIS version that same?
I see in master 'stacking' MDI commands stops the previous ones.
It didn't do this in linuxcnc 2.7 and I haven't tested 2.8 yet.
Stopping an MDI command by cursoring into MDI line is probably a qtvcp bug - I'll look into it.
Was the AXIS version that same?
I see in master 'stacking' MDI commands stops the previous ones.
It didn't do this in linuxcnc 2.7 and I haven't tested 2.8 yet.
Stopping an MDI command by cursoring into MDI line is probably a qtvcp bug - I'll look into it.
Please Log in to join the conversation.
5 years 10 months ago #191929
by cmorley
Replied by cmorley on topic Learning to work with new QTVCP screens and handler
Sorry i see you said you are using 2.9.
I'm investigating - i have found a bug in 2.8 that causes stacked MDi commands to not work properly. it could be the total problem after all.
I'm investigating - i have found a bug in 2.8 that causes stacked MDi commands to not work properly. it could be the total problem after all.
Please Log in to join the conversation.
5 years 10 months ago #191938
by cmorley
Replied by cmorley on topic Learning to work with new QTVCP screens and handler
ok i think i got it fixed in 2.8 and master.
next time you update, let me know if it's fixed.
Chris
next time you update, let me know if it's fixed.
Chris
Please Log in to join the conversation.
5 years 10 months ago #192030
by hottabich
Please make these changes, they work, you suggested them to me. Thank you.
Replied by hottabich on topic Learning to work with new QTVCP screens and handler
Code:
try in handlerfile
if flag:
if isinstance(receiver2, GCODE):
# if in manual or in readonly mode do our keybindings - otherwise
# send events to gcode widget
if STATUS.is_man_mode() == False or not receiver2.editor.isReadOnly():
if is_pressed:
receiver.keyPressEvent(event)
Please Log in to join the conversation.
5 years 10 months ago #192099
by cmorley
pushed to 2.8
Replied by cmorley on topic Learning to work with new QTVCP screens and handler
hottabich wrote:
Please make these changes, they work, you suggested them to me. Thank you.Code:try in handlerfile if flag: if isinstance(receiver2, GCODE): # if in manual or in readonly mode do our keybindings - otherwise # send events to gcode widget if STATUS.is_man_mode() == False or not receiver2.editor.isReadOnly(): if is_pressed: receiver.keyPressEvent(event)
pushed to 2.8
Please Log in to join the conversation.
5 years 10 months ago #192282
by Pro_El
Replied by Pro_El on topic Learning to work with new QTVCP screens and handler
Sorry for late respond. Iv been able now to test your push in LCNC 2.9 with buster.
Now MDI is working like it should it finished the first command and even during execution of first command i enter second one the mdi finishes first and start second command. I think this is fixed now
You are great Chris
Bojan
Now MDI is working like it should it finished the first command and even during execution of first command i enter second one the mdi finishes first and start second command. I think this is fixed now
You are great Chris
Bojan
Please Log in to join the conversation.
5 years 10 months ago #192285
by cmorley
Replied by cmorley on topic Learning to work with new QTVCP screens and handler
thank you for the report and update!
Please Log in to join the conversation.
5 years 10 months ago #192418
by Pro_El
Replied by Pro_El on topic Learning to work with new QTVCP screens and handler
Hello Chris. Perhaps is not a issue but missing future maybe in QTVCP widgets. GCodeGraphic did not show rotary A axis visual. I tested same ini on Axis and on QT dragon on A axis and it show visual rotation of 360 deg only on Axis screen. In QTDragon it's standing and only DRO is counting for A axis. I put A axis DRO my self. Is this a missing function of GCodeGraphic or i am missing something.
Thanks Chris
Thanks Chris
Please Log in to join the conversation.
Time to create page: 0.096 seconds
