John Thornton wrote: > I have to disagree with this, you can have unlimited INI options if > you call them from your HAL file and as we all know this only confuses > new users when they see a snippet in the manual and assume that it is > used by LinuxCNC in some way other than how it is used to bring all > the settings to one location. The configurations should say in the INI > file that some settings are used by the HAL file and are only done > this way for convenience. When some sample configs use this and others > do not it only adds to the confusion. > > Imagine your an adventurous type and you roll your own config. You > create a HAL file and load a pid component and by looking in the > manual you assume you put the P, I, D, FFx settings in the INI file... > this is so totally wrong and confusing to a newbee. I finally > understand what the code words (in HAL) mean :) Yes, if the docs don't adequately describe how this system of putting settings in the .ini file and then having HAL code in a HAL file that reads them and makes the settings to the HAL component, then it does need to be put into the docs. It should at least be documented one place, and any HAL component doc that says the settings come from the .ini file should be corrected.
Jon ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
