Skip to main content
D
1m ago

Please make frame 1 of a timeline, when triggered by a state machine NOT be the state of the object pulled through from design mode.

Hello team... great new features!

I looked to see if this was already posted, but I could not find it. Apologies if it is.

I think it is very confusing when the following happens:

  • In design mode, user designs his/her screen the way they want it. In this example, lets say that the user is creating a button and it is fully designed and at 100% opacity in design mode.

  • the user switches over to animate mode,and wants to the button to fade from 0% opacity to 100% full opacity, and so they set key frames to achieve this on a timeline 1.

  • The user sets up a state machine to trigger the button fade in from 1 to 100... yet... when the timeline is triggered... it is still showing the exact same state the button was in over in design mode.... and is using that state as the first frame of the animation timeline. This does not make sense.

Change request: Please make the first frame of the object's timeline only relevant to what is tweaked in animate mode. If the object is at 0% opacity in animate mode for example, it should look like that once the state machine is run, which triggers the timeline. It should not pull through the state of the object as the first frame from design mode. This is very confusing and it creates the following problem:

  • if the user needs to edit the look of an object over in design mode, and the object is at 0% opacity in animate mode, they have to either drag the playhead to the point in the timeline where the object IS NOT at 0%, then jump over to design mode to make the edits. Because in this example... the user would have already changed the opacity from 100 to 0 in design mode... because they needed that as their starting point in the animate mode timeline. OR

  • The user needs to jump over to design mode, change the opacity back to 100%... then make their visual edits... then change it back to 0% again so the object will be at 0 for the first frame of the timeline.

This is very counterintuitive and requires a lot of steps in order to set things up right. I would suggest having animate mode be its own silo, and design mode be its own separate solo. With frame 1 not being the state the object is in... in design mode.

Please let me know of there an alternative or work around to this.

Thank you

Join the discussion
Join Rive to reply J