I strongly disagree with you from two points of view: 1. freedom - the component is great and it would be even greater with a bit more freedom. 2. In my opinion, control has to be fast and simple. And user / customer is always right. At least almost. And when he brakes something due to what he asked - let him decide, don't push.
Instead of forcing user pushing step button 4 times every time he wants to reduce the step, we could take some measures to make unintended cycling to highest step harder or to be noted by sound, indicator, vibration, etc. Or even use two buttons - one for increasing and one for decreasing step size, without rollover. I configured this pendant before 2.6.0 was out and I made changes to .cc file to invert stepsize direction. And the user was very happy till 2.6.0 has overwritten my compiled component. One more question / idea is to let user select step sequence freely, I mean instead of default: 1,10,100,1000 something like: 1000,200,50,10,1 Is this possible? Can pendant display any number in stepsize position? On 2014.09.13 19:12, Dewey Garrett wrote: > We could implement an additional stepsize-down input for use > instead of stepsize-up but I am not sure it is a good idea. If > the user does not carefully note the displayed increment value > and pushes the step button to do stepsize-down, a rollover to > the largest increment may be a big surprise when the user next > clicks the MPG. > > When using the current implementation with stepsize-up, an > inadvertent rollover to the smallest increment may be a surprise > but is less likely to crash a machine. > > The existing implementation aligns with the button names on the > pendant and is simple. Cycling throught four stepsize increments > is fairly quick and encourages the user to look at the displayed > increment value when choosing a smaller increment. It seems to me > that adding provisions for stepsize-down would add complexity and > increase chances for operator error. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
