If there will be an INI option, it should be set a way, that on default jog rate and feed overite are not afecting each other.
IMHO : the complete development should go away as much as possible from INI settings. WINDOWS is not every time a good example, but in this case it is. Why did Windows work away from INI options ? Because Users do not like that way to edit options! And I feel the same, most users today are mouse movers and we should take care of it! Norbert Norbert Am 14.11.2014 um 16:46 schrieb Dewey Garrett: > I have pushed a new branch (dgarr/jog_no_fo based on master) > with a patch for: > jogging: ignore feedoverride > > The commit message points out a number of existing methods for > controlling jog rates: > > Prior behavior: feedoverride affects: > 1) wheel jogging (axis.N.jog-*) > 2) halui jogging (halui.jog*) > 3) axis ui jogging > > New behavior: feedoverride ignored for motion_state==EMCMOT_MOTION_FREE. > > Notes: > 1) for wheel jogging, the jog rate can be managed > with axis.N.jog-scale, axis.N.jog-counts > (ref: man motion) > 2) for halui jogging, the rate can be managed with > halui.jog-speed (for plus/minus jogging) > (ref: man halui) > 3) the axis ui provides individual sliders for both > linear and angular jog rates > ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
