>
> If you need to overwrite user defined values, via the command line
> argument, you probably don't want to persist these values. While we
>
Exactly. The requirement is to override the preference value but
*preferably* without overwriting the user's settings.
Not overwriting the user's setting is not an explicit requirement from the
project, but the users already told that it would be annoying for them
otherwise. That is, we can go with the persistent solution, and strictly
saying that would satisfy the projects' requirements. But if it is not much
more work, it would be better to come up with a solution that does not
overwrite the persistent settings to make the users happy. :)
could think about a command line approach, the
> berry::IPreferencesService interface will persist all values, so a
> solution would require more "thinking". Furthermore, what value should
> be used if the user changes a preferences in the preferences pages for
> which a command line value was given?
>
Good question. I think, it should show the persistent settings.
Cheers,
Miklos
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
