|
From: Guido S. <gui...@ba...> - 2012-10-29 22:20:38
|
Am Mon, 29. Oct 2012 um 19:35:45 +0100 schrieb Matthias Trute: > Hi, Hello Matthias, > There are only a few general options at all > > device > verbosity > use_watchdog > restore_device_settings > auto_power_on > speed > auto_speed_detection (? why is this not an option for speed?) because this would mix up two different meanings in one variable. > esp the device settings are commonly used (except for auto_speed, > which does not makes sense for at least the marklin 6051 interface). > On the other hand, there are now very different methods for a device, > that makes it troublesome to integrate serial lines, CAN devices, > ethernet targets (with and without IP) into one settings schema. You are quite right, but the real root cause for this trouble is not to have the different options for different devices but the variable evaluation of "general" options and "module specific" options. The implementation of the config file layout is just erroneous. The sequence of options for a specific bus should not result in different server behavior respectively ignoring one option or not. To remove or rename one or another option will not change this error. If we chose my proposed layout, all options will be on the same level, independent if they are general or specific and in what sequence they are listed. The transition to this new file format is not really pleasant for users used to the old format. That is quite clear. Guido -- http://www.bayernline.de/~gscholz/ http://www.lug-burghausen.org/ |