Skip to content

Conversation

@WhalesState
Copy link

@WhalesState WhalesState commented Nov 2, 2025

Following Godot’s modular design approach, this PR cleans up the codebase by disabling sections of unused code that were still active, improving maintainability and reducing unnecessary compilation.

Note: This change also removes some methods from the documentation by default. If there are plans to re-enable this feature in the future, we can add dummy methods to preserve the related documentation entries.

@WhalesState WhalesState marked this pull request as draft November 2, 2025 05:27
@WhalesState WhalesState force-pushed the accesskit-blazium branch 2 times, most recently from 7e9b53b to d164bfa Compare November 2, 2025 05:38
@WhalesState WhalesState marked this pull request as ready for review November 2, 2025 05:39
@WhalesState WhalesState changed the title More disable for accesskit and fix Node's accesskit related methods. [4.5] More disable for accesskit and fix Node's accesskit related methods. Nov 2, 2025
}
}

RID RichTextLabel::get_focused_accessibility_element() const {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

get_focused_accessibility_element() doesn't look like it needs to be moved for this if I am not mistaken.

String accessibility_description;
#endif // ACCESSKIT_ENABLED

void _accessibility_notify_enter(Node *p_node);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were these intended to be in the ACCESSKIT_ENABLED block? If not, they should probably not be moved.

#endif // ACCESSKIT_ENABLED
}

String Window::get_accessibility_name() const {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The binding for this looks to be wrapped in an ACCESSKIT_ENABLED check, is something else using it that the function needs to remain with a return String(); placeholder?

}
}

bool Node::_is_accessibility_enabled() const {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These functions should remain in the original places so upstream changes are less likely to conflict in future merges if possible.

#endif // ACCESSKIT_ENABLED
}

String Control::get_accessibility_name() const {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The binding for this looks to be wrapped in an ACCESSKIT_ENABLED check, is something else using it that the function needs to remain with a return String(); placeholder?

return ret;
}

void Control::set_accessibility_name(const String &p_name) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can these functions be kept in the original positions so upstream changes are less likely to have merge conflicts if possible?

String get_accessibility_name() const;

#ifdef ACCESSKIT_ENABLED
void set_accessibility_live(DisplayServer::AccessibilityLiveMode p_mode);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the addition of set_accessibility_live fixing something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants