cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
EpicTriffid
Helper V
Helper V

Stutting in Animations

Hi all,

 

So I've been trying to implement an animation timer to expand and contract a box, rather than just having it pop in and out of existence. However, with any guides I find, none talk about the stutter effect when you press the button to expand or contract it.

For example, on expanding, the box will appear at full size for a moment, disappear, then begin the animation of expanding. Is this a problem other people have experienced? It's making me feel really reluctant to use animations in my final app.

I've included three pages where people explain their methods and provide sample apps, but they all have the same issue with that stutting effect. Is there someway around this?

 

https://powerapps.microsoft.com/en-us/blog/ux-patterns-expander-control-with-expand-collapse-animati...

 

https://8bitclassroom.com/2018/02/21/powerapps-remix-expand-and-collapse-ui/

 

https://powerusers.microsoft.com/t5/PowerApps-Community-Blog/Vertical-menu-with-expand-and-collapse-...

1 ACCEPTED SOLUTION

Accepted Solutions
RusselThomas
Community Champion
Community Champion

Hi @EpicTriffid ,

 

First, let's assume timer duration is set to 500ms, and target height of rectangle is 500 to keep it simple.  We also use a value of true for menuDirection when it's opening, false when it's closing.  By default it starts off false.

Button Onselect:

UpdateContext({animatonStart: true, menuDirection: !menuDirection})

Timer;

OnTimerEnd: UpdateContext({animationStart: false})
Start: animationStart

Duration: 500

 

Rectangle Height:

If(menuDirection, Timer.Value, 500-Timer.Value)

So here's where the stutter comes in.  If you're using the Timer.Value as the derivitive value for your menu height, then the reason you get the stutter is the end state of the Timer and how it resets.  Certainly, this was the case for me, so I'm guessing it's the same for you.

The timer always runs in one direction - from 0 to 500. 

At the end of its cycle, it's sitting at 500.  When the cycle starts again, even though it resets - it resets from 500, meaning your rectangle starts at 500, then jumps to 0 as the timer restarts - hence the stutter.

To avoid this, we need to do two things;

  • Reset the timer automatically after a cycle.
  • Record the state of the rectangle (open or closed) and specify the open or closed height, using that as our base instead of the Timer.Value for the height

Timer;

OnTimerEnd:

UpdateContext({runAnimation: false});
Reset(Timer);
If(menuDirection, 
    UpdateContext({menuState: 500}), 
    UpdateContext({menuState: 0}))

Start: animationStart

Duration: 500

Rectangle Height:

If(menuDirection, menuState+Timer.Value, menuState-Timer.Value)

This cleared it up for me 🙂

Hope this helps,

RT

View solution in original post

7 REPLIES 7
RusselThomas
Community Champion
Community Champion

Hi @EpicTriffid ,

 

First, let's assume timer duration is set to 500ms, and target height of rectangle is 500 to keep it simple.  We also use a value of true for menuDirection when it's opening, false when it's closing.  By default it starts off false.

Button Onselect:

UpdateContext({animatonStart: true, menuDirection: !menuDirection})

Timer;

OnTimerEnd: UpdateContext({animationStart: false})
Start: animationStart

Duration: 500

 

Rectangle Height:

If(menuDirection, Timer.Value, 500-Timer.Value)

So here's where the stutter comes in.  If you're using the Timer.Value as the derivitive value for your menu height, then the reason you get the stutter is the end state of the Timer and how it resets.  Certainly, this was the case for me, so I'm guessing it's the same for you.

The timer always runs in one direction - from 0 to 500. 

At the end of its cycle, it's sitting at 500.  When the cycle starts again, even though it resets - it resets from 500, meaning your rectangle starts at 500, then jumps to 0 as the timer restarts - hence the stutter.

To avoid this, we need to do two things;

  • Reset the timer automatically after a cycle.
  • Record the state of the rectangle (open or closed) and specify the open or closed height, using that as our base instead of the Timer.Value for the height

Timer;

OnTimerEnd:

UpdateContext({runAnimation: false});
Reset(Timer);
If(menuDirection, 
    UpdateContext({menuState: 500}), 
    UpdateContext({menuState: 0}))

Start: animationStart

Duration: 500

Rectangle Height:

If(menuDirection, menuState+Timer.Value, menuState-Timer.Value)

This cleared it up for me 🙂

Hope this helps,

RT

v-xida-msft
Community Support
Community Support

Hi @EpicTriffid ,

Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned.

 

Please take a try with the following workaround:2.JPG

 

3.JPG

 

4.JPG

 

5.JPG

Set the OnSelect property of the "DownIcon" button to following:

Set(IsExpand, true);Set(IsStart, true)

set the Visible property of the "DownIcon" button to following:

If(IsExpand, false, true)

Set the OnSelect property of the "UpIcon" button to following:

Set(IsExpand, false); Set(IsStart, true)

set the Visible property of the "UpIcon" button to following:

If(IsExpand, true, false)

Add a Timer control, set the Duration property to following:

222

set the OnTimerEnd property to following:

Set(IsStart, false)

set the IsStart property to following:

IsStart

Please check the following GIF screenshot for more details:Test.gif

Please also consider take a try with the attached Sample App as below.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thank you @RusselThomas! For the life of me, I couldn't work out the WHY of the problem. Extremely grateful for the explanation

Hi again @RusselThomas! How would you use this process when trying to integrate easing equations, such as Cos. For example:

 

If(expandCollapse,
95*Cos('ani timer_1'.Value/'ani timer_1'.Duration * Pi()/2),
95*(1-Cos('ani timer_1'.Value/'ani timer_1'.Duration * Pi()/2)))

where 95 would be the max height of the box and expandCollapse is the equivalent of your menuDirection?

Hi @EpicTriffid 

You're way ahead of me there - maths was never my strong suit!

My approach to easing is a lot less elegant, but that's just because I don't have a clue how to construct the formulas you're suggesting - I just specify keyframes in the duration that would correlate in segments to your bezier or spline-related easing path.  Less smooth, but works for my brain 🙂

Assuming the breakdown of path velocity as follows;

0-10% = "slow"

10%-80% = "fast"

80%-100% = "slow"

I'd base my height changes as a factor of where the timer is in it's journey.

Using your formula's though would be much more elegant, and smoother as it adjusts for every single tick - even better if we could build in some easing functions in PA that correlate to some of the more popular behaviours (https://easings.net/en).

Sorry I can't help, but I'll definitely watch this post to see what you come up with 🙂  Perhaps you can come up with a nice 'easing calculator' component to share!

 

Good luck!

RT

Do you have any thoughts on how to save the state of the box at its various points like it your previous solution so that I can avoid the stuttering? I can use my expandCollapse variable the get the movement to work, using the easing equations, but it's still stuttering. I would assume because, like you said, the timer is resetting to 0?

Hi @EpicTriffid ,

Not sure if I'm understanding you correctly, but my savestates were done at the end of the timer duration - i.e. OnTimerEnd property, when completely open or completely closed.

There I set the fully open and fully closed height values depending on the value of the direction, so in your case I'm guessing this would equate to;

 

OnTimerEnd:

UpdateContext({runAnimation: false});
Reset(Timer);
If(expandCollapse, 
    UpdateContext({menuState: 95}), 
    UpdateContext({menuState: 0}))

and the Height property of the box would be ;

If(expandCollapse,
menuState + 95*Cos('ani timer_1'.Value/'ani timer_1'.Duration * Pi()/2),
menuState - 95*(1-Cos('ani timer_1'.Value/'ani timer_1'.Duration * Pi()/2)))

 ...just guessing though, hope this helps

 

RT

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   Week 2 Results:  Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Top Solution Authors
Top Kudoed Authors
Users online (3,500)