wpf modeless dialog and windows, how to communicate

Question

3.50/5 (2 votes)

See more:

I want to ask a question , maybe it is stupid , but I want to best solution , so here it is:

I have a mode-less dialogue in wpf, its owner is a window. when I click a button on the model-less dialogue I want to do something on a part of windows.

I tried a solution like that:
define a static methods of that owner window, and call that static method on every click of button on modelless dialog, but in this static methods I have no access to datagrid. (on every click I want to select different row in a datagrid which is on window) and I guess define a object of that window in click of dialog is not good idea.

how can I response the click in window ? how can I communicate between them and I should have access to controls in window?

could anyone tell me or direct me to solution?

Posted 2-Aug-11 22:47pm

Alimjan Yasin

Add a Solution

2 solutions

Solution 1

There is no a concept of modeless dialog in WPF, to the best of my knowledge. It must be the regular window, owned by a main window.

Your approach is not the best. The most robust approach is implementing appropriate interface in a windows class. In this way, another windows should get only the interface reference representing the other window, which improves the isolation of windows — only the interface required for collaboration is passed.

Also, there is a very convenient way to implement interface in the window class. Pay attention, a window class is declared as partial. You can add one more file representing the same class and add a separate partial declaration of it. The trick is: the inheritance list should be be repeated in all parts. You specify a base class in one part (it it already done in the auto-generated code), and one or more interfaces in the inheritance list in other parts.

In this way, you can create a separate file with partial class declaration containing only the interface to be implemented in the inheritance list and its implementation.

—SA

Posted 2-Aug-11 22:59pm

Sergey Alexandrovich Kryukov

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

BobJanova · Accepted Answer · 2011-08-02T23:10:00

In WPF you should have the data grid (including its selected index property) bound to a view model. Give the second form a reference to that view model instance and then it can simply set the property (which will cause the UI controls on the first form, and anything else that is watching it, to update).

For some types of change you might want to modify the underlying model, instead. But selecting a different row seems like a view model thing to me. And generally in WPF you should go through the view model, as all the update and binding mechanics are attached there and not normally to the model (though if one model is attached to by several VMs, it makes sense to have notify mechanics on it as well).