sources

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[ On Hold - P1B ] UI-DEN-16181_UI VD S103 Filemodel
[ On Hold - P1B ] UI-DEN-16181_UI VD S103 Filemodel
Done

Done

After our conversation, I have changed as requested.

After our conversation, I have changed as requested.

Changed as requested

Changed as requested

Changed as requested

Changed as requested

I have removed the added and using the Settings_Path()

I have removed the added and using the Settings_Path()

I resolved my own message because of the conversation we had in terms of why I am making the change suggested.

I resolved my own message because of the conversation we had in terms of why I am making the change suggested.

I don't believe we need did * spaceChange. I am not interested in when the space changes. I am only interested when that partition gets too low on available space. Unless there is a case that you h...

I don't believe we need did * spaceChange. I am not interested in when the space changes.
I am only interested when that partition gets too low on available space. Unless there is a
case that you have which indicates otherwise.
This signal is similar to didSDCardSpaceTooLow, line 231

For SD card case, when the SD card is not ready, we update the visuals to set the "available" and "used" to 0 and emit the update. For this case, we are not updating any visuals. The need we have f...

For SD card case, when the SD card is not ready, we update the visuals to set the
"available" and "used" to 0 and emit the update. For this case, we are not updating
any visuals. The need we have for this function is to determine whether we are
low on available partition space and if we are, emit the "low" signal to handle

as has been mentioned follow the other two (USB, Sd-Card) methods naming and signature.

as has been mentioned follow the other two (USB, Sd-Card) methods naming and signature.

please follow the same naming and arguments for the did<device>SpaceChange(bool vReady, ....) did<device>StateChange( ... ) don't think we need toolow fir this one.

please follow the same naming and arguments for the
did<device>SpaceChange(bool vReady, ....)
did<device>StateChange( ... )

don't think we need toolow fir this one.

we already have the same variable define as Settings_Path_Name. Please use that

we already have the same variable define as Settings_Path_Name.
Please use that

Why it is different than the same function for the SD-card? It is a mounted drive.

Why it is different than the same function for the SD-card?
It is a mounted drive.

please add //DEBUG

please add //DEBUG

UI-DEN-15833_UI VD S101 - UI - Post Settings Check - [ READY ]
UI-DEN-15833_UI VD S101 - UI - Post Settings Check - [ READY ]
UI Staging Unreviewed Commits
UI Staging Unreviewed Commits
UI-DEN-16123_UI BN S103 Postreq
UI-DEN-16123_UI BN S103 Postreq