On Sunday 03 October 2021 10:27:22 Gene Heskett wrote: > On Saturday 02 October 2021 14:50:09 Gene Heskett wrote: > I'm being ignored, why? > > > Greetings all; > > > > The attached file would be quite a bit easier to trace and hook up > > in a .hal file if it was subjected to the joints update script. > > There now exist in both the listings for halmeter, halshow and > > halscopeidentical names for signals I need, some of which I have > > been able to exercise to prove they would work, but some, like jogs, > > don't seem to be valid signals although they'll show in halshow too.
Attachment not sent again. > I have it hooked up, I think, but its not working, because applying a > logic true to "halui.axis.z.select" has no effect when the gui is > showing x button is active. And vice-versa. Anybody have an idea why? I've poked around on another wintel box, and am getting the same results. I cannot select the active axis as seen in the axis gui and in the axisui pins, with a signal from any halui pin that claims to be a select (axis| joint) input pin. The other halui pins say it worked, but the gui does not change. So its not pi specific. There appears to be a disconnect between the halui*select input pins, and the axisui output pins. The axis gui's active axis buttons only follow keyboard or mouse for axisui. But most of the halui.axis and halui.joint stuff, while they seem to work for halui, have no effect on what the gui shows. The gui responds to the keyboard and the mouse, but not to halui. Thanks all. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
