UI-DEN-1090

RESOLVED.

RESOLVED.

I aligned the m(s) so I'm sure that I'm using the correct variables since I have variables with the same name with v at the beginning most of the time. *Also it's really easy to copy/paste variab...
  • I aligned the m(s) so I'm sure that I'm using the correct variables since I have variables with the same name with v at the beginning most of the time.
  • Also it's really easy to copy/paste variables vertically.
  • Also it shows me at first look that I used ".value" otherwise it won't work.
What I meant is vData += mPWMDtCycle.value; instead of vData += mPWMDtCycle .value; such that the .value is always stuck to the member variable. This looks really odd as it stands.

What I meant is vData += mPWMDtCycle.value; instead of vData += mPWMDtCycle .value;

such that the .value is always stuck to the member variable. This looks really odd as it stands.

RESOLVED.

RESOLVED.

that is one operator not two. This has a meaning and cannot be separated ! If you separate them you get compile error ...

that is one operator not two.
This has a meaning and cannot be separated !
If you separate them you get compile error ...

I agree that it's a little bit redundant but after facing an error I found a subject and this approach was recommended and it worked for me. This happens since I need to convert array of bytes to f...

I agree that it's a little bit redundant but after facing an error I found a subject and this approach was recommended and it worked for me.
This happens since I need to convert array of bytes to float value and then to variant which GUI understands and during this conversion some values get more that expected values after decimal point.

Isn't there a library or a method that already does this?

Isn't there a library or a method that already does this?

I would recommend putting the extra spaces after the += sign rather than between the variable and its property.

I would recommend putting the extra spaces after the += sign rather than between the variable and its property.

RESOLVED

RESOLVED

RESOLVED

RESOLVED

Some Constants are one time use and doesn't add any value to the code to collect them in one place. And also since it is the unit test class the constants have been tweaked and modified to get erro...

Some Constants are one time use and doesn't add any value to the code to collect them in one place.
And also since it is the unit test class the constants have been tweaked and modified to get errors to test the code.
So even if it's look like the other one it has some slight changes.

Fixed.

Fixed.

Same here, These are aligned parameters as I mentioned to better identify the code bugs.

Same here, These are aligned parameters as I mentioned to better identify the code bugs.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

Same here, These are aligned parameters as I mentioned to better identify the code bugs.

Same here, These are aligned parameters as I mentioned to better identify the code bugs.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

This code is for test to be able to enable or disable CanInterface , MessageDispatcher console out to be able to debug without rebuild even on target. And I mentioned at top of the code that it's a...

This code is for test to be able to enable or disable CanInterface , MessageDispatcher console out to be able to debug without rebuild even on target.
And I mentioned at top of the code that it's a Test code for debuging