Designer problems

[alprinias]

Hello,

I'm using v. 2.3.2-Beta with VS2015, targeting .NET Framework 4.7.1. When I add bindings using the designer, it is not clear how to save bindings. There are Add, Edit and Delete but not a Save button. So when I move to another control of the form, I get a dialog asking if I want to save the changes before changing to another control (in German) but even if I press "Yes" the changes are not saved. The dialog keeps coming up after that for every moving between controls. Same for Delete button. The binding gets deleted from the grid when I press the button, but when I come back to the control it is still there.

I am not sure how, but when I finally managed to add a couple of bindings I get an exception if my model's property is double and I bind it to the text property of a label. I also used an object to string converter.

A very simple tutorial would be great to support this extremely interesting work you have done!

All the best, Alex

[KlausLoeffelmann]

Hey Alex,

Take a look at the GitHub wiki of MvvmForms - there is a detailed description how to use it. It should also link to a YouTube video!

We will look into the localization issue today, and come back to you, soon! Can you provide a screenshot so we see which dialog is not localized?

Thanks so much

Klaus

[alprinias]

Hi Klaus, thanks for your answer. I have looked at the wiki. I will go through the Youtube video in case I am missing something. To describe what I am doing: Open the dialog, select the control I need from the treeview on the left, (TextBox1 in my case), press the "Add" button (in the series of Add, Edit, Delete buttons). No row is added to the gridview above. I select the Text property from the TextBox1's properties and a String Property from my model. How do I save???

The localization is the least of my problems, since I know some german, however, the message goes: "Mochten Sie Ihre Anderungen speichern, bevor Sie die nachste Eigenschaftenzuweisung bearbeiten?" (with the missing Umlaut of course).

Vielen Dank! Alex

[surgien]

Hey,

If you are open the dialog, you have already an entry for the first binding and you can choose your binding properties. Then you press "Add" to add the Binding to the grid (or edit to modify). The save function is in the Add, Edit and Delete button included. For more details about the binding assignment, you can look into the youtube video (around minute 31).

Greetings Stephan

[alprinias]

Hi again, So, after watching your YouTube video I managed to have TextBoxes and Labels work. However, I would like to use WinForms Buttons, which do not exhibit the Command property, the way your CommandButton does. What is the way to make them work? The reason I'm not using your CommandButton is that I would like ultimately to apply your framework NOT to WinForms but to Wisej (have a look at wisej.com), a WinForms-like ASP.NET implementation, which does not include a CommandButton.

Best regards, Alex

[KlausLoeffelmann]

Hey Alex,

While I‘m not at all familiar with that framework, I‘m pretty sure the underlying infrastructure is completely different from WinForms, so I would be surprised if binding would work the same. But if it did, you could always try to call the methods of a ViewModel directly from the view, to see if everything else works in principle, and go from there.

[alprinias]

Hi Klaus, What you are saying is correct, I'll give it a try. I believe it will work, and the combination will be great! In fact you should give it a try too, you'll be amazed by the simplicity and how close to WinForms it is. I have tried Wisej with Reactive UI (another MVVM "framework") and it works, but I find your approach much cleaner.

However:

1. you haven't answered my question :-) If I want to use a normal Winforms button with your framework, how do I do it?
2. Apart from PropertyBindings, the MvvmManager extends the controls with EventBindings. How are these used? Best, Alex

[alprinias]

Hello again! Kind reminder ... for the lat two questions.

Thank you, Alex

[surgien]

Hey 1: via code behind 2: EventBindings are not final now Greetings Stephan