Additional FADE options for images

[Livin]

I'd like to have an image "build" starting at a corner, bottom, top, etc.

I think this could be accomplished if we had more fade options. If we were able to tell the fade at what coordinate to start and which to end that might work?

JM... do you think you could add this?

[jmarshall]

This is not actually doable using the current engine (as it only uses a single variable for the "fade" coordinate).

Even if it was, it requires careful thought about how it is implemented anyway - I presume some sort of a "fade direction" needs to be specified, but how would it work anyway? Surely you need to specify not only the direction of the fade, but also the magnitude of the fade (ie difference in fade amount as you progress in the direction specified).

I also think you'd need a fixed origin of the fade as well (ie a specific place where we can specify that the fade should be the full fade amount).

Thus:

Fade amount (start/end)
Fade direction (vector)
Fade magnitude (possibly determinable by the vector?)
Fade origin (fixed at left corner of screen or something?)

If we simplify things and have a set few fade directions (eg left/right etc.) then I guess we just need to specify a way to indicate the difference in fade amount from the left of the screen to the right of the screen.

Suggestions?

Cheers,
Jonathan

[Livin]

JM,
I think you understand exactly what I'm hoping for.

Variable ideas...

Start - visibility start % (already exists today)

End - visibility end % (already exists today)

Origin - starting point or boundary
a) coordinate -- if the image is 600x350 and you want to start in the bottom right corner, you'd set at 600,0
b) boundary -- left, right, top, bottom

Vector - direction to fade
a) Center -- center out in all directions
b) Angle

Time - speed of fade (already exists today)

Reversible - reverses upon state change (already exists today)

Pulse - loops the fade (already exists today)

Acceleration - speed up or slow down the fade (already exists today)

[jmarshall]

It's still missing the gradient of the fade over distance (eg 10 pixel units away from the origin, how much should the fade be compared with the origin?)

Furthermore, we can only specify the alpha values for an image at the corners, so fading from the center is not possible anyway.

As you can see, it gets quite complicated pretty quickly, particularly if the skinner is interested in trying to sync the fades between controls in different locations.

We thus need at least an origin and gradient of the fade. Also, should the time for the fade be taken as the time for the origin to fully fade, or the time for the whole anim (more complicated to calculate, but perhaps more useful to the skinner?) Or, should we simply assume that after 50% of the time the origin is fully faded, and then the opposite side starts fading?

IMO it would be easier to simply define some "fadewipe" effects (eg from left, from right or whatever) so that the skinner doesn't have to worry about any of the speed/timing/origin/gradient issues, and can just see the results.

And lastly: Would any of the skinners who make and distribute skins care to comment?

Cheers,
Jonathan

[Livin]

I see what you mean. I'd say to make things simple have the Time be the total fade effect and have the gradient user definable... thus dividing the Time/Gradient to get your fade effect result.

I'm interested in hearing other skinner's opinions too. For me, I'm going to use it to modify PM3 so there is a 'full screen' version with a hidden menu and still keep the skin's original design integrity... I hope ;)

Thanks for the interest.

[Livin]

JM,
You still considering this?

[jmarshall]

Not unless some skinners that make and distribute skins think it's a worthwhile addition.

My time is limited nowadays, so I have to prioritise what I spend time doing.