GuiObject:TweenRotation

[GuestCapone]

I would like to propose for a simple tween request for the Gui objects. Since we have, TweenPosition and TweenSize and TweenPositionAndSize, why don’t we have :TweenRotation(CurrentRotation, GoalRotation, TweenTime, Callback)?

Just a simple request.

[EchoReaper]

First they’d need to make it so GUIs aren’t pixel perfect. Because of that, all rotated GUIs are aliased nightmare fuel. Even if you tweened it it’d still look stupid.

[Sharksie]

Tween methods shouldn’t exist. Having a unique method to tween every property is not the direction roblox should be moving in. What we need is a generic tween function that can be used to tween any tweenable property of any object.

[Locard]

Personally, I wouldn’t find creating a new method to be the most useful way of granting this request. Personally, I would modify the current tweening functions and add an extra argument (since they already tween the position, it’d be better to tween the rotation within the same sequence than calling 2 functions).
Although, I do agree that something like this could be implemented, there are still bugs involving surfaces rotating outside of its parent when the parent’s ClipDescendants property is active. Example:

Before rotation:

After rotation:

[Tomarty]

Tween methods shouldn’t exist. Having a unique method to tween every property is not the direction roblox should be moving in. What we need is a generic tween function that can be used to tween any tweenable property of any object.

SOMEONE WHO UNDERSTANDS!!! :DDD
If we go down this road we’ll end up with :TweenTransparency :TweenBackgroundColor3 :TweenTextColor3 :TweenReflectance and all kinds of API bloat :X

[Dapale]

Tween methods shouldn’t exist. Having a unique method to tween every property is not the direction roblox should be moving in. What we need is a generic tween function that can be used to tween any tweenable property of any object.

SOMEONE WHO UNDERSTANDS!!! :DDD
If we go down this road we’ll end up with :TweenTransparency :TweenBackgroundColor3 :TweenTextColor3 :TweenReflectance etc. etc. etc. :X[/quote]

That would be neat, currently you can do that but it doesnt look as good

[AlgyLacey (Algy)]

Tween methods shouldn’t exist. Having a unique method to tween every property is not the direction roblox should be moving in. What we need is a generic tween function that can be used to tween any tweenable property of any object.

SOMEONE WHO UNDERSTANDS!!! :DDD
If we go down this road we’ll end up with :TweenTransparency :TweenBackgroundColor3 :TweenTextColor3 :TweenReflectance and all kinds of API bloat :X[/quote]

Yep, I agree with that!
I find a loop quite adequate.

[woot3 (Woot)]

I wrote this module sometime ago in order to animate properties as I wanted. It works in the exact same way that the tween methods do, except you need to supply the object and the name of the property. It will work on both the server and the client, all animations on the client are done on renderstep.

Here is the usage

animate(Instance Object, String PropertyName, Tuple NewProperty, Enum EasingDirection, Enum EasingStyle, Float Time, Bool Overideable, Function Callback)

Here is an example of how to use it

animate = require(animation)

animate(game.Workspace.Part, "Transparency", 1, "Out", "Sine", 0.25, true, function ()
 print'Finished'
end)

It does not support certain property types. Specifically NumberSequence and Range.

[GuestCapone]

Necro bump buuuuuuut.

Looks like we might be getting this after all.

[EchoReaper]

Ew

[GuestCapone]

Yeah, I feel like my tween module is almost useless now.

[spotco]

@Osyris