components

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

RESOLVED.

RESOLVED.

RESOLVED.

I don't usually remove these kinds of comments they are there for developers as a reminder to keep the indices match. This is like a code comment.

I don't usually remove these kinds of comments they are there for developers as a reminder to keep the indices match.
This is like a code comment.

So then when would we remove this line of code?

So then when would we remove this line of code?

RESOLVED.

RESOLVED.

Disabled the "coco end"s as well.

Disabled the "coco end"s as well.

To make sure it is intentional, and we didn't miss a parameter. also it helps with the copy pasts later.

To make sure it is intentional, and we didn't miss a parameter.
also it helps with the copy pasts later.

IT has been recently removed from the diagnostics screen. I'm not sure when it will be needed to get back again on that screen. Probably keeping it is a lot easier than reimplementing it.

IT has been recently removed from the diagnostics screen.
I'm not sure when it will be needed to get back again on that screen.
Probably keeping it is a lot easier than reimplementing it.

When will this get fixed (removed)?

When will this get fixed (removed)?

Why only comment out? Can't we just remove?

Why only comment out? Can't we just remove?

very good point Sean. Coco ignores it but logs each one which I think it more bothers us than coco. I am going to disable them too.

very good point Sean.
Coco ignores it but logs each one which I think it more bothers us than coco.
I am going to disable them too.

Does it bother CoCo if you disable a begin but leave the end there?

Does it bother CoCo if you disable a begin but leave the end there?

UI-DEN-12258_UI BN S66
UI-DEN-12258_UI BN S66
RESOLVED.

RESOLVED.

Actually, this is correct. And it should not have parenthesis like you said, otherwise it becomes incorrect. if I write it like : ( ( x * ( maximum - minimum ) ) / width ) + minimum then too man...

Actually, this is correct.
And it should not have parenthesis like you said, otherwise it becomes incorrect.
if I write it like :

 ( ( x * ( maximum - minimum ) ) / width ) + minimum 

then too many /redundant parentheses make it confusing.

To make sure the addition is done first, should you put ( width + minimum ) ?

To make sure the addition is done first, should you put ( width + minimum ) ?

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

Thanks, Updated.

Thanks,
Updated.

Thanks, Aligned.

Thanks,
Aligned.

This is part of an ongoing investigation on how to fix the slider touch margin issue. I am still working on it. It worked somehow for the slider with lower resolution but for sliders, with a high r...

This is part of an ongoing investigation on how to fix the slider touch margin issue.
I am still working on it.
It worked somehow for the slider with lower resolution but for sliders, with a high resolution, it causes a handler jump which makes it less user-friendly.
Added clarifying comment.

This is the Trends screen. It is needed since it has not been implemented yet has been commented out.

This is the Trends screen.
It is needed since it has not been implemented yet has been commented out.

If not needed, why not just delete this line?

If not needed, why not just delete this line?