D26524: configmodule: Make sure the kcm information is loaded when the qml is created

2020-05-22 Thread Aleix Pol Gonzalez
apol added a comment. hmmm. Ping @mart. :) what do you suggest we do? REPOSITORY R296 KDeclarative REVISION DETAIL https://phabricator.kde.org/D26524 To: apol, #plasma, #frameworks Cc: mart, davidedmundson, kde-frameworks-devel, LeGast00n, cblack, michaelh, ngraham, bruns

D26524: configmodule: Make sure the kcm information is loaded when the qml is created

2020-01-09 Thread Marco Martin
mart added a comment. that depends how heavy the load() implementation is... both ways are not optimal.. this behavior comes from KCModule, where the module nevel loads itself and a load() must be called from outside. here may be worth doing that even if it's two loads as would

D26524: configmodule: Make sure the kcm information is loaded when the qml is created

2020-01-09 Thread David Edmundson
davidedmundson added a comment. I kinda see what you're saying, I don't understand why we currently do anything on showEvent() But now we're going to call load() twice, which doesn't sound very optimal. REPOSITORY R296 KDeclarative REVISION DETAIL https://phabricator.kde.org/D26524

D26524: configmodule: Make sure the kcm information is loaded when the qml is created

2020-01-08 Thread Aleix Pol Gonzalez
apol created this revision. apol added reviewers: Plasma, Frameworks. Herald added a project: Frameworks. Herald added a subscriber: kde-frameworks-devel. apol requested review of this revision. REVISION SUMMARY Otherwise we'll initialize with dumb values and refresh it when shown, which