Reply to thread

Message

<blockquote data-quote="morpheus_xx" data-source="post: 1031225" data-attributes="member: 48495">The cause is simple, I had to learn this difference to WPF myself:In MPF you also need to expose the AbstractProperty for xaml binding.If your property is named &quot;Width&quot; you have to expose &quot;public AbstractProperty WidthProperty&quot;.Another important note: from models use only WProperty (weak references). SProperty is only allowed for controls.For an example and comments take look at the HelloWorldModel:[CODE=csharp]&nbsp; &nbsp; /// &lt;summary&gt;&nbsp; &nbsp; /// This sample property will be accessed by the hello_world screen. Note that the data type must be the same&nbsp; &nbsp; /// as given in the instantiation of our backing property &lt;see cref=&quot;_helloStringProperty&quot;/&gt;.&nbsp; &nbsp; /// &lt;/summary&gt;&nbsp; &nbsp; public string HelloString&nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; get { return (string) _helloStringProperty.GetValue(); }&nbsp; &nbsp; &nbsp; set { _helloStringProperty.SetValue(value); }&nbsp; &nbsp; }&nbsp; &nbsp; /// &lt;summary&gt;&nbsp; &nbsp; /// This is the dependency property for our sample string. It is needed to propagate changes to the skin.&nbsp; &nbsp; /// &lt;/summary&gt;&nbsp; &nbsp; /// &lt;remarks&gt;&nbsp; &nbsp; /// &lt;para&gt;&nbsp; &nbsp; /// If the screen databinds to the &lt;see cref=&quot;HelloString&quot;/&gt; property in a binding mode which will propagate data&nbsp; &nbsp; /// changes from the model to the skin (OneWay, TwoWay), the SkinEngine will attach a change handler to this property&nbsp; &nbsp; /// and react to changes.&nbsp; &nbsp; /// &lt;/para&gt;&nbsp; &nbsp; /// &lt;para&gt;&nbsp; &nbsp; /// In other words: For each property &lt;c&gt;Xyz&lt;/c&gt;, which should be able to be attached to, there must be an&nbsp; &nbsp; /// &lt;see cref=&quot;AbstractProperty&quot;/&gt; with name &lt;c&gt;XyzProperty&lt;/c&gt;.&nbsp; &nbsp; /// Only if &lt;c&gt;XyzProperty&lt;/c&gt; is present in the model, value changes can be propagated to the skin.&nbsp; &nbsp; /// &lt;/para&gt;&nbsp; &nbsp; /// &lt;/remarks&gt;&nbsp; &nbsp; public AbstractProperty HelloStringProperty&nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; get { return _helloStringProperty; }&nbsp; &nbsp; }[/CODE]</blockquote>

[QUOTE="morpheus_xx, post: 1031225, member: 48495"] The cause is simple, I had to learn this difference to WPF myself: In MPF you also need to expose the AbstractProperty for xaml binding. If your property is named "Width" you have to expose "public AbstractProperty WidthProperty". Another important note: from models use only WProperty (weak references). SProperty is only allowed for controls. For an example and comments take look at the HelloWorldModel: [CODE=csharp] /// <summary> /// This sample property will be accessed by the hello_world screen. Note that the data type must be the same /// as given in the instantiation of our backing property <see cref="_helloStringProperty"/>. /// </summary> public string HelloString { get { return (string) _helloStringProperty.GetValue(); } set { _helloStringProperty.SetValue(value); } } /// <summary> /// This is the dependency property for our sample string. It is needed to propagate changes to the skin. /// </summary> /// <remarks> /// <para> /// If the screen databinds to the <see cref="HelloString"/> property in a binding mode which will propagate data /// changes from the model to the skin (OneWay, TwoWay), the SkinEngine will attach a change handler to this property /// and react to changes. /// </para> /// <para> /// In other words: For each property <c>Xyz</c>, which should be able to be attached to, there must be an /// <see cref="AbstractProperty"/> with name <c>XyzProperty</c>. /// Only if <c>XyzProperty</c> is present in the model, value changes can be propagated to the skin. /// </para> /// </remarks> public AbstractProperty HelloStringProperty { get { return _helloStringProperty; } } [/CODE] [/QUOTE]

Verification