feature/defaults_graphic_workaround_speed_and_bug_fixes

[nindim]

• Fixed issue in which the Animation Step's Delay was being applied to each Action individually, this was causing them to execute sequentially rather than simultaneously.
• Fixed an issue in which joined Steps after an Invoke Callback Step with a delay were incorrectly delayed.
• Added general defaults, previously defaults could only be set for Actions.
• Worked around a Unity bug in which updating the colour of a Graphic does not cause any visual change outside of PlayMode (affects "Color Graphic" and "Fade Graphic" actions).
• Improved Step naming for Invoke Callback to include the called function name and also support multiple callbacks.
• Added RectTransformSizeDOTweenAction to tween the sizeDelta of a Graphic.
• Fixed a bug in which exiting the prefab staging view with an active preview would cause a null ref and failure to reset the animation. This was due to the timing of EditorWIndow.OnDisable (it is is called after the prefab objects have already been destroyed) and has been fixed by hooking into PrefabStage.prefabSaving.
• Added runtime playback speed.

[brunomikoski]

One small question and some weird line ending! but overall pretty good improvements! Thanks a lot for the contribution again!

I also advise you to take a look at the warnings/errors on the codacy! https://github.com/brunomikoski/Animation-Sequencer/pull/36#pullrequestreview-835851828

Its not always mandatory but its good to keep an eye on it!

[nindim]

Hey @brunomikoski,

I had a look through the Codacy issues, please see below:

"Remove this initialization to 'XXX', the compiler will do that for you." I matched the style of the existing code when setting bools to false (it already existed for useRelative).

"Remove this unused method parameter 'gameObject'." The problem it's picking up with the PrefabSaving(GameObject gameObject), this can't be removed as it's a Unity provided Action.

"Duplicated block occurs 2 times in 1 files" With regards to the the duplication Codacy picking up between FadeGraphicDOTweenAction and ColorGraphicDOTweenAction, given it's a (hopefully) temporary workaround, is this OK? There is no common base class in which the Graphic component is available so no clean place to put a shared function. Any ideas here?

With the above in mind, is there anything I need to do here to get the PR mergeable?

Thanks,

Niall