MenuEdit: Do not use autoconnection mechanism for slots used in QMenu #132
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently whenever UI gets loaded and we try to connect a slot with a signal emitted in QAction, for example in appending frame, inserting it, etc. we get warnings like these: qt.core.qmetaobject.connectslotsbyname: QMetaObject::connectSlotsByName: No matching signal for on_actionAdd_Frame_triggered() This is because MOC tries to automatically connect functions which have "on_objectname_triggered" signature, and it can't find a matching signal for it by default. So the solution for that is to simply not use the autoconnection mechanism by changing names of those slots, removing "on" prefix from them.
QMenu Currently whenever UI gets loaded and we try to connect a slot with a signal emitted in QAction, for example in appending frame, inserting it, etc. we get warnings like these: qt.core.qmetaobject.connectslotsbyname: QMetaObject::connectSlotsByName: No matching signal for on_actionAdd_Frame_triggered() This is because MOC tries to automatically connect functions which have "on_objectname_triggered" signature, and it can't find a matching signal for it by default. So the solution for that is to simply not use the autoconnection mechanism by changing names of those slots, removing "on" prefix from them.
tetektoza
changed the title
AJenbo
approved these changes
Nov 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently whenever UI gets loaded and we try to connect a slot with a signal emitted in QAction, for example in appending frame, inserting it, etc. we get warnings like these:
qt.core.qmetaobject.connectslotsbyname: QMetaObject::connectSlotsByName: No matching signal for on_actionAdd_Frame_triggered()This is because MOC tries to automatically connect functions which have "on_objectname_triggered" signature, and it can't find a matching signal for it by default. So the solution for that is to simply not use the autoconnection mechanism by changing names of those slots, removing "on" prefix from them - this way we won't get those warnings whenever we load certain parts of GUI.