941
General Mach Discussion / Re: New Mach3 v4 VB Interface
« on: October 17, 2009, 08:08:39 PM »Thanks Ray,Quote*** SetButtonText has always been there, but probably never documented. GetButtonText is new.Quote*** I will ask, but my guess is the answer is "no". OnPress, of course, you already have - the button script.
The main one to add for the buttons would be on release. Brian had said in the past he would add that function so hopefully it will be included. The others were just wishful thinking. As it is right now you can add a system function jog button that works as it should, but from VB you have to add a stop jog button which leaves a lot to be desired IMO. I never suggest a jog button be done from VB as it is now. Maybe this could be handled with a function (sysfunction&) and add VB to it? Some of the system functions versus VB do quirky things and maybe this would be a good option to handle that. I always prefer system functions to VB but if you want your buttons to do more than one thing you have to do them in VB. The jog stop on release is just one example but I think that function would add a lot of flexability (more than sysfunction&). Mouse is over would be great for interactive training screens but I knew when I mentioned it it was a stretch.Quote*** DoSpinCW() should not have been in there. DoSpinCW and DoSpinCCW are replaced by SpindleOn(DIR).Thanks for clearing that up.Quote*** All these are already accessible via OEM LEDs. I did not see the point in adding explicit functions for things that are available in OEM LEDs and DROsFair enough. Why are these (Sub SetIJIncremental(Boolean), Function IsIJIncremental() As Boolean)worthy of having their on functions and these (SetIJABS, IsIJABS) aren't?QuoteI think that any DRO or tick box in any and all config. pages should have associated DROs and LEDs that you can at least read and as many as possible that you can read/write to from VB would be great.I can't remember now what I was wanting to monitor and act on from VB at the moment. But then again there are quite a few I have had no need for in the past but I suppose someone has. It would also help with consistency IMO. Would certainly be able to build one heck of a diagnostics page though.
*** I looked at all the config stuff, and couldn't see any real value in making it VB accessible. Any examples of some that would be really useful, and for what?
Thanks,
Brett
Brett,
I will pass all your requests along to Brian, and see what he says. I certainly agree it would be nice to have the OnRelease calls for buttons. My own experience is pretty limited, so it's hard for me to know what's really useful and what's not, unless it's something I've needed myself.
Regards,
Ray L.