Skip to content

Conversation

@wutschel
Copy link
Collaborator

Description

This rework was triggered by the recent observations that reloadData is called too often. In the custom button view signaling "No custom button defined" was done by adding a dummy button and calling reloadData to show it. This PR replaces this approach by introducing a UILabel which is faded in/out as needed. This allows to remove the dummy button logic and the related calls of reloadData. While working on this, I also recognized that UIButton control state were not correctly used and did rework this, as well as removing some superfluous keys.

Summary for release notes

Improvement: Correctly use UIButton control states in custom button view
Improvement: Avoid calling reloadData by using UILabel to signal "No custom button defined"

Introduce a label which shows the information that no custom button has been defined yet. This label is faded in/out depending on the button list content. This allows to avoid calling reloadData and using a fake button with the same information.
Correctly use UIControlStateNormal and UIControlStateSelected for editTableButton.
These keys were either not used at all ("helpText", "xbmxSettings, "revealViewTop") or are not needed anymore as all buttons are editable ("isSettings") nowadays.
@wutschel wutschel force-pushed the rework_custombuttons branch from 2c623b3 to cb0372e Compare January 24, 2026 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant