Giving this another thought, you may want to think about dividing
between user-specific and "global" state in general. This is not so
important if you don't want to persist the data, but if you do, you can
store user-specific data seperately. So this is not only helpful when
multiple users can
Sanjay,
I am not a big fan of Dictionaries for these kinds of things, but if you
need "named slots" for a previously unknown list of settings, the
approach you describe is perfectly okay, IMO.
This approach can also be extended into a database or any other kind of
storage and also stands the t
Hi
What is the usual practices in storing values of variables / parameters the
persist through an users usage of an application.
e.g. say the user logs in and then selects a current printer, current
company, accounting year and then moves between various application options
and eventually logs ou
