qtvcp issues

Ok I have the zoom buttons working now. I was zoom_in and zoom_out. It was not happy about the dash before in and out. When I enabled the DRO before the display becomes jerky and it seems like something is spending a lot of time trying to get something that it cannot find which causes the graph to be updated at a jerky manner and slower rate like one time per second.

There is something that bugs me about GSTAT. It appears to be responding to any event such a s a mouse click on either one of my monitors and not just just events that take place in the area of gui. I suspect this is the way GSTAT works but it does not seem proper to me.

auto-mation-assist wrote: There is something that bugs me about GSTAT. It appears to be responding to any event such a s a mouse click on either one of my monitors and not just just events that take place in the area of gui. I suspect this is the way GSTAT works but it does not seem proper to me.

GSTAT does not directly respond to mouse clicks or keystrikes.
GSTAT (in general) only responds to linuxcnc state changes.
Widgets can use the GSTAT system for communication of some actions, so I guess you could say GSTAT is involved indirectly.

What makes you think it's GSTAT that is the source of your bother?
What behavior is clicking on the screen doing that you feel is wrong?
What behavior would you have expected instead?

Chris M

i just pushed work (to master now) for more graphics view commands.
using action buttons or the ACTION library or calling gcode_graphics directly,
you can now:
set the basic view: X, Y, Y2, Z, Z2
clear the view: clear
modify the view: zoom-in, zoom-out, pan-up, pan-down, pan-left, pan-right, rotate-up, rotate-down, rotate-cw, rotate-ccw

Chris M

I’m not sure yet but its part of attempting to trace down what I think my observations tell me since its an event monitor. I think this is related to having a second terminal window open in my folder /home/cnc/qtvcp-dev and also one open and running linuxcnc itself as rip.

Sometimes doing something in second terminal widow will produce messages like this in the actual terminal running linuxcnc: task: main loop took 0.004563 seconds. It can occur even when linuxcnc is not actively being asked to do anything and is not not always consistent.

It may be nothing to worry about.

I was making some mechanical upgrades in my Z axis drive and remembered that I do not have a dro display for the mills knee yet which is really a convenience item. The knee does have a linear scale whose output I used to display.

The dro numbering does not have a 'knee' option for such purpose. The knee on my machine does have a drive motor but the knee is manually positioned when required. The motor has a hard time moving the knee up since there is no counter balance.

While writing this it comes to mind that the knee does not need a display if its output could be added or subtracted from the normal z axis value automatically. I will need to think more about doing that. Its output would then possibly show up in the z axis dro due to its modification to the z axis value.

On another item.

To day I'm starting on moving my automatic move out of limits function from hal into the gui. This function monitors all positive and negative limit switches. It activates with just a push of a button, drives the affected axis the correct direction no matter which switch is activated and stops when a switch flips back to normal. Most limits alarms for me are z axis related.

That message is nothing to worry about and has nothing to do with the screen.