> > > > >Yes. Keyboard and click on radio button both change so the Tool > > > buttons refer to the correct axis. But Pendants don't seem to have > > > that feature. John > > > > If a USB (or in this case a Ps/2) keyboard can do it, then somewhere > > in the code for that, there must be a way to get any other device > > connected by USB to make the same GUI updates. > > > > Or am I just being naive? > > > > Martin > > > > Mouse and keyboard inputs are handled very differently from those on a > > pendant. The mouse and keyboard are part of the user interface and > > get to Linuxcnc through Axis or what ever UI is being used. Pendant > > inputs get to Linuxcnc directly through Hal. This has the advantage > > of being real-time and independent of userspace hangups, but has the > > disadvantage of not being easily tied into the UI. > > > > Todd > > I had suspected as much, but in this case its (this jogging from a mesa > encoder input dial) is all handled by hal, which IIRC sends it to > motion, never getting anywhere near axis. So it would be totally > dependent on motion telling axis, I think. > >
Actually not quite since you'll notice the DROs on the screen change so stuff does go back. Once the signal from the keyboard or display radio button sets the axis there is no need to feed back to the AXIS radio button which is probably why it was never exposed for setting externally. So yes, the MPG does get near AXIS but not the part we want. BTW, the example I showed written in Object Pascal is very simplistic and is fixed at 3 axis. The AXIS software reads the INI file values to determine what to display. But even it's kind of broken. The [TRAJ].COORDINATES.value set to XYZA assigns the X to joint0, Y to joint1 and so on and you see the 'A' radio button on the screen. Set it to only XYZ and you only see 3 radio buttons. But swap those around like AXYZ and now the AXIS radio button marked X spins the Y axis. The Y button spins the Z, the Z button spins the A axis and the A button spins the X. And yet, the arrow keys still spin the correct axis. The [DISPLAY].GEOMETRY.value set to xyza doesn't seem to affect the radio buttons. I think it impacts the trajectory display but haven't looked further into that. I think AXIS python code counts the number of letters and uses that to put XYZ A Radio buttons on the screen but it gets confused with the mapping to the +/- buttons while the keyboard doesn't seem to care. John _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
