One observation: with that change we emit countChanged inside beginResetModel() -- endResetModel(), however if the backend dee model is not synchronized yet, we emit countChanged in onSynchronizedChanged() and it's outside of beginResetModel() -- endResetModel() there. I'm not sure if this is can have any side effects (probably not), but just mentioning it; perhaps it makes sense to make it consistent?
41 - m_parent- >beginResetMode l(); get_n_rows( m_deeModel) ; >endResetModel( ); >countChanged( ); connect( m_deeModel, "notify: :synchronized" , G_CALLBACK( onSynchronizedC hanged) , m_parent); hronized = true; >endResetModel( );
42 m_count = dee_model_
43 - m_parent-
44 Q_EMIT m_parent-
45 }
46 else
47 @@ -156,6 +155,7 @@
48 g_signal_
49 m_listeningSync
50 }
51 + m_parent-
One observation: with that change we emit countChanged inside beginResetModel() -- endResetModel(), however if the backend dee model is not synchronized yet, we emit countChanged in onSynchronizedC hanged( ) and it's outside of beginResetModel() -- endResetModel() there. I'm not sure if this is can have any side effects (probably not), but just mentioning it; perhaps it makes sense to make it consistent?