Bug 9898 – Thinking widget animation speed

Bug 9898 - Thinking widget animation speed

Summary:

Thinking widget animation speed

Status:	CLOSED FIXED

Product:	SB Controller
Classification:	Unclassified
Component:	UI
Version:	unspecified
Platform:	PC Windows XP

Importance:	-- enhancement (vote)
Target Milestone:	7.3
Assigned To:	Richard Titmuss

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-11-03 17:47 UTC by ndijulio
Modified:	2009-09-08 09:16 UTC (History)
CC List:	3 users (show)

See Also:
Category:	---

Attachments
Widget example (46.43 KB, image/png) 2008-11-03 17:47 UTC, ndijulio	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description ndijulio 2008-11-03 17:47:12 UTC

Created attachment 4199 [details]
Widget example

The speed of the thinking/searching widget is currently set to around 1 revolution per sec.  If we increase the speed or one revolution to x2 or x3 the device appears to be searching faster with little or no increase in software development:)  

The main point is that our current widget appears to search slowly and thus implies the devices is 'slow.'

Comment 1 Richard Titmuss 2008-11-04 01:35:13 UTC

Fixed in r3267, we now think faster.

Comment 2 ndijulio 2008-11-04 09:16:09 UTC

Cool...what did you up to the speed to?  x1.5, or x2?  It will be interesting to see if any comments:)

Comment 3 Richard Titmuss 2008-11-04 09:26:35 UTC

I think it was x2. The only problem i've noticed is sometimes the animation is not smooth, when it actually is thinking. That's probably why we used the slower speed before. Please try it out (once the update is available) and let me know what you think.

Comment 4 James Richardson 2008-12-15 12:09:12 UTC

This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.