Skip to content

Settings and activity

7 results found

  1. 737 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Juho Röyhy supported this idea  · 
  2. 956 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Juho Röyhy supported this idea  · 
  3. 1,472 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Juho Röyhy supported this idea  · 
  4. 834 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Juho Röyhy supported this idea  · 
  5. 37 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Juho Röyhy supported this idea  · 
  6. 213 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Juho Röyhy commented  · 

    Currently updating highly interactive component contents is a mess. For each instance you need to go through all of the states and update contents & size as there's is no propagation possibilities.

    Currently changes done to main component propagate to all instances of component if there hasnt been done any overrides in instances regarding updated parameters. This sort of propagation should be applied to component instances default state as well to easily update all of the child states with proper content / size.

    See attached picture describing the issue and solution in the best possible way.

    Juho Röyhy supported this idea  · 
  7. 313 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Please note that stacks is a feature that is intended to be used at design time, and does not dynamically shift the stack in preview. I’m going to rewrite this particular request to be more precisely about the latter suggestion.

    An error occurred while saving the comment
    Juho Röyhy commented  · 

    Stacks work as intended in Design mode, but when you actually drive the prototype stack doesn't update on all changes that are happening inside stack.

    See attached example where there are one mother stack and two child stacks and when child stack's size changes mother stack doesn't update when in "play mode" on design mode it works just fine.

    Juho Röyhy supported this idea  ·