docs: Improve pointing docs #2703
Conversation
|
|
||
| The details will depend on if you are adding a pointing device to a [split peripheral](../../features/split-keyboards.md#central-and-peripheral-roles) as opposed to a unibody keyboard or split central part: | ||
| Pointing devices are also supported on split peripherals, with some additional configuration using the [input split device](../../config/pointing.md#input-split). | ||
| The configuration details will depend on if you are adding a pointing device to a [split peripheral](../../features/split-keyboards.md#central-and-peripheral-roles) as opposed to a unibody keyboard or split central part. |
There was a problem hiding this comment.
| The configuration details will depend on if you are adding a pointing device to a [split peripheral](../../features/split-keyboards.md#central-and-peripheral-roles) as opposed to a unibody keyboard or split central part. | |
| The configuration details will thus vary depending on if you are adding a pointing device to a [split peripheral](../../features/split-keyboards.md#central-and-peripheral-roles) as opposed to a unibody keyboard or split central part. |
| @@ -1,30 +1,48 @@ | |||
| --- | |||
There was a problem hiding this comment.
Should we mention somewhere in this page that designers can default ZMK_POINTING to y using the .defconfig file?
|
|
||
| </Tabs> | ||
|
|
||
| ); | ||
|
|
There was a problem hiding this comment.
I think the tab selector goes here and the other two tab appearances become invisible.
There was a problem hiding this comment.
As long as the selections are synced, I think having separate tabs isn't bad. I find it confusing when you select a tab and it affects things way down the page, and you can't switch back without scrolling to the top.
There was a problem hiding this comment.
How about just moving the first tab with the trick and leaving the second untouched?
|
|
||
| Second, the input listener for the central side is added here, but disabled, so that keymaps (which are included for central and peripheral builds) can reference the listener to add input processors without issue. |
There was a problem hiding this comment.
This sentence feels like it needs some rephrasing. Also, for a split keyboard with a pointing device on the central, I think that there might be some issue where the peripheral needs the listener. Don't think that's accounted for in the docs atm.
A few miscellaneous tweaks to improve the newly added pointing-related docs:
&mscvalue in exampleLast one was discussed in the 2477 PR review. Feedback welcome on the approach, though I feel this is the best way. (Unfortunately the diff is hard to follow due to many moved chunks, so you might want to review the final page.)
PR check-list