23 + // because of dynamic assignment of states, we need to assign state after completion. 24 + Component.onCompleted: state = "initial"
Is this really true? Why would « state: "initial" » not work?
=====
43 - property alias searchEnabled: search.enabled 44 + property bool searchVisible: true
Why this rename?
94 - function show() { 95 - search.state = "visible" 96 + function show_state() { 97 + return "visible" 98 } 99 100 - function hideUp() { 101 - search.state = "hiddenUp" 102 + function hideUp_state() { 103 + return "hiddenUp" 104 }
169 - searchIndicator.hideUp() 170 + searchIndicator.state = searchIndicator.hideUp_state()
177 - searchIndicator.show() 178 + searchIndicator.state = searchIndicator.show_state()
This is weird, why the _state() methods at all? Either direct names or readonly props would suffice, no?
116 + available: true
This is the default.
« Back to merge proposal
23 + // because of dynamic assignment of states, we need to assign state after completion. onCompleted: state = "initial"
24 + Component.
Is this really true? Why would « state: "initial" » not work?
=====
43 - property alias searchEnabled: search.enabled
44 + property bool searchVisible: true
Why this rename?
=====
94 - function show() {
95 - search.state = "visible"
96 + function show_state() {
97 + return "visible"
98 }
99
100 - function hideUp() {
101 - search.state = "hiddenUp"
102 + function hideUp_state() {
103 + return "hiddenUp"
104 }
169 - searchIndicator .hideUp( ) .state = searchIndicator .hideUp_ state()
170 + searchIndicator
177 - searchIndicator .show() .state = searchIndicator .show_state( )
178 + searchIndicator
This is weird, why the _state() methods at all? Either direct names or readonly props would suffice, no?
=====
116 + available: true
This is the default.