UWP:通过后台线程的数据绑定更新 UI [英] UWP: Updating UI through data binding from a background thread

查看:26
本文介绍了UWP:通过后台线程的数据绑定更新 UI的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在我的 UWP 应用程序中使用 x:Bind(编译绑定)将 TextBlock 绑定到 ViewModel 中的整数属性,该属性由值转换器转换为字符串.我在工作线程上的 ViewModel 中使用一种方法来设置属性并调用 PropertyChanged 事件.但是,我收到一个异常(具体来说,它在 MainPage.g.cs 文件的 XamlBindingSetters 类中)说,应用程序调用了一个为不同线程编组的接口."

I'm using x:Bind (compiled binding) in my UWP app to bind a TextBlock to an integer property in the ViewModel which is converted to a string by a value converter. I am using a method in the ViewModel on the worker thread to set the properties and call the PropertyChanged event. However, I am getting an exception (specifically, it's in the XamlBindingSetters class in the MainPage.g.cs file) saying, "The application called an interface that was marshalled for a different thread." According to this post, this should work just fine in WPF; has this ease of functionality been removed in WinRT/UWP or am I doing something wrong?

Here's exactly what I'm doing.

My property is defined like this:

private int myProperty;

    public int MyProperty
    {
        get { return myProperty; }
        set
        {
            Set(ref myProperty, value);
        }
    }

The Set method is part of the Template 10 library and is defined:

public bool Set<T>(ref T storage, T value, [CallerMemberName]string propertyName = null) 
     { 
         if (object.Equals(storage, value)) 
             return false; 
         storage = value; 
         RaisePropertyChanged(propertyName); 
         return true; 
     } 

Nothing wrong there from what I can see; it just makes sure the new value is different than the old value and then calls RaisePropertyChanged(propertyName) which makes sure the app is actually running (not in design mode) and then raises the PropertyChanged event.

I set my property from a worker thread:

MyProperty = newValue;

and when it gets to the XamlBindingSetters class:

internal class XamlBindingSetters
    {
        public static void Set_Windows_UI_Xaml_Controls_TextBlock_Text(global::Windows.UI.Xaml.Controls.TextBlock obj, global::System.String value, string targetNullValue)
        {
            if (value == null && targetNullValue != null)
            {
                value = targetNullValue;
            }
            obj.Text = value ?? global::System.String.Empty;
        }
    };

it breaks on that last line (obj.Text = ...) and tells me that the application called an interface that was marshalled for a different thread. What am I doing wrong?

解决方案

You need to execute all graphical objects in the UI Thread.

Typical usage:

obj.Invoke((MethodInvoker) SomeMethod);

See How to Use ISynchronizeInvoke interface?

这篇关于UWP:通过后台线程的数据绑定更新 UI的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆