Wpf animation handling twice

Question

0.00/5 (No votes)

See more:

Hi. The wpf animation is handling twice. do not why.
so, here is the code:

C#

public void FadeIn()
{
    //fade in animation for user control
	DoubleAnimation opFadeInAnim = new DoubleAnimation(1, FadeTime);
    opFadeInAnim.Completed += delegate(object s, EventArgs e)
    {
        if (OnFadedIn != null)
        OnFadedIn(this, EventArgs.Empty);
    };
    this.BeginAnimation(UserControl.OpacityProperty, opFadeInAnim);
}

i subscribe only once for OnFadedIn event, but event is firing twice

Posted 17-Jan-15 11:44am

Arlert

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2015-01-17T12:08:00

The problem is cannot be seen from this fragment of code along.

So, first put a break point at the point of += operation and make sure this place is executed exactly once. Mayne not, by whatever reason. If it's done just once, put a break point on the beginning of your event handler. According to your report, it will execute more than once. Then, on each stop on this break point, look at the debug window "Call stack". Using these techniques, find out where what causes event invocation in all cases; then you will be able to find out what's going wrong.

—SA