WhatPulse 2.0.1a

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.

You can find them here:

http://whatpulse.org/etc/whatpulse-win-2.0.1a.exe
http://whatpulse.org/etc/whatpulse-mac-2.0.1a.dmg
http://whatpulse.org/etc/whatpulse-linux-32bit-2.0.1a.tar.gz
http://whatpulse.org/etc/whatpulse-linux-64bit-2.0.1a.tar.gz

Here’s a list of addressed issues:

  • Random crashes when using wireless network
  • Heatmap doesn’t update ‘today’ - until the next day
  • Random crashes when coming out of hibernation
  • Unable to set a proxy when logging in
  • Auto pulsing disabled too quickly when detecting pulse errors
  • The client does not see certain USB network adapters
  • Computer crashes can cause the client to ask for a login, next startup
  • Windows closes input hooks when putting your CPU under load, which makes it stop counting.
  • Add some critical keys to keyboard heatmap
  • Only show active metrics in tooltip (icon hover)
  • Allow a password reset without knowing the old password
  • Update Windows installation to include explanation of WinPcap
  • Update (Windows) network interfaces immediately when they change

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.

Amazing work guys!

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. :wink:

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.

Nice, thanks. Downloading now and I’ll install it on all my pc’s later today

Indeed it would be, maybe in near future :slight_smile:

Turned off aero (uxsms) with command line, waited more than 2min, still no count. Did some random clicks while waiting.

Turned on aero (uxsms) with command line, waited more than 2min, still no count. Aldo did some random clicks.

Still no counting.
After restarting it started counting. Hope this helps.

[quote=“eTheBlack, post:7, topic:10919”]Still no counting.
After restarting it started counting. Hope this helps.
[/quote]

I suppose you mean with “After restarting it” - restarting the client?

Anyhow, I’ll leave that for now…it’s not like people restart aero every day…

I suppose you mean with “After restarting it” - restarting the client?

Anyhow, I’ll leave that for now…it’s not like people restart aero every day…
[/quote]

Yes that what I meant. I don’t have a problem with it, but aero isn’t quite stable on every PC, as on mine and yours :stuck_out_tongue:
So I thought I give a heads up.

Liking this update, it loaded on the first attempt at opening it, unlike 2.0

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.

http://img10.imageshack.us/img10/8499/whatpulse201a.jpg

Seconding this, I, however, am running on W7 x64. It just randomly crashed.

But wait, there’s more.

While watching a movie for over an hour I got the following on my screen, out of nowhere (I wasn’t touching the mouse, or keyboard):