Skip to content

GUI: Fix restricted asset clear slots - #1315

Open
Tabakkui wants to merge 1 commit into
RavenProject:developfrom
Tabakkui:fix/issue-968-restricted-clear-slots
Open

Tabakkui wants to merge 1 commit into
RavenProject:developfrom
Tabakkui:fix/issue-968-restricted-clear-slots

Conversation

@Tabakkui

Copy link
Copy Markdown

Problem

Issue #968 reports Qt connection warnings when opening Restricted Assets:

  • No such slot AssignQualifier::clear()
  • No such slot FreezeAddress::clear()

Both widgets connect their buttonClear signals using the string-based Qt SLOT(clear()) syntax, but clear() was declared as a regular public method rather than a meta-object slot.

Change

Declare AssignQualifier::clear() and FreezeAddress::clear() in public Q_SLOTS. The existing connections and clear implementations remain unchanged.

Test plan

  • git diff --check
  • Verified both headers place void clear(); directly under public Q_SLOTS:.
  • Confirmed the existing buttonClear connections use SLOT(clear()).

The checkout is unconfigured and Qt's moc executable is not installed on this ARM64 host, so no generated-meta-object or full Qt build was run. The authorized PC should run the Qt build/test gate.

Fixes #968

Declare the restricted-asset clear handlers as Qt slots so the existing button connections resolve through the meta-object system.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant