Per-User Settings?
 

For Windows computers with several user accounts -- as I recall, the MA2.6 settings were "global".

I haven't had time to test this with MA3, but I thought I would just ask: are the MA3 settings "individual" per user? Or "global" (per computer)?

Answering my own questions:

I tested it (on Vista 32), and the MA3 settings are per-user.

So, I also tested MA2.6 on the same system, and those settings are per-user too.

Sorry for wasting everybody's time. :o

I actually didn't know whether it would turn out to be per-user or not. I thought each user might have their own Registry, but I wasn't sure.

It comes down to whether you are poking CURRENT_USER or LOCAL_MACHINE.

OK, so having settled that -

When the "custom logos" feature of the clock is added, can that also be a "per user" thing? Please.

It would be stored in the same Registry key, so yes.

Does this mean the key code is stored on a per user basis as well? I'm thinking some will be confused about having to enter the key code more than once.

Keycodes are written to both CURRENT_USER and LOCAL_MACHINE.
So if the user does not have admin privilege then it will only write it to CURRENT_USER so it will ask for keycodes per user.

Screensaver settings are CURRENT_USER only so each user should have their own settings.

The Images for the Crystal are save in one area so it is shared with all users.

Thank you! :)

MA3's settings is hacked right now to work with MA2.6 keycodes and I haven't look at the source code changes so I don't know how it is setup right now.

Perhaps my question wasn't clear. I know that the images are saved in one shared area with MA2.6 So, with MA2.6, every user has the same (set of) image(s).

I was requesting that, with MA3, each user be able to have different image(s). That is, different images from other users.

That's a "feature request" -- submitted before the feature has been rolled out to the Beta bunch.

Of course, if the feature is already there/planned, then this isn't a "feature request" it's a "Thanks". ;)

A logo picker would remedy this. Then it would be per-user in the Registry, rather than a global scan of the appropriate Program Files folder. And P.S. please make it read PNG out-of-the-box. :)

Looks like years of Registry and interface programming purgatory for me, instead of bringing the background to life.

JimS,
I am here to help. I am just having problem figuring out which ones you need me to do to complete MA3.
Just let me know in Qtask which ones you need me to work on.

Sorry. Most of us here in the Beta forum don't have any idea who is doing what.

All we can do is comment on the result (and suggest reasonable characteristics for the result).

Edgar has been kind enough to help me out, but he has a day job - working on Qtask, Prolific's world-changing management software.

Thanks for the info. And thanks, Edgar (and any others who are helping).

Clearly, the most important thing is trying to get MA3 released before Windows 7.

However, I would hate to see the software structure built so that enhancements (like per-user logos) would be impractical, and/or would not be upward-compatible with MA3.1, etc.

By the way - who is going to write the "installation" software? I hope that's not going to be a stumbling block.