Stylet | powerful ViewModel-First MVVM framework

I have tried to create these, but not able to understand how to keep the relation between these and insert/get the saved data.

You can do this 2 ways either with:

• a POJO with all three tables @Embedded (only suitable for 1 Org -> 1 Login and 1 Style)

• with a POJO with the OrgTable @Embedded and with the LoginOptionsTable and StyleTable with @Relation annotations

An example of the first (all three tables @Embedded) being :-

Jason Tyler's reply got me going in the right direction. Thank you!

So because I am using a ViewModel first pattern, I did not need to specify the DataContext of the user control like I thought...Its already set.

However, his suggestion of binding using the relative source and researching on how to do this (I have never used RelativeSource before..I am kinda new to this stuff) I came across this Stack post

How do I use WPF bindings with RelativeSource?

A Jeff Knight Posted a diagram of how ancestor binding works.

Using that, I was able to figure out the syntax and my document came right up and I can still use the right click context menu items that are bound to Telerik. So now my Xaml looks like this note how the Document source binding has changed.

Memo could be useful when you don't expect your component to change often. It comes with a cost that does these evaluations to verify if it should rerender.

In your case you would have a lot of rerenders because several components would need to be rerender to fit the correct background which is a downside to use Memo.

Besides, you would see these bugs, since other components won't rerender given their props won't change.

I would suggest to remove memo for this case.

You see the accordion effect that you have right? You wouldn't see that effect if the component did unmount. That means the component never unmounts. You are using 2 show states, one state created at root at your App and another state that comes from your reducer.

Your button only flips the reducer show state. But to render TaskItem you use the stale show state created, that is always true. If you were using the redux state there wouldn't be any effect at all:

when using transition, if you declare for multiple properties then you need to set transition-duration (and any other prop you want) to each of then. the way you wrote only opacity had transition-duration set. you need to add to max-height also:

After a lot of attempts, I finally found the culprits :

• INPC not implemented in ShoppingCartModel.Item despite the PropertyChangedBase inheritance (either implementing INPC or remove the PropertyChangedBase inheritance work)

You do not have to create a new ViewManager, as this scenario is already supported.

You just have to add a namespace transformation to the ViewManager that maps a view model from StyletViewModels.ViewModels namespace to a view from the StyletProj.Pages namespace.

I realize I am missing property changed notifications. Through all of the examples I saw I assumed this was handled implicitly by Stylet for me.

After changing my property setters to the following, it works as expected.

You need to read this page: https://github.com/canton7/Stylet/wiki/StyletIoC-Injection

There is an attribute [Inject] that will get the class you need from the DI container.

something like:

You should add the trigger(s) to the ItemTemplate, e.g.: