|
Your XAML declares a StaticResource for the binding, which does not exist at load time; see the discussion here[^].
Use the best guess
|
|
|
|
|
Hi Guys, I have a nice working app in Windows Forms. I am attempting to port it to WPF and I am stuck with selecting a row and getting a value from one of the columns.
Apologies for the long code:
In Windows Forms App I do the below:
private void lstFiles_DoubleClick(object sender, EventArgs e)
{
if (lstFiles.SelectedItems.Count != 0)
{
string file = lstFiles.SelectedItems[0].Text;
openFormGeneral(file);
}
}
In WPF .xaml:
<ListView x:Name="lstFile" Height="357" HorizontalAlignment="Left" Margin="18,144,0,0" VerticalAlignment="Top" Width="550"
ItemsSource="{Binding songDetails}"
MouseDoubleClick="lstFile_MouseDoubleClick"
IsSynchronizedWithCurrentItem="True"
SelectedItem="{Binding Path=SelectedSong}">
<ListView.View>
<GridView>
<GridViewColumn CellTemplate="{StaticResource FirstCell}" Width="30" />
<GridViewColumn Header="File Name" DisplayMemberBinding="{Binding FileName}" />
<GridViewColumn Header="Title" DisplayMemberBinding="{Binding Title}" />
<GridViewColumn Header="Artist" DisplayMemberBinding="{Binding Artist}" />
<GridViewColumn Header="Album" DisplayMemberBinding="{Binding Album}" />
<GridViewColumn Header="Set" DisplayMemberBinding="{Binding Set}" />
<GridViewColumn Header="Genre" DisplayMemberBinding="{Binding Genre}" />
<GridViewColumn Header="Language" DisplayMemberBinding="{Binding Language}" />
<GridViewColumn Header="File Path" DisplayMemberBinding="{Binding FilePath}" />
</GridView>
</ListView.View>
</ListView>
I Populate the ListView as follows:
public class songDetails
{
public string Title { get; set; }
public string Artist { get; set; }
public string Track { get; set; }
public string Set { get; set; }
public string Album { get; set; }
public string Genre { get; set; }
public string Language { get; set; }
public string FileName { get; set; }
public string FilePath { get; set; }
}
public IList<songDetails> songDetail { get; set; }
public void AddFile(ID3Info File)
{
lstFile.Items.Add(new
{
FileName = File.FileName,
Artist = File.ID3v2Info.GetTextFrame("TPE1"),
Title = File.ID3v2Info.GetTextFrame("TIT2"),
Track = File.ID3v2Info.GetTextFrame("TRCK"),
Album = File.ID3v2Info.GetTextFrame("TALB"),
Genre = File.ID3v2Info.GetTextFrame("TCON"),
Language = File.ID3v2Info.GetTextFrame("TLAN"),
FilePath = File.FilePath
});
artist = File.ID3v2Info.GetTextFrame("TPE1");
track = File.ID3v2Info.GetTextFrame("TRCK");
set = File.ID3v2Info.GetTextFrame("TPOS");
title = File.ID3v2Info.GetTextFrame("TIT2");
album = File.ID3v2Info.GetTextFrame("TALB");
genre = File.ID3v2Info.GetTextFrame("TCON");
language = File.ID3v2Info.GetTextFrame("TLAN");
InitializeComponent();
this.DataContext = this;
}
How do I access the FilePath from the ListView with MouseDoubleClick event? Thanks in advance
Excellence is doing ordinary things extraordinarily well.
|
|
|
|
|
You bound the SelectedSong so SelecedSong.FilePath should contain your information provided you double clicked on a row so test for null!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hi Mycroft. Thanks for the reply. This may sound stupid but how do I do that? I have tried numerous things and nothing works or I get a very long string of all the items in the object returned. 
Excellence is doing ordinary things extraordinarily well.
|
|
|
|
|
Wherever this property (SelectedSong) is declared is where you object is
SelectedItem="{Binding Path=SelectedSong}"
In your doubleclick event you need to reference the SelectedSong
string sPath = class.SelectedSong.FileName
If you are using MVVM then class = your viewmodel.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hi Mycroft. Apologies for taking this long to reply. Been a little busy. I tried the below and I get the SelectedItem but it does not get passed to "theSong". Am I going crazy or am I just missing the point completely here?
private void lstFile_MouseDoubleClick(object sender, MouseButtonEventArgs e)
{
try
{
var theSong = this.lstFile.SelectedItem as songDetails;
if (theSong != null)
{
string filePath = theSong.FilePath;
}
}
catch (Exception ex)
{
System.Windows.Forms.MessageBox.Show(ex.Message.ToString());
}
}
Excellence is doing ordinary things extraordinarily well.
|
|
|
|
|
You are missing the point completely  you are thinking like winforms, stop.
You should not/never be referencing the controls in the view but the collection it is bound to in you viewmodel or code behind. Stop trying to get the info from the list control and look in the SelectedSong property where you have bound the SelectedItem to!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I bound the SelectedSong to a textBox and it works now. Not the cleanest way of doing things but it works.
Thanks
Excellence is doing ordinary things extraordinarily well.
modified 3-Apr-13 17:25pm.
|
|
|
|
|
I have a requirement to display a collection of sections, each section needs needs to show a few combos, a couple of large textboxes, probably a grid and support drag and drop files.
I was thinking of using a listbox of user controls, the user control would be an expander (telerik) with all the bits in it.
My issues is how to put together the collection/control/viewmodel. Building the VM that accepts a SelectedSection and loads the static lists for the combos etc is not a problem. I can then bind the view datacontext to the viewmodel.
I would then use the UC as the datatemplate of the listbox. How do I bind the SectionsList collection to the listbox and the UC data template.
Are there any good examples of this!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
You should not expose a collection of user controls, or any control for that matter. Define a class called Section (whatever the hell that is) that contains all the data for a section. Then define an ObservableCollection<Section> and expose that from your VM and bind it to the ListBox ItemsSource. Then simply define the ItemTemplate for the ListBox and you are good to go.
Your ItemTemplate would define the controls and their layout and bind them to the Section object which will be the ListBoxItem content.
|
|
|
|
|
This is fine for a standard list of items, I need a UC and a VM for each item in the list.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Not quite sure what you mean. When you say "UC", you should be using a DataTemplate that defines that "UC". When you say "VM" for each item, that would be your Section object. In fact, if you want to argue semantics, your DataTemplate could just be your user control. It would inherit the DataContext.
|
|
|
|
|
My section object is a Model, basically a POCO with onpropertychanged events.
Main View has an observable collection of Sections, these are to be displayed in a list/tree container that needs to contain a set of controls (UC) for the management of the section contents.
UC UserControl will be a set of controls required for each section (datatemplate), including combos and a drag and drop target, an expander and some large textboxes.
The UC will need bind to a ViewModel to manage the Section interactions. How to achieve the binding is my problem!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Sounds like we are saying pretty much the same thing, but you don't like my semantics lol  .
Ok, so Section is a model an observable POCO. Check.
UC UserControl = DataTemplate for an item.
Here is where you are arguing semantics. You say you need a VM for binding to the UC UserControl / DataTemplate... I'm agreeing with you, but saying it needs to be part of Section. Then you can bind as normal.
If you still want to argue semantics, you can do something like:
class Section
{
public Prop1
public Prop2
public Prop3
ViewModelBase ViewModel;
}
and then in your XAML, you could either do:
<MyUserControl /> and the DataContext will point to the Section object and you can reference the VM from there using Path=ViewModel.Blah;
Or if you want to be pedantic, you can do:
<MyUserControl DataContext="{Binding ViewModel}" />
and the MyUserControl will only get the ViewModel rather then the whole Section object. Either way works, but the VM / sub object / whatever you want to call it, has to be part of Section since that is what you are binding to.
If you don't want to do that for whatever reason, the only other thing you can probably do if you want to get all tricky is use DataTemplates to instantiate the VMs based on something in the Section object, but that would require modifying how the item creation works and the end result will be that you could have just stuck your "VM" into the section object and achieved the same thing and kept a few more hairs .
|
|
|
|
|
Ah I think I see where I am diverging, my Section object is part of the ViewModel whereas your Section object would contain the ViewModel.
So the collection of Section objects should include the POCO AND the VM functionality, in my architecture this is then a collection of VMs which becomes the DataContext for CollectionControl.
Have a bunch of 5s - thank you!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
You got it .
Calling something a ViewModel is just arguing semantics. Its just some random (generally observable) object that the DataContext points to. In the MVVM world its just some random (always observable) object that derives from "ViewModelBase" or something similiar.
The VM that owns the listbox would have the ObservableCollection<Section>. Section would then contain the VM / whatever for the UserControl.
|
|
|
|
|
Sorted the binding, now to make the dammed thing sit up and beg! thanks
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I created a user control and I want to display it as the content of a combobox.
I tried to wire up the user control inside the combo, but I see nothing, and the user control's view model isn't being instantiated.
The combo:
<ComboBox Grid.Column="1"
TabIndex="0"
Style="{StaticResource ComboBoxStyle}"
HorizontalAlignment="Left"
Width="450">
<ComboBox.ItemTemplate>
<DataTemplate>
<views:JobListView/>
</DataTemplate>
</ComboBox.ItemTemplate>
</ComboBox>
JobListView is a custom tree with search conntrols. How do I make the ComboBox use the JobListView as its content? Right now, when I run it and open the combo, nothing appears.
If it's not broken, fix it until it is
|
|
|
|
|
I am not a pro so this may not work. Set the ComboBox Datasource to the JobListView.(Or the View Model)
Hope this helps.
Edit Changed the subject title so others might help.
Frazzle the name say's it all
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
John F. Woods
|
|
|
|
|
There is no data to bind to. The data for the control is retreived from inside the control, not bound to the combo.
I'm trying to use the combobox to simple pop open the user conrrol
If it's not broken, fix it until it is
|
|
|
|
|
Then it seems that the Usercontrol should have contained a TextBox A Button with a drop down arrow and the ListView with visability set to collapsed. Then on the Button click open the ListView.
Frazzle the name say's it all
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
John F. Woods
|
|
|
|
|
Why would it show anything? Think about what your XAML is doing. You set the ComboBox.ItemTemplate to show a views:JobListView. You just said "I want to render each item (in both the edit box and the drop down list) as a views:JobListView". So, if you have 10 items, you are going to get 10 views:JobListView plus another one in the edit box. Probably not what you meant .
As I have mentioned to you in the past, you really need to aquire a tool that will allow you to dump out control templates, so you understand how they are put together so you can do these types of mods as you get more advanced.
I would highly recommend you install Expression Blend Preview since its now free and allows you to dump out control templates easily as well as modify them visually.
Also, in your response to the other guy, you said you didn't set the combo box ItemsSource to anything and wanted the JobListView to retrieve everything. That won't work on a conceptual level. How is the edit box in the combo box going to display the selected item when it knows nothing about the collection?
You need to have the VM that owns the combo box own the collection and set the combo box ItemsSource to it. The edit box will show the selected item and the popup view will render as your JobListView.
I'm not going to post the ComboBox control template here since its quite large (200+ lines of XAML), but I did dump it out for discussion purposes.
There isn't an easy way to style the drop down list because its essentially an ItemsPresenter and doesn't have any built in templates for that.
You *might* be able to wait for the combo box template to be applied and then find the "DropDownScrollViewer" control by name and replace its content with your control. I haven't tried this, so its possible it won't work. If I was doing this task, I'd probably try it first though. Otherwise, it looks like you are going to have to dump out the control template and replace the ItemsPresenter with your joblistview.
|
|
|
|
|
Hey all!
Does anyone know of a good, functional Windows 8 theme for WPF? I'd like something like GitHub's desktop GUI theme.
Thanks!
|
|
|
|
|
You could use MahApps; http://mahapps.com/MahApps.Metro/[^]
"As beings of finite lifespan, our contributions to the sum of human knowledge is one of the greatest endeavors we can undertake and one of the defining characteristics of humanity itself"
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
