home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Improving GUI Animations, staggering the delay timers
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mbuzina" data-source="post: 1109888" data-attributes="member: 12382"><p>I am thinking about contributing a little to the gui animation capabilities of MP. I like the way Windows 8 creates staggered animations, just slightly delaying each animation a little more than others. So I want to change the animation delay (and maybe the duration value as well) to allow an additional component to be added to each control to automate this type of animation.</p><p></p><p>And I would like some feedback on how @skinners might use such a functionality.</p><p></p><p>I have 2 basic versions in my head, which would be better for skinning?</p><p>a) change the value of the delay parameter to delay="100+10a", this would add 10 ms per control in the order the controls are listed to the delay (or duration) value. Several groups could be started by using different letters/tokens. Sample:</p><p><animation effect="slide" start="-50,0" delay="100+10a">WindowOpen</animation> //starts @ 110</p><p><animation effect="slide" start="-50,0" delay="100+10a">WindowOpen</animation> //starts @ 120</p><p><animation effect="slide" start="-50,0" delay="100+10a">WindowOpen</animation> //starts @ 130</p><p></p><p>b) use a calculation based on x&y position, sample delay="100+100x-80y", this would add 100 ms for the highest x and subtract 80 ms for the highest y values to the delay, so for a 1080p skin the following would hold</p><p>x=1000, y=100 --> delay = 100+100*1000/1920-80*100/1080 = 145 ms</p><p>x=1000, y=130 --> delay = 100+100*1000/1920-80*130/1080 = 142 ms</p><p>x=500, y=100 --> delay = 100+100*500/1920-80*100/1080 = 119 ms</p><p>etc.</p><p></p><p>Advantage of a is that it is probably easier to understand, advantage of b is that you can make great visual patterns and ignore hidden controls when calculating the delay.</p><p></p><p>Right now I am thinking of implementing b) but I would like to hear some opinions on this.</p></blockquote><p></p>
[QUOTE="mbuzina, post: 1109888, member: 12382"] I am thinking about contributing a little to the gui animation capabilities of MP. I like the way Windows 8 creates staggered animations, just slightly delaying each animation a little more than others. So I want to change the animation delay (and maybe the duration value as well) to allow an additional component to be added to each control to automate this type of animation. And I would like some feedback on how @skinners might use such a functionality. I have 2 basic versions in my head, which would be better for skinning? a) change the value of the delay parameter to delay="100+10a", this would add 10 ms per control in the order the controls are listed to the delay (or duration) value. Several groups could be started by using different letters/tokens. Sample: <animation effect="slide" start="-50,0" delay="100+10a">WindowOpen</animation> //starts @ 110 <animation effect="slide" start="-50,0" delay="100+10a">WindowOpen</animation> //starts @ 120 <animation effect="slide" start="-50,0" delay="100+10a">WindowOpen</animation> //starts @ 130 b) use a calculation based on x&y position, sample delay="100+100x-80y", this would add 100 ms for the highest x and subtract 80 ms for the highest y values to the delay, so for a 1080p skin the following would hold x=1000, y=100 --> delay = 100+100*1000/1920-80*100/1080 = 145 ms x=1000, y=130 --> delay = 100+100*1000/1920-80*130/1080 = 142 ms x=500, y=100 --> delay = 100+100*500/1920-80*100/1080 = 119 ms etc. Advantage of a is that it is probably easier to understand, advantage of b is that you can make great visual patterns and ignore hidden controls when calculating the delay. Right now I am thinking of implementing b) but I would like to hear some opinions on this. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Improving GUI Animations, staggering the delay timers
Contact us
RSS
Top
Bottom