Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

The reason is separation and keeping the logic of the Slider and its ON/OFF switch clear and non-confusing, and independent. Like right now that I had a wrong fix and I easily just changed the conn...

The reason is separation and keeping the logic of the Slider and its ON/OFF switch clear and non-confusing, and independent.
Like right now that I had a wrong fix and I easily just changed the connection related to the fix I had not changed the Slider implementation itself.

I disagree. If we bind the value here to the "active" property, the value it takes is whatever "active" has when the component gets created.

I disagree. If we bind the value here to the "active" property, the value it takes is whatever "active" has when the component gets created.

Unfortunately, we can't and it created a binding loop. I tried it.

Unfortunately, we can't and it created a binding loop.
I tried it.

This is the default value of the heparinStopTime. If you bind to the active of the dispensing switch nothing will happen, since the switch by default is active=false and if active is not changed, n...

This is the default value of the heparinStopTime.
If you bind to the active of the dispensing switch nothing will happen, since the switch by default is active=false and if active is not changed, no signal, therefore no property change will happen, and the enable remains unchanged, as true.

Binding here for instance, enabled: _heparinDispensingRateSwitch.active

Binding here for instance, enabled: _heparinDispensingRateSwitch.active

I believe we can bind the active state of _heparinDispensingRateSwitch and _heparinStopTime together.

I believe we can bind the active state of _heparinDispensingRateSwitch and _heparinStopTime together.

Is there a specific reason to why we are opting to use a connection here instead of handling the signal in the component body? (ie: line 181 further down?)

Is there a specific reason to why we are opting to use a connection here instead of handling the signal in the component body? (ie: line 181 further down?)

UI-DEN-14866_UI BN S92
UI-DEN-14866_UI BN S92
UI-DEN-14796_UI BN S91_2
UI-DEN-14796_UI BN S91_2
UI-DEN-14838_UI VD S91 [ Sliders ]
UI-DEN-14838_UI VD S91 [ Sliders ]
Yes, assignments break bindings. RESOLVED

Yes, assignments break bindings.

RESOLVED

Ok, sounds good. RESOLVED

Ok, sounds good.

RESOLVED

Good point, But you can't. The readonly properties are only working with bindings, not assignments. I am using that as a public variable.

Good point,
But you can't.
The readonly properties are only working with bindings, not assignments.
I am using that as a public variable.

Good point, I agree with the two intervals, it would be clarifying. For the counter, though, it might not be always the case. I will start doing it in my next task, since I would like to change all...

Good point,
I agree with the two intervals, it would be clarifying.
For the counter, though, it might not be always the case.
I will start doing it in my next task, since I would like to change all, to be consistent across the entire code base.

If _root.isOpen is not modified outside of this powerItem.qml, You can make it a readonly property and bind it to the powerDialog's property.

If _root.isOpen is not modified outside of this powerItem.qml, You can make it a readonly property and bind it to the powerDialog's property.

Only a suggestion: It is a good idea to append the unit to the end of the variable name especially for time. It helps improve readability and clarity. For instance, here, we have ms and the next o...

Only a suggestion:
It is a good idea to append the unit to the end of the variable name especially for time. It helps improve readability and clarity.

For instance, here, we have ms and the next one, _pendingInterval is in seconds. and I believe _pendingCounter is in minutes based on the .cpp file's comment.

_interval_ms
_pendingInterval_sec
_pendingCounter_min

RESOLVED

RESOLVED

Thanks for the feedback. Fixed.

Thanks for the feedback.
Fixed.