crelf

Do you have the build chekc box that includes custom error codes checked? I'm not sure if you need any of the custom error codes installed on your development PC - unchecking that might be a workaround. No idea on hte root cause though...

Oops - sorry, I stand corrected: yes, notifyicon works fine for me on XP - I was thinking about something else. Move along people, nothing to see here.

Can't imagine you're going to find anything - if your device is flaky at times, then dead reckoning might be your best bet. You can make it more robust by dead roeckoning way back to the base menu (or whatever it is) but knowing the depth of the deepest menu you ever enter (or that exists < safer) and escaping (or whatever) that many times to the base menu, and then renavigating back in from there. Horrible, yes, robust, mostly. Unless you can tell us what the instrument(s) are that you're looking at, that's about all I think I can offer.

I had issues using notifyicon on XP - I couldn't get it to work.

What do you mean "you people"?!?! Oh, they're all LAVA members... https://decibel.ni.com/content/groups/niweek-2011/blog/2011/07/19/why-do-you-come-to-niweek

I think that might be an option for distribution, but not development (eg: can't handle methods in SCC).

We use active directory - you can create groups, and add memebers to thsoe groups: then query the groups for their members - if the logged on user belongs ot the group, then enable the functionality. This is beneficial for several reasons, including the ability to decouple "admin"-like functions from actual software application admins and local (or network) PC admins (these two groups are rarely the same, so there's little reason to couple them), and also that you can manage user access remotely using native controls (I know ppl often shy away from asking their IT departments to do anything, but all they need to do is create the groups, and give you permission to add/remove people to/form them). It's simple, and it's easy to control.

Moderator's Note: mballa's Message Routing Architecture post was moved to its own thread here.

If you're worried about an undocumented feature going away, why not just add a sort after the read?

10% off coupn code: SHAREMEOFFER

I'd agree, but I feel that you should use the best tool for the job. Storing complex data as XML (whether using the built-in XML functions or the super awesome JKI EasyXML toolkit <- if you haven't tried it, get a demo copy and check it out) certainly fits the requirements of a lot of use cases, but one thing I like the class mutation history for is when I have a bunch of classes (let's call them plugins) that grow over the years, and now I want to add something to the class and/or deprecate something else, because my plugin interface needs to change - the mutation history can certainly help. I'm not saying it's perfect (eg: typedefs), but if you know that your class structure will change (eg: an app that's going to be in service for a looooooong time, with many new plugins coming online relatively regularily) then, with proper planning, it's a good choice.

I just ran a few tests - I can't see what the problem is

Tru dat! Unfortunately, getting to and from the Salt Lick is a problem. The Block (Diagram) Party is the official opening of the exhibition (downstairs in the Expo Hall), where you can wander the booths and have a few beers. From last year's NIWeek blog:

Cranky, yet you continue to remain polite - you must be English.