Override Component Variables with Scenes Variables | Feature Requests

ProtoPie

Create

Roadmap

Feature Requests

759

120

Override Component Variables with Scenes Variables

Kimball Wirig

Ability to override a component variable with a global or scene level variable would be very helpful in allowing multiple components respond in harmony with each other.

October 23, 2019

Activity Feed

Sort by

J Rub

+1 for ability to control All-Scene variables from components (nested or not) - true globals please.

Patricia (ProtoPie Team)

Merged in a post:

Access Component variables from main scene

Pepe

It would be great to access the (exposed) component variables from the main scene.

August 10, 2019

January 2, 2022

Patricia (ProtoPie Team)

Merged in a post:

Expose component layers to triggers/overrides

Mikael Staer Nathan

To make components truly useful, the layers within a component should be accessible to triggers in scenes.
Example: a button that opens a flyout menu, with hover states on menu items. I want to add different triggers to those menu items in different scenes (for example, Jump).
Also, you should be able to access component variables in scenes and/or access global variables from within components.

June 30, 2020

January 1, 2022

Patricia (ProtoPie Team)

Merged in a post:

Create variable for all scenes inside Components

ALEN KHODUZADEH

This is critical when we have fixed menu item that holds information specially in automotive prototypes

January 14, 2021

January 1, 2022

Patricia (ProtoPie Team)

Merged in a post:

Allow variables to be pushed from scene into a component

John Redhead

It would be great to allow variables to be pushed back (on a case by case basis) into a component, without having to build send /receive triggers, which potentially need to be on every page. When you have a large number of pages this can become burdensome.

December 3, 2020

December 24, 2021

Patricia (ProtoPie Team)

Merged in a post:

Use 'Detect' trigger on component variables

mark pearce

Expose the overridable variable in a component to the Detect trigger so that they show up like the layer properties

This would save on a lot of send/receive, and make it easier to use values in components.

May 3, 2020

December 24, 2021

Patricia (ProtoPie Team)

Merged in a post:

Make a Variable for All Scenes from a Component

Rob Cleaton

The ability to also make a Variable For All Scenes from a component.

This would be useful for assigning a value in the component that could be detected on the Scene.

December 17, 2019

June 2, 2021

Florian Grau

I am trying to do the same thing: The same trigger should jump to different scenes, depending on a variable. However the component cannot access the global variable and the variable inside the component seems to only live within the instance instead of across all instances.

Alexandre Schrammel

Something like global variables?

Alexander Nehls

Yes, please! Not being able to access "global" variables inside of components makes it really really hard to work with nested components. You have to pass values from one component to the next. This is really tedious.

→