If you are doing this in the constructor, then the combo box is created but not yet visible. In the slot, you can check isVisible() and only call fillTable() if it returns true.I am not sure how to get around that
Guru
Re: Function running on its own
If you are doing this in the constructor, then the combo box is created but not yet visible. In the slot, you can check isVisible() and only call fillTable() if it returns true.I am not sure how to get around that
<=== The Great Pumpkin says ===>
Please use CODE tags when posting source code so it is more readable. Click "Go Advanced" and then the "#" icon to insert the tags. Paste your code between them.
Novice
Re: Function running on its own
I did not realize that. That is certainly much cleaner than what I was planning. Thanks again!If you are doing this in the constructor, then the combo box is created but not yet visible.
Guru
Re: Function running on its own
Alternatively, you could bracket the for() loop in your constructor with calls to blockSignals( true ) and blockSignals( false ) through the combo box pointer.
<=== The Great Pumpkin says ===>
Please use CODE tags when posting source code so it is more readable. Click "Go Advanced" and then the "#" icon to insert the tags. Paste your code between them.
Novice
Re: Function running on its own
That might be another option, but I think it might be better suited for a different situation. Now that I know the combo box is not visible, at that point, I think the first way is more readable.
Now if I can just get my queries to work right...
Posting Permissions
Reply With Quote
Bookmarks