8d522de7e7
drop some unnecessary logging when ignoring request replies
2013-06-21 16:39:04 +02:00
81ae4c8d4d
forgot about pairing notification on receiver...
2013-06-21 16:32:29 +02:00
c1aa341a7a
tweaked timing of enabling receiver notifications
2013-06-21 15:20:52 +02:00
fd35f23af7
one a separate flag to check if the device is active
2013-06-21 15:17:14 +02:00
c04851f64e
better handling of timeouts in base.request
2013-06-21 15:05:48 +02:00
431f1c97cf
added read/write_register to receiver and devices
2013-06-21 15:03:36 +02:00
1b68a3d5a9
fixed request timeouts for devices
2013-06-20 19:51:54 +02:00
1d9a3bf23a
fixed checking for features of offline 2.0 devices
2013-06-20 17:21:23 +02:00
3d8c764eb0
relax timeouts for device requests
2013-06-20 17:13:49 +02:00
31e134c1e0
don't wait so long on the first idle poll
2013-06-20 13:12:29 +02:00
ca9825d262
support for the VX Nano mouse
2013-06-20 13:10:30 +02:00
1a36ec65ee
faster checking of feature-based settings
2013-06-20 12:55:48 +02:00
d07a20e6f8
improved reading device properties
2013-06-20 12:54:27 +02:00
783b317281
added a protocol field to the device descriptors
2013-06-20 11:04:17 +02:00
4bc525f250
minor clean-ups
2013-06-20 11:02:45 +02:00
11cfc7ea09
enable notification on recevier as soon as possible
2013-06-19 19:46:54 +02:00
a806f2672d
group all status keys into one object
2013-06-19 19:45:39 +02:00
b4bca4670b
cache notification flags when possible
...
avoids unnecessary reads from devices when the status hasn't changed
2013-06-19 17:03:01 +02:00
4af714f1dd
K750: register the FN swap setting statically, no need to detect it at runtime
2013-06-18 16:48:02 +02:00
836719587c
renamed NANO receiver id
2013-06-18 16:45:44 +02:00
57c759773a
attach configuration to device settings objects
2013-06-17 11:00:53 +02:00
9d6402a4f7
shorter thread name on receiver listener
2013-06-17 08:00:17 +02:00
04ea8293a8
persist and restore device settings
2013-06-16 17:41:03 +02:00
febf571d84
account for devices going out-of-range while active
2013-06-16 17:10:46 +02:00
8852d50971
mark device status as inactive after idling out
2013-06-12 14:31:46 +02:00
d9801e2d57
fixed firmware info for some HID++ 2.0 devices
2013-06-12 14:21:31 +02:00
5cf6777340
more tweaks to idle polling
2013-06-08 21:06:52 +02:00
17863c85b6
fixed querying for known registers
2013-06-08 21:06:22 +02:00
237d0f9d9a
keep the battery level if polling the device marks it as offline
2013-06-08 21:05:30 +02:00
d01d9edb78
tweaked idle polling timings
2013-06-08 16:27:03 +02:00
b2b4febd31
receiver notifications: don't set all flags, might fail
2013-06-08 16:18:10 +02:00
ad67e6eaee
fix read timeouts in base.py, use seconds everywhere
2013-06-08 16:17:14 +02:00
ed5ce48f65
fixes to polling receiver/device status
2013-06-08 16:16:12 +02:00
46544e1cbe
listen for udev events on the GLib main loop
2013-06-07 14:39:04 +02:00
c52f2fc069
fix descriptor for K700 keyboard
2013-06-05 01:24:19 +02:00
c186573775
fix register blacklisting
2013-06-05 00:31:40 +02:00
cbdc0bd99b
very low battery level should trigger an attention event
2013-06-03 21:40:15 +02:00
bfe7bcf1b4
avoid possible race condition on device initialization
2013-06-02 11:19:30 +02:00
c61eb3f039
show charging status in device icon
2013-06-01 22:08:14 +02:00
83a29328c7
don't use notification flags with HID++ 2.0 devices
2013-06-01 15:07:39 +02:00
39e630cece
cli: improve alignment for special keys
...
The following lines have an insane length and are therefore not included in the
longest line:
WIN7_MONITOR_SWITCH_AS_WIN_SHIFT_LEFTARROW=0x0093,
WIN7_MONITOR_SWITCH_AS_WIN_SHIFT_RIGHTARROW=0x0094,
While doing this, also fix an obvious typo in the "Lock PC" control.
2013-05-27 14:07:38 +02:00
b2a62c2dd7
special_keys: update controls list
...
My previous observation was right, controls and tasks are really different
entities. The following "controls" appears to be invalid and have been removed:
Home=0x001A,
Music=0x001D,
Search=0x0029,
Sleep=0x002F,
2013-05-27 11:44:20 +02:00
6ae11f862c
Add more feature names, rename existing ones
...
Extracted from SetPoint 6.52.74 software using:
<FeaturesSupported.xml awk -F\" '/<Feature /{sub(/^LD_FID_/, "", $2); printf("\t%s=%s,\n", $2, $4)}' | sort -t= -k2
Existing names are renamed to the newer, verbose names.
2013-05-26 23:47:40 +02:00
28c35633d3
Add more tasks for special keys
...
Based on tasks.xml from `%ProgramFiles%\\SetPointP\\tasks.xml`.
2013-05-26 22:47:03 +02:00
6e36e33b22
Decouple controls from tasks (programmable keys)
...
They are treated differently in the HID++ 2.0 specification. Observations seem
to confirm this difference. For instance, a part of solaar-cli's output:
0: unknown:0022 => Home FN sensitive, is FN, reprogrammable
1: Mail => Mail FN sensitive, is FN, reprogrammable
2: unknown:003E => Search FN sensitive, is FN, reprogrammable
2013-05-26 22:47:03 +02:00
e73f076324
don't support the VX Nano right now
2013-05-22 20:43:29 +03:00
131f8f7f45
disable status polling on devices
...
the regular flow should be reading the battery on all devices now
2013-05-22 20:42:26 +03:00
c3b73964d5
improved support for some Nano receivers
2013-05-22 20:41:11 +03:00
790fc7c04b
improved support for the Nano receiver
2013-05-22 07:31:16 +03:00
9c0dac044c
hid10: update 07 battery parsing based on spec
...
This fixes pwr/Solaar#49 partially, at least the charging state will be reported
correctly hereafter. The charge level may still be incorrect though.
2013-05-22 00:10:17 +02:00
da6711c93c
the 'Solar key' on K750 is named 'Light Check button'
2013-05-21 00:48:21 +03:00
d3dcdcb92e
Merge remote-tracking branch 'origin/master'
2013-05-19 11:54:38 +03:00
f0542923d7
hid10: update flags description for notifications
...
The Logitech HID++ 1.0 documentation actually names the fields for devices and
receiver. Clarify that and explain why enabling all of the bits is a bad idea.
2013-05-19 10:30:41 +02:00
29d0c07164
hid10: Formatting and re-order NOTIFICATION_FLAGs
...
Align values for easier reading the numeric values of NOTIFICATION_FLAGs. To
maintain consistency in the ordering of the values, swap keyboard_backlight with
keyboard_present.
2013-05-19 10:20:21 +02:00
152abb086a
hid10: document notifications better
...
See [registers.txt][1] for 'keyboard_backlight'. The behavior of
keyboard_sleep_raw and keyboard_multimedia_raw is described at
[keyboard.txt][2].
[1]: https://git.lekensteyn.nl/ltunify/tree/registers.txt
[2]: https://git.lekensteyn.nl/ltunify/tree/keyboard.txt
2013-05-19 10:14:31 +02:00
ef62892f60
pop up a desktop notification if the battery is below 5%
2013-05-18 14:35:33 +03:00
7ae24488d9
only notify on connected devices at start-up
2013-05-18 02:20:22 +03:00
317cf6d00f
only enable certain notification flags on devices
...
Also added some documentation to the notification flags, where possible.
2013-05-18 00:15:42 +03:00
a5eeac6e5a
enable notifications for peripherals; fixes #27
2013-05-17 23:06:24 +03:00
c20b279362
minor tweaks
2013-05-08 12:06:01 +03:00
8d5ca66db7
get rid of bad map() calls
2013-05-06 17:51:03 +02:00
3ecfdd027e
handle all 07/0D register notifications
2013-05-06 17:08:58 +02:00
55ca9927b0
python 2/3: fix handling of first argument (unicode) of pack/unpack
2013-05-06 16:50:17 +02:00
0283bb0e91
fix str/unicode detection in Python 3.2
2013-05-06 15:33:42 +02:00
d39c0995b6
Merge remote-tracking branch 'origin/master'
2013-05-06 14:55:21 +02:00
db4c088ce9
Merge pull request #37 from Lekensteyn/py3-compat
...
Py3 compat: replace use of "unicode" (pwr/Solaar#32 )
The `u''` syntax fails in Python 3.2; will fix is_string after the merge.
2013-05-06 05:54:53 -07:00
a4898e24b7
extended documentation of descriptors and registers
2013-05-06 14:51:57 +02:00
1f48e44cc6
Merge remote-tracking branch 'origin/master'
2013-05-04 20:20:43 +02:00
9d8743e765
comment-out descriptor settings for Anywhere MX, not actually tested
2013-05-04 20:18:10 +02:00
2327a0012e
descriptors.py: Clarify use of negative values
...
The negative behavior is not obvious, document it in the descriptors.py file
such that people who edit it to add new devices know how it works.
2013-05-04 20:02:37 +02:00
e819265e7e
fix automatic register blacklisting
2013-05-04 19:50:08 +02:00
d7dd9393ff
minor clean-ups
2013-05-04 17:19:48 +02:00
64c36a1562
updated descriptors table and the devices doc
2013-05-04 17:18:39 +02:00
13a54565ba
cleaned-up the descriptors table
2013-05-04 15:09:50 +02:00
ad577d22d0
handle sleep in udev monitoring, fixes #35
2013-05-04 12:19:29 +02:00
10c26fe642
Py3 compat: replace use of "unicode" ( pwr/Solaar#32 )
...
Generating "an unknown notification" type bailed out because of an unknown
feature type None. Since `isinstance(other, str)` is False for None, the script
will raise an exception on `isinstance(other, unicode)`.
There is no differentiation between `str` and `bytes` in Python 2, therefore
add another condition to `NamedInt.__eq__` to catch unknown types (like
`bytes`).
2013-05-03 23:46:46 +02:00
2ee2a5dc46
Merge remote-tracking branch 'origin/master'
2013-05-03 17:08:32 +02:00
430fdf4fcf
initial support for the MOUSE_POINTER hid++2.0 feature
2013-05-03 17:08:26 +02:00
a0a76f738b
assert that data read/written on the receiver handle is of type bytes
2013-05-03 16:35:28 +02:00
266edd80f3
Process reg07 battery notification
2013-05-03 00:10:58 +02:00
d1b1be32ca
Make read_battery use set_battery_info
...
This allows battery readouts to generate warnings and debug logs for a given
status and level.
2013-05-02 23:56:08 +02:00
fbdd923d43
Refactor battery info update
...
- `self[BATTERY_STATUS] = BATTERY_STATUS[battery_status]` should be:
`self[BATTERY_STATUS] = _hidpp20.BATTERY_STATUS[battery_status]`, otherwise
the battery status would be a single char from the string `battery-status`.
- Make `_hidpp20.BATTERY_OK` check against strings instead of a number.
- Move setting battery information to a separate function, `set_battery_info`.
This prepares for notifications when a battery error/warning occurs.
2013-05-02 23:51:40 +02:00
d8e469a33a
hidpp10: split reg07 (battery) parsing so it can be reused
2013-05-02 23:06:45 +02:00
0f80901bce
quicker detection of matching receivers in udev
2013-05-02 11:11:53 +02:00
c829304e31
use only udev events to detect receiver devices
2013-05-01 15:47:23 +02:00
d3f94ff2fb
detect some HID++1.0 custom battery notifications
...
they're not handled yet
2013-05-01 11:36:15 +02:00
04db6d3838
python 3 fixes for #29
2013-04-30 22:31:06 +02:00
feedbcf581
some code clean-ups
2013-04-28 15:16:45 +02:00
a57f3be58d
renamed event alert levels to be more clear
2013-04-28 15:12:20 +02:00
897dffc426
only dispatch notification events from the specialized listener thread
2013-04-28 15:09:09 +02:00
6f0b61e6d8
better handling of eq/ne/hash in receiver and device objects
2013-04-28 15:02:17 +02:00
674ee9ac9e
split read_battery in status into its own function
2013-04-28 15:01:27 +02:00
5eab013cf6
more explicit logging
2013-04-28 14:58:40 +02:00
079ef8d800
incipient support for the Nano receiver
2013-04-28 14:27:16 +02:00
c4dc49ac5e
Merge pull request #24 from Lekensteyn/hid10-fnkey
...
Add FN key swap support for K800 (and presumably K710)
2013-04-28 02:03:33 -07:00
5e58f1e273
Fix battery status reading, add "fully charged"
...
Commit 438c501fae
2013-04-27 17:07:55 +02:00
c79ad65d37
Add K710 with FN key swap support ( pwr/Solaar#18 )
...
The K710 keyboard is (according to the issue reporter) part of a MK710 combo
(which also contains a M705 mouse). Observing a succesful 07 register read,
I think that it is a HID++ 1.0 device too that uses the same register for FN
key swapping as K800.
2013-04-27 15:17:05 +02:00
95a97ad776
Support FN keys swap for K800
2013-04-27 15:13:42 +02:00
6c28cedf23
Make BooleanValidator accept bytes too besides int
...
Previously, only the first parameter byte can be read or written. After this
patch, it is possible to select/write more bytes by specifying a mask of type
bytes with the appropriate length.
2013-04-27 15:12:55 +02:00
438c501fae
Parse battery status of HID++ 1.0 devices
...
This applies to K800 but it seems also to apply to M510. The numbers are based
on the HID++ 2.0 spec that state the following for GetBatteryCapability:
If number of levels < 10 or if mileage is disabled then report are
mapped to 4 levels this way.
0%->10% critical
11%->30% low
31%->80% good
81%->100% full
i.e. to report battery low, FW send 25%, to report battery good, FW send 50%.
2013-04-27 11:58:09 +02:00
Daniel Pavel
Peter Wu