As of 1.8.4 Windows Vista says that Workrave needs elevated privileges in order to run.

It is probably necessary to run Workrave with a high integrity level so that it can communicate with all applications on the desktop in Windows Vista. You can check out bug #590 to see what I'm talking about.

(In reply to comment #1)
> It is probably necessary to run Workrave with a high integrity level so that it
> can communicate with all applications on the desktop in Windows Vista. You can
> check out bug #590 to see what I'm talking about.

This would make sense. That said, I would much rather have Workrave not detecting activity in applications running in an elevated state than be required to run in an elevated state. Workrave has no business running at a high integrity level and not everyone has administrator privileges.

(In reply to comment #2)
> This would make sense. That said, I would much rather have Workrave not
> detecting activity in applications running in an elevated state than be
> required to run in an elevated state. Workrave has no business running at a
> high integrity level and not everyone has administrator privileges.
> 

I see what you mean. UAC requires you to start Workrave 1.8.4 as an Administrator even if you set your security policy to run the program as a basic user. It still runs with high integrity if you use icacls to set the integrity level to medium. I don't know if that's UAC auto-detection or if that's intended with a program manifest.

I changed Workrave 1.8.4 to request administrator privileges (using a manifest file) because otherwise Workrave did not monitor activity in a DOS-box. It seems that this is no longer needed: Workrave now uses low-level keyboard/mouse hook to monitor users' activity.

The next nighly build (>= March 28) will no longer request admin privileges.