Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8217051
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T12:20:42+00:00 2026-06-07T12:20:42+00:00

If I have XAML element that is binded to a data source property and

  • 0

If I have XAML element that is binded to a data source property and the data source changes faster then the human eye can see I am assuming that the UI also gets re drawn faster then the human eye can see and wasting resources. Would it be a good idea for the property change to raise a flag instead of triggering re-draw of UI and then a timer to trigger the UI redraw if the property was changed? or am I missing how the UI gets re-drawn?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T12:20:43+00:00Added an answer on June 7, 2026 at 12:20 pm

    You Could use a delyed invocation of raising the property changed event, maybe like this…

    public static class DispatcherExtensions
    {
        private static Dictionary<string, DispatcherTimer> timers =
            new Dictionary<string, DispatcherTimer>();
        private static readonly object syncRoot = new object();
    
        public static void DelayInvoke(this Dispatcher dispatcher, string namedInvocation,
            Action action, TimeSpan delay,
            DispatcherPriority priority = DispatcherPriority.Normal)
        {
            lock (syncRoot)
            {
                RemoveTimer(namedInvocation);
                var timer = new DispatcherTimer(delay, priority, (s, e) => action(), dispatcher);
                timer.Start();
                timers.Add(namedInvocation, timer);
            }
        }
    
    
        public static void CancelNamedInvocation(this Dispatcher dispatcher, string namedInvocation)
        {
            lock (syncRoot)
            {
                RemoveTimer(namedInvocation);
            }
        }
    
        private static void RemoveTimer(string namedInvocation)
        {
            if (!timers.ContainsKey(namedInvocation)) return;
            timers[namedInvocation].Stop();
            timers.Remove(namedInvocation);
        } 
    
    
    } 
    

    Then

    private object _property;  
    public object Property  
    {  
        get { return _property; }  
        set  
        {  
            if (_property != value)  
            {  
                _property = value;  
                Dispatcher.DelayInvoke("PropertyChanged_Property",(Action)(() =>
                {
                     RaisePropertyChanged("Property");   
                }),TimeSpan.FromMilliseconds(500));
    
            }  
        }  
    }  
    

    Not sure i like it though…

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I thought that element property syntax and attribute property syntax have no big semantical
I have the following xaml inside a text box element that is part of
I want my application to have a zoomable element which will allow the XAML
Can I have more than one XmlElement on property of a class? For example:
I have a Xaml file that does not have any code behind. I would
I have a .xaml file and a .cs file that share value with Binding.
I have read that SL4 introduces the ability to data bind properties on objects
It seems that d:IsDataSource can be used to provide design time data in blend
We have a languaging mechanism that recurses through our XAML pages when they load,
I have a TextBox that is bound to my ViewModel. The TextWrapping property of

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.