Component States | Feature Requests

ProtoPie

Create

Roadmap

Feature Requests

252

Component States

under review

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)

December 10, 2019

DavidT Kim

marked this post as

under review

f83 pix

B U M P

Alexander Vinogradov

Any Progress on this?

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.

ProtoPie

Merged in a post:

Binary/Multi-state switch trigger

Andrey Zhilin

For the sake of saving time spent on manual creation of variables and conditions for switch-type behaviour, we can have a dedicated Trigger with automated formatting for that.

January 20, 2020

September 1, 2020

ProtoPie

Merged in a post:

Instane vs. class variables in Components

Jan-Peter Krämer

It would be super helpful to have components either have separate state in each instance (such as a button) or shared state in all instances. The latter would allow to, e.g., build a status bar that you can manipulate but that retains its state across multiple scenes.

This is already possible for variables in scenes, that can either be local for a single scene or global.

July 13, 2020

July 15, 2020

Martin Boerma

A simple work around for component states
Example. A tab bar has three tabs and thus three states.
Create one tab bar component.
Inside component create three overridable variables, state01, 02 and 03
Create a Start trigger that evaluates all three variables
If variable state01 is true then set component to state01
If variable state02 is true then set component to state02
If variable state03 is true then set component to state03
Now you can put the component instances in a certain state by overriding the correct state variable.

Dana Avesar

Martin Boerma: How do I override the variable from outside the component? I want a tap on another shape to trigger than state change within this component

Dain Saxon

Axure has been doing this for years and years. So, like, copy them!

Eirik Somerville

Yes please!

→