Share content between 2 controls

Question

0.00/5 (No votes)

See more:

I have the following code:

XML

<Grid>
    <Grid.ColumnDefinitions>
        <ColumnDefinition Width="*"/>
        <ColumnDefinition Width="Auto"/>
        <ColumnDefinition Width="*"/>
    </Grid.ColumnDefinitions>
    <ContentControl x:Name="MainContent" Grid.Column="0">
        Some content
    </ContentControl>
    <GridSplitter Grid.Column="1" Width="5"/>
    <ContentControl Content="{Binding ElementName=MainContent, Path=Content}" Grid.Column="2"/>
</Grid>

This shows the content of the first ContentControl in both sides.
If I change the "Some content" text to any control it shows the content only in the second ContentControl and not in both.

Is there any way to do this?

Posted 5-Jun-13 19:46pm

Itamarep

Add a Solution

2 solutions

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-06-05T20:35:00

Solution 1

One way to share is to use XAML resource dictionaries: http://blogs.msdn.com/b/wpfsldesigner/archive/2010/06/03/creating-and-consuming-resource-dictionaries-in-wpf-and-silverlight.aspx[^].

—SA

Posted 5-Jun-13 20:35pm

Sergey Alexandrovich Kryukov

Comments

Itamarep 9-Jun-13 8:40am

In my case, I want to display 2 web browsers that will display the same content and when browsing in one it will show the same results in the other.
If I connect the source to a resource it will browse in both opening the same page twice, more than that, if an internal script on the page changes the display, the URL doesn't have to change meaning they will display different pages (under the same URL)

Sergey Alexandrovich Kryukov 9-Jun-13 13:03pm

And how is that related to the original question?
OK, please see Solution 2 then.
—SA

Sergey Alexandrovich Kryukov · Answer 2 · 2013-06-09T07:02:00

The question asked in the comment to Solution 1 has nothing to do with the original question:

Itamarep asked:
In my case, I want to display 2 web browsers that will display the same content and when browsing in one it will show the same results in the other. If I connect the source to a resource it will browse in both opening the same page twice, more than that, if an internal script on the page changes the display, the URL doesn't have to change meaning they will display different pages (under the same URL)

System.Windows.Controls.WebBrowser is not System.Windows.Controls.ContentControl, and the media content it shows has nothing to do with the content of ContentControl:
http://msdn.microsoft.com/en-us/library/system.windows.controls.webbrowser.aspx[^].

Isn't the resolution of this problem, especially taken into account the last clause about the effect of the page's "internal script" trivial?
The browser URI is changed is 1) you navigate to some other URI using one of the Navigate methods; 2) when a use clicks in some HTML navigation control (such as anchor) inside the page currently rendered; in other way, you can navigate using some different URL from outside the browser's page and from the page. In first case, simply call the same Navigate method from both browser.

The second case is just a little bit different and asymmetric: handle the event Navigating in one browser instance, and, in its handler, call Navigate for another browser instance accordingly.

First and foremost, don't try to handle this event in both browsers in reciprocal manner, to avoid "infinite" mutual recursion: http://en.wikipedia.org/wiki/Mutual_recursion[^]… :-)

—SA