162
Component States
A
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
Newest
Oldest
ProtoPie
ProtoPie
Merged in a post:
Instane vs. class variables in Components
J
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.
M
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.
D
Dain Saxon
Axure has been doing this for years and years. So, like, copy them!
Eirik Somerville
Yes please!
Joao Rios
This should come with quickly changing multiple component states at once, for example for calendar selections, radio buttons, etc, where we need to select one while diselecting any other
A
Ajith Sowndararajan
Ability to have states within components will be very powerful and is closer to how a UI is implemented.
Will be great to have this.