Jcee wrote:
well its value is arguable... because the fact that the menu opens is indication enough that you pressed/touched the button
it is nice to have aesthetically though
that's true. but this all makes me wonder if the whole way that
animated buttons are currently implemented makes sense. it seems like you should just define a set of frames to be
animated and define a speed (that is limited for safety). then no matter what happens the animation plays. it would be easier for people creating the button and would seem to fill the needs of all. you would probably want to limit the number of frames as well as the total play time. but allow people to slow down or speed up the animation so that it visually looks good. right now having 255 frames seems a bit much. 13 seems more reasonable. i doubt anyone wants to see an animation more than 30 seconds long either. it might not be a bad idea to have the animation time be something you can set in classic shell settings. that way all one needs to do to create an
animated button is line up 13 frames. the first and last frame being the same. so no line of pixels would even need to be defined at all. you'd probably get more people creating buttons if it were that easy.
update; even better idea. limit to 12 frames and just have the program replay the first frame at the end of the animation, so that it ends where it started.