Comment 1 for bug 1227418

Thanks for your bug report. As you correctly pointed out, the hardcoding of values is affecting the functionality of the clock app. This is something I need to address asap but haven't got to doing yet. There are several things which are being hardcoded such as,

1. The height of the animation counter. -> I tried using page.height to make it dynamic, but then it displays an error message regarding binding loops.

2. Height of the stopwatch, clock, timer and upcoming alarm list.

Instead of hardcoding they should dynamically adjust based on the phone dimensions.

To answer your question about the page scrolling animation, basically every page has two states: the first being the state where the clock is fully visible. In this state the listview is hidden. The second state is the state where the clock face is partially visible while the list view is shown prominently. We do not allow any intermediate view points for the flickable. The animations are there to provide a smooth transistion between these states.

A fix for this would be highly appreciated :)