Dear List, Simon
Thanks Simon for your kind reply and explanations
So although there might be space for calling that behavior an additional but questionable 'feature', i consider it an inconsistency in user interface design. Preferences are preferences, whether they are in a .pdrc file or in a preferences file.
IMHO -noprefs should disable all preferences-mechanisms.
Regards,
Peter
simon wise wrote:
On 1 Dec 2007, at 10:11 PM, Peter Plessas wrote:
i thought that the -noprefs flag also disables loading of the .pdrc file on linux, but it does not. Is this intentional on 0.40-2?
Since the preference dialogues were added they have always been treated as quite separate from the older .pdrc system - IMHO this split remains useful as it is possible to either ignore the older system (just delete any .pdrc files) or use it instead (delete the settings files instead) or use both in parallel to help manage your settings in different ways for different circumstances (eg using the .pdrc to set up machine specific things like which soundcard to use while selecting libraries and startup patches with the preferences). The newer preference system is getting some very useful features - especially the embedded option! - and when the dialogue box eventually gets more than 10 slots I will use the .pdrc system less often.
simon