UI/QT warnings

[dexX7]

Stumbled upon this in the debug.log:

GUI: Object::connect: No such signal QWidget::message(QString,QString,unsigned int) in qt/walletview.cpp:137
GUI: Object::connect: No such slot OverviewPage::updateAlerts(QString) in qt/overviewpage.cpp:364
GUI: Object::connect:  (receiver name: 'OverviewPage')

And when building after cleaning:

qt/forms/lookupspdialog.ui: Warning: Z-order assignment: '' is not a valid widget.
qt/forms/lookupspdialog.ui: Warning: Z-order assignment: '' is not a valid widget.

[zathras-crypto]

Stumbled upon this in the debug.log:

Ahh nice - good catch. OK so:

GUI: Object::connect: No such signal QWidget::message(QString,QString,unsigned int) in qt/walletview.cpp:137

This is due to my moving the original bitcoin send dialog into a tab - fixed by directing the signal to the new tab instead of the original page (05e0e81)

GUI: Object::connect: No such slot OverviewPage::updateAlerts(QString) in qt/overviewpage.cpp:364
GUI: Object::connect:  (receiver name: 'OverviewPage')

This is due to the fact updateAlerts() no longer takes a string parameter - I must have missed updating the slot - fixed in 9f47020

qt/forms/lookupspdialog.ui: Warning: Z-order assignment: '' is not a valid widget.

Looks like some extraneous zorder directives have gotten in here somehow - perhaps I did something weird when designing that form - fixed in a0f081c

Thanks again dude!!! :)

[dexX7]

A few of the following lines are printed to the debug file, after generating a block:

GUI: QTableWidget: cannot insert an item that is already owned by another QTableWidget

State: after running the regtests. It also appears, if all Omni transactions are confirmed.

It is not triggered by simple sends, and also not when creating new trades.

But it is triggered, when cancelling trades.

[zathras-crypto]

OK great, thanks for the heads up - I'll take a look once I get through with rewriting populateRPCTransactionObject()