We’re releasing a preliminary 2.0.1(a). This should address most issues seen by users. It’s obvious there were some issues with 2.0, and we’ve been working on it since users detected these.
This release is not yet on the main website, because we would like to see if most issues are indeed resolved.
Yay, it seems to resume hibernation and sleep fine on my laptop now, and no longer crashes when disconnecting/reconnecting to wireless networks, I’ll edit this post or make a new one if it somehow still happens to crash. But good job so far, I can finally track network bandwidth on my laptop now.
Running game in fullsceen doesn’t stop counting anymore.
That is for Windows x64.
So thanks for this quite fast update fix.
Edit:
Power shortage isn’t a problem anymore. It doesn’t ask for log in details and settings are saved, thought you lost few seconds of data (keys, clicks, etc.) before shortage.
But there is still a bug that stops counting key and clicks if you disable aero with command line, and also if it crashes. Restarting app fixes it, but if you enable aero back, you must restart app again.
That’s to be expected…it would be great if Windows would announce there will be a power outage…but then it wouldn’t be an outage.
How long after disabling aero did you wait? There’s a timer (60 sec) that checks whether the keyhook is still alive. If not, the client will restart the keyhook.
Still crashed under Windows 8 x64. About six minutes or so after installing. I was using Opera to reply to a thread on this forum, and after clicking reply and while the thread was loading, WhatPulse kicked the bucket and I had to manually restart it.
Switching user/remote desktop issue not fixed.
Whenever I switch to other user and back to my account, Whatpulse client stop working with black borders in its windows. So I have to restart the client everytime my father using my PC. I thought this would be fixed with Hibernation issue, but I guess it’s not.
This problem didn’t happen with version 1.7.0 and this happens both Win 7 and 8.