352
Component States
Alexander Vinogradov
Now it takes an enormous amount of time to create a simple tabs menu with buttons having active and normal states. Please do an ability to make a "snapshot" of the component and save it as a "state". Then allow to tween between them (or simply switch). Now it takes 2 hours to just set up showing/hiding and recoloring the text/shapes of the simple button (up/down/active/disabled)
Activity Feed
Sort by
Patricia (ProtoPie Team)
Merged in a post:
Import Figma component states
Fynn MLlyr
When importing components with states, translate those states into equivalent triggers, conditions, and actions. Currently, when I import a component with states from Figma, it's not interactive at all. Recreating that in Protopie is a huge time suck.
Matthew Mercer
Agreed, having "states" within each component, a feature available in proto.io, would make components more capable and make the workflow for tasks as described above much simpler. +1
e
eden huh
open
S
Saulo Vallory
There's a cheap way to get 80% of this. You guys could simply show unmediatable interaction previews. That would already be a huge help.
The idea is that, for each trigger, we would have in the editor a preview of what the component would look like after all responses have been executed. And it can be a simple preview! Editing can be done as we do today as long as the trigger preview is automatically updated
L
Lucas Malaquias
Hopefully we can get this feature soon
D
DavidT Kim
under review
f
f83 pix
B U M P
Alexander Vinogradov
Any Progress on this?
F
Florin Ursu
Up on this, Protopie! This, and autoanimate would make you win the market! A desperate pretty please, cause would cut my time by 25% prototyping.
Imagination Digital Team
It's driving me crazy that this isn't just a simple built in function! creating a form in an overlay or any filtering component feels like doing surgery! Figma & XD actually do this really well.
Load More
→