Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
This I will align similar to how the others look in the AppController. The SLOT/SIGNAL keywords are aligned.

This I will align similar to how the others look in the AppController. The SLOT/SIGNAL keywords are aligned.

this is incorrect connection usage. it should be moved to the applicationController class. The rule of API design: *the API is just emitting the signal *and is not responsible for the usage. *an...

this is incorrect connection usage.
it should be moved to the applicationController class.

The rule of API design:

  • the API is just emitting the signal
  • and is not responsible for the usage.
  • any object which needs to use it will connect and use (connects the signal to its own slot and runs the logic in its own thread)


Please move to ApplicationController class.

please check, lists are not empty. can be checked by private member variable: isConfigOk = isConfigOk && ! _<Property Name>.isEmpty();

please check, lists are not empty.
can be checked by private member variable:

isConfigOk = isConfigOk && ! _<Property Name>.isEmpty();
add an empty line before and after

add an empty line before and after

please align SIGNAL(did SLOT( on

please align
SIGNAL(did
SLOT( on

please do not use else. make it like the others on top. Look at lines 79 - 83. And insert it in between lines 89,90 with two empty line on top and bottom of the if block if ( ! codition ) { err ...

please do not use else.
make it like the others on top.
Look at lines 79 - 83.
And insert it in between lines 89,90
with two empty line on top and bottom of the if block

if ( ! codition ) {
  err = ;
  LOG_ ;
  return err;
}


thanks

UI-DEN-15833_UI VD S101 - UI - Post Settings Check - [ READY ]
UI-DEN-15833_UI VD S101 - UI - Post Settings Check - [ READY ]
[~msuleiman], thanks for the comment. this is fine to be consistent with the rest of the models, which are organized this way.

[~msuleiman],
thanks for the comment.
this is fine to be consistent with the rest of the models, which are organized this way.

use braces for if statement

use braces for if statement

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

removed

removed

thank for catching that, it has been fixed.

thank for catching that,
it has been fixed.

this will automatically get corrected when the file name is changed in the file explorer of the QtCreator.

this will automatically get corrected when the file name is changed in the file explorer of the QtCreator.

the file and the actual Class name does not necessary should be the same. to make sure these are not dependent, I use alias in the qrc. so although the name was not correct this still works.

the file and the actual Class name does not necessary should be the same.
to make sure these are not dependent, I use alias in the qrc.
so although the name was not correct this still works.

Correct, that is for clarification since in each of the child(ish) classes in stack back and confirm have different meaning.

Correct, that is for clarification since in each of the child(ish) classes in stack back and confirm have different meaning.

If the file is indeed incorrectly named, please also correct here

If the file is indeed incorrectly named, please also correct here