dos authored 1 year ago and dos committed 1 year ago

That's how the real thing behaves.

we're already changing a bunch, this one looks silly but it does
affect how user interaction affects calibration at boot. also file
access does weird stuff in general, maybe it does weird stuff to
captouch output too, so an early exit when called from mp is maybe
beneficial.

there's many cleaner ways to do this but we intentionally just go
back to 1.2 status quo to account for any wonk that might be at the
bottom of recently reported boot calib failures. we'll move to
persistent calib soon anyways, no reason to go out of our way here :P

.down property was returning True only if the pressable was in DOWN state.
This leads to glitches, as because of key repeat it also goes through
REPEATED state while the pressable is being held, going against the
documented behavior. Fix this by considering both DOWN and REPEATED
states when evaluating the property.

still didn't get around to finish it right, it's in an awkward
in-between state and does not really build on the differences
to scalar yet.

with a tear in our eye we send it off to a nap, but like a
worm emerges from its cocoon to grow into a butterfly this old
companion too will see the light of menu again more beautiful
than ever before. sweet dreams, it won't be long.

This reverts commit 6df6c9a0.

Commit breaks changing of values.

dos authored 1 year ago and dos committed 1 year ago

Since !620 it happened much earlier, causing a lot of flickering at boot,
especially with plenty of apps installed. Move it back to until after
the application bundles are already collected.

Note that it happens a bit later than before now, as bundle processing
itself happens later because of being moved into the menu class, but
the end result is arguably nicer than before, as there's no weird
delay between setting the LEDs and showing the menu anymore.

Fixes: 06983264 ("Split sunmenu into its own file")

dos authored 1 year ago and dos committed 1 year ago

SunMenu is just a presentation layer that doesn't concern itself with
any kind of logic. It could be simply replaced with (already existing)
SimpleMenu and FlowerMenu or, in the future, may even become customizable
by the user.

Split the main menu's logic into a separate entity that delegates
the presentation to the class it inherits from, like all the other
uses of the menu system.

mitigates floating flow3r captouch threshold issues.
side effects unknown but there probably are some.
it's nice not having to care about EMI n'est-ce pas?

- petal pressed takes now raw data from all segments into account
- use ratios for positional captouch, improves "couch effect"
- position filter changes: comb->pole, before->after nonlinearity
- slightly better petal 5 missing data simulator
- troubleshooting section in docs

AFE would only get tweaked if it was necessary for the
last pad in the sequence. This can lead to random bad
calibration for any pads except for the last ones.

(also changed behavior to not autocalib in C on boot,
we're doing that OS-side anyways and alternate firmwares
also benefit from developers making an active choice.)

note to self don't just test with mpremote run :3