What's new with WhatPulse?
Use setting
Include beta releases
WhatPulse 2.8
December 27, 2017
🎉 New Features
- Introducing Milestones: A way to get notifications when you reach certain statistics (e.g. every 1000 keys) and notify that you've earned some coffee.
- Add the ability to filter on the type of network traffic; wireless or wired.
- Add support for network hardware offloading. This means the client is way more accurate with network bandwidth in certain hardware setups.
- The Client API now has a new endpoint (/v1/realtime) to collect real-time information (keys per second, bandwidth, etc.).
🐛 Bug Fixes
- Fix network latency spikes (slowness) on Mac OS 10.11+ when using wireless only.
- Don't crash on start-up when a network issue downloads a corrupted network-ports.csv file.
- Ignore Docker virtual interfaces which prevents the client from using way too much memory when Docker is running.
- Adjust the height of the Facts window so the letters aren't squished.
- Fix sharing keyboard and mouse heat maps on the website.
📈 Improvements
- Prevent the client from locking up when loading keyboard heat map data, when there is a lot of data.
- Don't ever show the updates window when a full screen application is active.
- Update our framework to Qt 5.9, which solved a few random stability issues.
- Properly scale a few interface elements when using a high resolution screen.
- Start to store the client settings online, so the client can restore them quickly when installing anew (restore is planned for next version).
- Add "Access-Control-Allow-Origin: *" to the Client API headers, so JavaScript can be used to query it.
WhatPulse 2.8.1
December 27, 2017
📝 Notes
- Linux: Please update to the latest stable OpenSSL version for your distro, otherwise the client will not work.
🐛 Bug Fixes
- Windows: Fix crashes every 17 minutes. This was caused by the database backup which was not handling itself well with the backend updates.
- Windows: Fix network monitoring on some systems. The monitor did not get a proper network interface name which it could use to monitor, so the monitoring itself did not start at all. Fixed this by translating improper network interface names into proper names which can be used.