Absolutely, I'm doing it incrementally and slowly to not to make the code reviews harder and confusing git. I did for so many and this file will get its turn soon.
You are using this step change #define for step size (as name implies) but also for a maximum delta from your target position. Though they share the same value at this time (1000), they are two different things.
Thanks, I couldn't find a requirement for hiding the scrollbars and also don't see any reason why we need to do that. It's always good to see the scrollbars if the components are not fit in the view port of the container, so the user immediately will catch that there are more to take care of.
Please always put the id: <name of the object> in front of the <Type> { to be able to find object easily. I saw this in other codes but since it was the first line after { I didn't put any comment. So please follow this rule every where.
Please put a short description of your component and explain what it does and where it can be used. Since it is a specific or compound component and is not a general component like a just a Slider or Progressbar, it helps to understand the use case of the component.
Please put "done" when the code is pushed. When an email is sent to the reviewer it is assumed that there is something to review but putting a "done" and "will be updated" is not something that can be reviewed.
It is all documentations and Doxygenization. If you see otherwise is because the file names changed and the code review takes it as a new file and marks all the file content as to be reviewed. Let me know if otherwise.
