Work needed

[bstiq]

• Tour: display messages on each page instead of all at once. Issue need to store which messages have been displayed or not
• Test if pointing options persisted correctly in dilemma cirque trackpad
• Combos: add key selector at bottom
• push bkb-pointing-devices to bkb-develop, switch dilemma/all keebs to new branch, update docs
• Compile and test input devices for all keebs
• Switch to module memory space with latest qmk develop code
• layer color sync not working on older dilemma v2
• test dilemma v3 cirque works (weird serial speed issue)
• display keycode picker in combos screen
• some pid are duplicates in dilemma folder (at least 3x5_3, 3x5_3_procyon, 3x5_3_trackball, and 4x6_4 + 4x6_4_procyon)

per key RGB

• instead of reading key data one by one, read through a 32 bytes buffer

Fix other keebs and check they work:

• charybdis
• charybdis left
• cnano
• cnano left
• scylla
• skeletyl

Things to test specifically: per-layer RGB change (incl. persistent brightness), changing some keys and see if they update.

DPI Led indicator

Finish implementing DPI LED indicator on (specifically led min and max...):

• Charybdis 4x6
• CNano
• Dilemma MAX Procyon
• Dilemma Procyon
• Dilemma MAX Cirque
• Dilemma Cirque

More work:

• use keeb brightness instead of current MAX value

Optional

• pointing device minimum dpi/steps: TODO “set” functions and configure them?
• per key retro tapping : https://docs.qmk.fm/tap_hold#retro-tapping
• per key tapping term
• one shot modifiers
• dragscroll speed
• auto mouse layer trigger_enable ,trigger_threshold

ISSUES

• precision mode on dilemma making cursor jump: known issue, because we “compress” as there’s no DPI in digitizer mode. NOT solveable right now :(

• dragscroll invert on dilemma not working

• dilemma scrolling: create custom mouse report instead of mouse keys → will enable more natural feeling

• Force finger lifts when changing dpi? Isn't that solvable in code?

George implied he's planning to solve that on his end. But I'm sure you could work around it in the interim:

If you forced lifting before changing, then changed, then allowed the finger down again, it would look to the os like you just repositioned your finger closer to the center, which wouldn't cause movement.

• Invalid API data: bastardkb/dilemma/3x5_3: split.serial.speed: '4' is not of type 'integer'
• dilemma 4x6: error: 'ARGOS_OFFSET_POINTER_CONFIG' undeclared (first use in this function); did you mean 'ARGOS_OFFSET_CONFIG'?