Repository navigation
WaEnhancer Community 0.0.8
WaEnhancer Community 0.0.8
SHA-256: 0f25cad1210863a70ddabb0b1aaab09418ea231c2342abd344fb4c51963c0dec
Changes since v0.0.7.
What's changed
- #60 Fix floating bar runtime preference transport
Full changelog
This section compiles the descriptions of the pull requests included in this release.
#60 — Fix floating bar runtime preference transport
Merged by contribution from @igorcv88.
The 0sp icon-only implementation itself was working in shared geometry, but floating_bottom_bar_text_size never reached the hooked WhatsApp process. HookProvider.get_all_preferences only exposes schema entries assigned to Store.PUBLIC, while four numeric Floating Bottom Bar controls were incorrectly classified as module-private:
floating_bottom_bar_text_sizefloating_bottom_bar_icon_sizefloating_bottom_bar_icon_label_spacingfloating_bottom_bar_minimal_fab_margin
The manager UI stores these values, but WhatsApp therefore falls back to the schema defaults. For text size that means the runtime reads 12sp even when the UI shows 0sp, so labels remain visible.
This PR moves all four hook-consumed controls to PUBLIC_SETTING / Store.PUBLIC and adds a regression test requiring every numeric BottomBarPreferenceSchema key to be hook-readable.
No FloatingBottomBar layout/hook code is changed; the existing textSize = 0 -> labelVisible = false -> View.GONE path can now receive the actual setting.