|
still i did not get the solution for this..
|
|
|
|
|
Hi All,
I've been living a lie!
I thought that using this in XAML
DataContext="{Binding RelativeSource={RelativeSource self}}"
Would ALWAYS point to the .xaml.cs code behind file ... hmm, how wrong!
|
|
|
|
|
Jammer wrote: Would ALWAYS point to the .xaml.cs code behind file ... hmm, how wrong!
Yup. RelativeSource.Self allows you to point one property to another property on the same element, e.g.
<TextBlock Width="{Binding RelativeSource={RelativeSource Self}, Path=Parent.ActualWidth}"/>
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
|
Never starts in my case. 
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
Oh give over!
|
|
|
|
|
Dear friends
i have an doubt,
i have Page 1,Page 2 and view model for both.
now i have button in page 1 that is bound to a command
and now when i click that button it goes to view model command (and now here i want to open the second screen but second screen in view)
tel me how to access view objects in view model?
any idea? link?
by
Joe.I
|
|
|
|
|
Joe - it's generally considered to be a bad idea to put knowledge about a view into the viewmodel. This can cause you problems when it comes to testing your VM code because you now have an implicit link to a UI object in place. Saying that, this is a guideline not a hard and fast rule - if you can't get an alternative approach to work and you end up contorting yourself through all sorts of hoops then just do what you need to do.
However, one approach that I like is to use typed DataTemplates and let the binding engine take care of creating the relevant objects for me. Josh Smith explains it brilliantly in his MSDN article here[^]. Take a look at the section "Applying a View to a ViewModel" to get an understanding of how it all works.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
I don't mean to be rude, but if you are trying to access your view in your VM, then your OOP skills need some refactoring.
To try and be not such an ahole...I think what you are saying is that you have a view that contain another view and they share a VM. The main view we can call V1 - the subordinate we call V2. I'm guessing your V2 is simply not visible. In this case, you want to bind the visibility to a property on your VM (like IsOrdersLoaded or something) and use bool2invis converter. When you command fires, it should simply set this property to true (and your properties setter should call OnPropertyChanged("IsOrdersLoaded")).
On the other hand - if you are trying to "inject" V2 into V1 (or anywhere else in your layout) and it needs to be dynamic (i.e. the command operation knows what V2 should be) - then you should consider basically the same approach, but your V1 (or whatever else) should contain a ContentPresenter that is capable of taking content as a view. This gets a bit trickier when using Commands since they don't return anything - and the one excpetion to the rule (imo) where View Models "know" about views. Essentially your content presenter's content is bound to a property on your view model via a property something like ...
internal FrameworkElement SubContent { get { return this.subContent; } set { this.subContent = value; OnPropertyChanged("SubContent"); } }
and this command of your's simply executes to instantiate your new view and sets that view to this.subContent. Visibility of the content presenter should be implemented as a "is content null" kind of value converter.
Honestly, I personaly hate this approach - I much prefer command repositories that are decoupled from my MV (so the command itself isn't even in the MV) - makes much more sense for testing when I can spin off views from unit tests and have nothing to do with my V1 or MV. If you went this direction, however, you need to add OnCommandExecuted<t> type events to your own command infrastructure to capture the T and propegate back up to the code-behind in the view, which simply sets this.V2Container.Content = T.View type of thing.
I hope that helps a little? If you can be a little more clear about your use case, I can certainly be more helpful.
-dec
|
|
|
|
|
Hi,
I am trying to migrate my silverlight applications from version 3 to version 4. I've been running into this problem. when i try to install silverlight4 tools for visual studio 2010
Visual Studio 2010 or Visual Web Developer Express 2010 or Visual Phone Developer Express 2010 that matches the language version of Silverlight Tools 4 must be installed before installation of Silverlight Tools can continue. Silverlight Tools is available in other languages at http:
I have installed
microsoft visual studio 2010 professional version 10.0.30319.1.RTMRel
Microsoft .net framework version 4.0.30319 RTMRel
please help!!!!!
I've came across an article that provides a workaround for the RC version.
http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http://sorokoletov.com/2010/02/hate-2-wait-silverlight-4-beta-2-vs-2010-rc/
what is the difference between my version and the RC version.
Tiju John
Software Engineer
Noida
|
|
|
|
|
tijujohn83 wrote: my version and the RC version.
The term release candidate (RC) refers to a version with potential to be a final product, ready to release unless fatal bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
|
|
|
|
|
Hi John,
Why are you trying to install Silverlight 4 in a Visual Studio 2010 RC version? The RC candidate doesn't support Silverlight 4. Try installing the Visual Studio 2010 RTM (Final) and then install Silverlight 4 RTM (Final). You will not face any issue.
If any concern, please reply to us.
Don't forget to Click on [Vote] and [Good Answer] on the posts that helped you.
Regards - Kunal Chowdhury | Software Developer | Chennai | India | My Blog | My Tweets | Silverlight Tutorial
|
|
|
|
|
I have 10.0.30319.1.RTMRel version installed, u mean that this is the RC version ??
|
|
|
|
|
|
coudn't find the soulution.
however my issue resolved when i installed the same build version of Visual Studio Premium version.
|
|
|
|
|
Hello all,
I'm Asp.Net developer. And Now I want to learn Silverlight from the beginning , about its tools ( I have installed in VS 2008 ) etc..
anyone knows the best tutorial video sites about Silverlight...?
Thanks
|
|
|
|
|
To learn Silverlight, you might want to take a look here[^].
There is a good videos section in there.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
|
|
|
|
|
Its good site ...thanks
and I want to ask one thing that is it mandatory to learn WCF & WPF concepts before learning Silverlight ?
|
|
|
|
|
vinci007 wrote: learn WCF & WPF concepts before learning Silverlight
It is not at all mandatory to learn WPF concepts.
Basically you need to know a little about web services. So some preliminary WCF concepts should be sufficient.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
|
|
|
|
|
|
Very new to WPF. Trying to keep things simple. Some of the posts I read were a bit confusing - they assume I know something... Wink
I have a ComboBox that works well; display, etc.
Depending on the item selected from the ComboBox (i.e., 3, 7, or 11), I want the respective data displayed in their own text boxes.
The data:
3, Text1, Nbr1
7, Text2, Nbr2
11, Text3, Nbr3
etc.
<pre> <ComboBox Grid.Row="10" Grid.ColumnSpan="2" Width="160" Height="25" Margin="0,0,0,0"
HorizontalContentAlignment="Center" VerticalContentAlignment="Center"
FontSize="12" FontWeight="Bold" IsReadOnly="True"
BorderThickness="2" BorderBrush="Black"
Name="cboNewOption" Background="#FFFFB2" HorizontalAlignment="Right"
<ComboBoxItem>3</ComboBoxItem>
<ComboBoxItem>7</ComboBoxItem>
<ComboBoxItem>11</ComboBoxItem>
<ComboBoxItem>13</ComboBoxItem>
</ComboBox>
<TextBox Grid.Row="10" Grid.Column="3" Grid.ColumnSpan="2" Width="100" Margin="40,0,10,0"
HorizontalAlignment="Left" VerticalAlignment="Center"
HorizontalContentAlignment="Center" VerticalContentAlignment="Center"
FontSize="12" FontWeight="Bold" IsReadOnly="True"
Name="txtOne" Background="#FFFFB2" ></TextBox>
<TextBox Grid.Row="10" Grid.Column="3" Grid.ColumnSpan="2" Width="100" Margin="40,0,10,0"
HorizontalAlignment="Left" VerticalAlignment="Center"
HorizontalContentAlignment="Center" VerticalContentAlignment="Center"
FontSize="12" FontWeight="Bold" IsReadOnly="True"
Name="txtTwo" Background="#FFFFB2" ></TextBox>
</pre>
How do I set up the data/routines so it displays like I want? I would appreciate whatever you care to share!!
Thank you, in advance!
Steve
|
|
|
|
|
Give your combo box a name:
x:Name="myComboBox"
Then bind your textboxes to the combobox using an ElementName type binding.
Text="{Binding ElementName=myComboBox, Path=SelectedItem.PropertyName}"
|
|
|
|
|
Thanks, Jammer.
May I re-iterate? Most posts assume I know something....
I don't know how to set up the data for the textboxes...  I have pretty well mastered the visible (design) portion of XAML. Now trying to understand how to put it together with some functionality (real code). I figured out the code behind for a single button-click maneuver. Trying to bind is where my head hurts... The videos I've seen work from a database that is already created - especially those from MSDN. I just have minimal data I need to tie together...
Please?
Again, thanks, in advance!
Steve
|
|
|
|
|
Gotcha.
Put the data you wish to bind too in a collection like:
public ObservableCollection<string> MyData = new ObservableCollection<string>();
Then bind your combobox to this collection like:
<ComboBox Content={Binding MyData} />
This is assuming that the DataContext is set for XAML to the object that contains your MyData collection.
Make sense?
|
|
|
|
|
So-o-o, modifying my initial post...
The data:
3, Text1, Nbr1
7, Text2, Nbr2
11, Text3, Nbr3
etc.
<ComboBox Name="myComboBox"
Content={Binding MyData}
<ComboBoxItem>3</ComboBoxItem>
<ComboBoxItem>7</ComboBoxItem>
<ComboBoxItem>11</ComboBoxItem>
<ComboBoxItem>13</ComboBoxItem>
</ComboBox>
<TextBox Name="txtOne"
Text="{Binding ElementName=myComboBox,
Path=SelectedItem.PropertyName}"</TextBox>
<TextBox Name="txtTwo"
Text="{Binding ElementName=myComboBox,
Path=SelectedItem.PropertyName}"</TextBox>
<TextBox Name='Etc-etc" />
When I only had one number to display, it was easy:
private void btnGenData_Click(object sender, RoutedEventArgs e)
{
txtNewText.Text = "Text1";
txtNewNbr.Text = "Nbr1";
}
Guess I'm now looking at a case statement...?
public ObservableCollection<string> MyData = new ObservableCollection<string>();
private void btnGenPrime_Click(object sender, RoutedEventArgs e)
{
switch (MyData)
{
case 3:
txtNewText.Text = "Text1";
txtNewNbr.Text = "Nbr1";
break;
case 7:
txtNewText.Text = "Text2";
txtNewNbr.Text = "Nbr2";
break;
case 11:
txtNewText.Text = "Text3";
txtNewNbr.Text = "Nbr3";
break;
}
}
I don't care if it's in XAML or codebehind...it is said you can almost do it all in XAML, right?
Sorry for being dense...
Thanks.
< Steve >
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
