|
Ok. So, data is displaying correctly just the updates you make to PhotoMetadataList are not getting propogated to PhotoInformationWindow ?
Updates(CollectionChanged/PropertyChange?) are done in PhotoInformationWindow itself or in the Parent Window ?
Well, any DataBinding errors in the Output window ?
If my questions seem relevant then,
How about setting PhotoMetadataList as the DataContext of PhotoInformationWindow instead of accessing it as a StaticResource ? After setting it as the DataContext of PhotoInformationWindow bind ListView's ItemsSource using RelativeSource binding.
I would certainly try attempting this with a WPF ListView (if its a similar model) before making frustrating attempts with the third party control vendor.
|
|
|
|
|
ABitSmart wrote: Ok. So, data is displaying correctly just the updates you make to PhotoMetadataList are not getting propogated to PhotoInformationWindow ?
That is correct -- almost. The first time I bring up the window the ListView is empty. If I turn right around and bring the ListView up again, the ListView is populated. This sounds like my bug somewhere, but it's not obvious.
ABitSmart wrote: Updates(CollectionChanged/PropertyChange?) are done in PhotoInformationWindow itself or in the Parent Window ?
In the PhotoInformationWindow itself. The parent window just passes in the path to the image file. It's up to PhotoInformationWindow itself to obtain the metadata from the image file and set it in the data source.
ABitSmart wrote: I would certainly try attempting this with a WPF ListView (if its a similar model) before making frustrating attempts with the third party control vendor.
I don't know if this forum frowns on revealing 3rd party names (I think a post I made once got deleted because of that), otherwise I would and you'd see that this is a very robust control that developers spend thousands of dollars for (the Professional edition). Its programming model is very close to typical WPF ItemsControl elements, only far richer in the details than the native derivatives.
I don't think any of my problems stem from my 3rd party control as such. For example, in the last couple hours I've made progress by beefing up my own code-behind, and not changing a thing in their recommended XAML. It's just that their sample uses Application.Current as the container for the data (it's simple-minded), and that's the only example I have to go on. They obviously think further details are irrelevant and I can fill in the blanks without even thinking about it.
I think that's why their tech support is not too interested in helping me. They perceived right off the bat that I'm totally unqualified to write a book like Pro WPF in C# 2008 by Matthew MacDonald without even consulting MSDN, if I have to ask the sort of questions that get answered in this forum for example. So I'm here, rather than with the 3rd party tech support. They'll be more than happy to help me out with the details of their control, but are not interested in bringing me up to speed using data binding as such.
|
|
|
|
|
ABitSmart wrote: Another way is setting DataContext of PhotoInformationWindow to the respective PhotoMetadataList.
I didn't know what DataContext was, so looked it up. MSDN: "Represents the main entry point for the LINQ to SQL framework." I'm using neither LINQ nor SQL and don't know beans about either.
|
|
|
|
|
|
Hmmm. That MSDN link doesn't mention a thing about Linq or SQL. I may have to come to grips with it once I fix the bugs in my code behind and see what's left over.
|
|
|
|
|
You need not to define the RelativeSource to the name of your window
Might be this code may work:
Source="{Binding Path=DataContext.PhotoMetadataList, RelativeSource={RelativeSource FindAncestor, AncestorType={x:Type Window}}}"
If doesn't work Please response.
|
|
|
|
|
mittalamit wrote: You need not to define the RelativeSource to the name of your window
Might be this code may work:
Source="{Binding Path=DataContext.PhotoMetadataList, RelativeSource={RelativeSource FindAncestor, AncestorType={x:Type Window}}}"
If doesn't work Please response.
First, as I mentioned, don't think of my container as a WPF Grid. Think of it as a WPF ListView, because that's the correct model for the 3rd party control I'm actually using. But that has nothing to do with your suggestion.
I've already tried something similar to what you suggest but I left DataContext off of the path and omitted FindAncestor, but it didn't work. That's what the 3rd party tech support person suggested. So then I tried your suggestion and that didn't work, either.
I also tried the following, and it didn't work:
Source="{Binding Mode=OneWay, <br />
RelativeSource={RelativeSource AncestorType=local:PhotoInformationWindow}, <br />
Path=DataContext.PhotoMetadataList}"
I'm still out in the cold and have been tempted to drop this 3rd party control and go to the native WPF ListView, but I have a feeling I'd have exactly the same problem. There must be something fundamental that I'm missing, but I'm not a XAML guru, which is why I came to this forum. Tech support of the 3rd party control isn't much help, either.
Maybe the following is a hint to my problem. If PhotoMetadataList is in Application.Current, it almost works with the following XAML:
Source="{Binding Source={x:Static Application.Current}, Path=PhotoMetadataList}"
But there are two things wrong with this:
1. Putting my data source in Application.Current is like using the discredited notion of global data. It would also mean that I'd have to have a way of associating a different path for each window containing my ListView, and that might be challenging to express it in XAML (I sure don't know how to do that off the top of my head).
2. Using the above binding, I still have a couple problems. First, the ListView (or the 3rd party equivalent) doesn't display any data the first time I create the window. But it does on subsequent creations of the window. Second, the ListView never changes its values after the first display, no matter how I change the source. It's acting like a static rather than a dynamic binding.
Added later from another post I made in this thread: "'I didn't know what DataContext was, so looked it up. MSDN: 'Represents the main entry point for the LINQ to SQL framework.' I'm using neither LINQ nor SQL and don't know beans about either." So I guess your suggestion about DataContext is not relevant to my approach. Internally, PhotoMetadataList is of type, List<PhotoMetadata> and PhotoMetadata is a class derived from INotifyPropertyChanged. The data for PhotoMetadata is taken from the image metadata written into photographic image files by digital cameras, and so my data source is not a database, but the metadata in digital image files.
modified on Thursday, June 25, 2009 11:45 AM
|
|
|
|
|
Bindings aren't that complicated if you break them down a bit.
A binding consists of a source and a target, with hooks to look at the
data as it goes from one to the other.
The target is generally simple.
The source seems to give people the most trouble at first.
Read this - then read it again - and again: Binding Sources Overview[^]
(you'll be introduced to the magic DataContext there)
Also read this entire section: Data Binding[^]
(Note: there's a whole bunch of binding examples at the end!)
In your specific example here, you have a target not seeing changes on the source.
The framework cannot possibly know when you've changed something on the source without
some kind of notification. This notification must be provided by you, either through
the INotifyCollectionChanged interface or the INotifyPropertyChanged interface.
You didn't specify what "ignores any data I write to PhotoMetadataList" means.
If you mean adding/deleting/etc items from the list, then no - List<> does not implement
the necessary INotifyCollectionChanged interface so the target won't see those changes.
You should either implement INotifyCollectionChanged on a cusom List<> class or
use a class that does it for you - like ObservableCollection<>
If you meant changes to items in the list, then the type (class) of object the list contains
(PhotoMetadata in your case) needs to implement the INotifyPropertyChanged
interface, and any property of that class that can be or is binded to needs to use the
INotifyPropertyChanged implementation whenever its value changes.
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.freetls.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
Evidently while you were writing your post, you must have been sending good vibrations to me because I caught onto some of the things you write about in this answer and was in the middle of implementing them when your post arrived. This is exactly the kind of information I was soliciting. Of course you're just supplying information, not implementation solutions. It's up to me to figure out what those solutions in my code are, based on your new information.
First of all, I didn't know about INotifyCollectionChanged but conceptually I knew something like that must exist; I just didn't know the name of the class. It's still not clear to me what is meant by "collection changed," but I can look that up.
You mentioned "if you meant..." several times. I meant all of those possibilities. What is in image metadata can change from one image to the next, so sometimes I just need to change a value, but other times I need to remove the row in the ListView altogether, and at other times I need to add a row that hasn't appeared yet. I need to straighten all this out.
What I was doing before was creating an entirely new List each time the photographer selected a new image, and so none of the OnPropertyChanged events were taking place. Likewise, I was creating a new instance of PhotoMetadata for each metadata tag I needed for the new image: again, no notification was taking place.
So far I have improved behavior, but still lots of bugs. Each time I go to a new image, I get an entirely new set of rows duplicating what is already there. I've had this bug show up a hundred times in the last twenty years and it's because I don't clear the ListView each time I have a new set of data. That's entirely different from clearing the data source.
In any case, you've given me some great information and plenty of things to sink my teeth into. Before about an hour ago (when you probably started writing your post) I was gnashing my teeth in thin air!
I'll work all these ideas through in my code and post back when I have further questions, or even have a success story to report -- hopefully the latter. Next time if I have questions, they will probably be more pointed than my previous ones.
|
|
|
|
|
It's really worth taking a bit of time to learn databinding well if you're
doing data-driven apps - saves a lot of frustration! 
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Mark Salsbery wrote: It's really worth taking a bit of time to learn databinding well if you're
doing data-driven apps - saves a lot of frustration!
You're absolutely correct and I knew the day of reconning would be coming months ago. That day is now. But I was able to write 70,000 lines of C#/XAML/WPF code for my application without coming to grips with this central capability of WPF. Now the rubber hits the pavement.
|
|
|
|
|
One thing I forgot to mention in my first answer to your first post is that I still don't have the answer to how to free myself in XAML from the binding to data in Application.Current. I want to bind to data in each window instance. No one has come up with XAML that works to do this, not 3rd party tech support, not anyone on this forum, and certainly not me.
But first things first. Let me get the data in Application.Current working and once I've got that nailed, maybe I can open another thread on this wider requirement.
|
|
|
|
|
Sorry to wade into your discussion at this late stage, but there are a couple of things you should be thinking about. First of all, when you are working with collections of data in WPF it's generally a good idea to use an ObservableCollection rather than a list. Basically ObservableCollection exposes some handy events that WPF uses to add and remove items in the view. If you use this with items that implement INotifyPropertyChanged properly, you have a very powerful binding mechanism that requires minimal coding on your end to keep up to date.
Now, you can declare your DataContext very easily on an individual window. In my Twitter[^] sample, I do this in all of my windows - there's no code behind setting the context, and each window has its own data source. Here's a sample of how to do it in XAML:
<UserControl
x:Class="SongBird.FriendsView"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
Width="420"
Height="380"
xmlns:vm="clr-namespace:SongBird.ViewModel"
xmlns:twitter="clr-namespace:SongBird.Twitter"
>
<UserControl.Resources>
<ObjectDataProvider x:Key="VM" ObjectType="{x:Type vm:PostViewModel}">
<ObjectDataProvider.ConstructorParameters>
<twitter:StatusType>Friends</twitter:StatusType>
</ObjectDataProvider.ConstructorParameters>
</ObjectDataProvider>
</UserControl.Resources>
<Grid DataContext="{Binding Source={StaticResource VM}}" >
<ListBox
Height="380"
ItemsSource="{Binding Mode=TwoWay, Path=Model}"
ItemTemplate="{DynamicResource postItem}"
Padding="3"
ScrollViewer.VerticalScrollBarVisibility="Auto"/>
</Grid>
</UserControl>Here's a breakdown of how this code works. In UserControl.Resources, I create and ObjectDataProvider that instantiates a class called PostViewModel. This class has a constructor with an enumerated parameter, so we set this up in the ObjectDataProvider.ConstructorParameters portion. Now, as you can see, we've called this ObjectDataProvider VM. This enables us to set the DataContext in the Grid, by binding it to the resource called VM. Have a download of Songbird[^], and see how this hands together.
"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
|
|
|
|
|
Thanks for your post that addresses my original issue. You caught me in the middle of getting stuff to work with the original Application.Current location. Maybe when I fully investigate your suggestion, I'll be backing out a lot of that code. But I have to take my current direction to its completion first (it's going to take another hour or two). Optimization can come a little later.
But I'll definitely be looking into this ObservableCollection class. That in fact is what one of the 3rd party tutorials recommended developers use, but then when I got involved with their tech support, she was using a regular old List, so that's what I reverted to. It's got me involved in developing gobs of code, but my preliminary results are that it works, so I'd like to carry it through to completion before I change directions and do it "the right way."
|
|
|
|
|
In addition to my other reply...
The magic DataContext:
Any time you have a binding that doesn't explicitly set a source (be it a direct
source, RelativeSource, etc), then an attempt is made to bind to the object set
on the DataContext property of the target element.
If there's a DataContext set and the Path of the binding is not found on that object,
then the binding silently fails (almost silently - you'll get a handy warning in the
debugger output window).
If no DataContext is set on the element, then the system walks up the tree and tries the next
(parent) element's DataContext. This is repeated to the root element. If a source
still wasn't found after all that, the binding will fail and you'll get the message in the
debugger output window.
This allows you to set the DataContext at an appropriate place in the tree so it is
accessible by more than a single element if necessary - very flexible.
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I'm not sure this post is relevant to what I'm doing since I'm using neither Linq nor SQL. Is this thinking on my part correct?
|
|
|
|
|
You looked at the wrong DataContext. The DataContext we're referring to
is a property of every UIElement.
I think it's very relevant - you'll probably want to set the DataContext to
your list object instances somewhere in your visual tree so you don't have to
use a "global" Application object as your binding source (which is just silly
except for data that needs to be at application scope
From what I gathered, you want data at the scope of each Window (different set of data
for each window, so set the DataContext to that data on the Window or any appropriate
child element of the window).
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Mark Salsbery wrote: You looked at the wrong DataContext.
I do stuff like that all the time. I bring up a class in MSDN and start reading and think, what is this nonsense? Then I look where the article stems from and its Visual Basic or something!
|
|
|
|
|
I've got it all working now, exactly the way I want it. But things got solved in unexpected ways. I couldn't support updating the ListView in XAML if I wanted to replace the values in it multiple times in the same instance of the containing window. I had to initially set ItemsSource to null and Clear() the ListView, and only after setting all the values in the ItemsSource could I bind the data to the control through a simple assignment statement in code-behind.
This solved all my problems! so Mark Salsbery was on the right track when he advised me not to use XAML for the data binding. Maybe there's a way of assigning it in XAML but in this case, I don't know what it is. And where XAML is supposed to be so much more concise than code behind, in this case it is horrendously more complicated! I don't have to worry about "RelativeSource", "AncestorType", "Path", or any of that other BS in XAML. I just prepare my data source and do a one line assignment when it's done, like this:
metadataGrid.ItemsSource = PhotoMetadataList;
Voila! Mission accomplished! What could be simpler? PhotoMetaDataList is local to the window instance and I don't have to worry about binding to something in Application.Current, which was about as ugly as you can get. Each window instance has its own data source and everything works perfectly!
My apologies for not following up on all the posters who gave me fine suggestions, but as the saying goes, if it ain't broken, don't fix it! Thre's valuable suggestions in this thread that will come in handy in the future. And BTW, my problems had absolutely nothing to do with the 3rd party control I'm using, which is just about the spiffiest control in the universe. All my problems were with understanding the basics of pure WPF data binding. No wonder the 3rd party tech support was impatient with me.
Look up Matthew MacDonald's suggestion on page 608 for a replacement to the Windows Forms' DataGridView to find out what control I'm actually using. Unfortunately the book is out of date in suggesting that you can get the standard edition for free. However, it was correct information when I bought the book and I jumped at the chance to get it free! It will currently set you back $300, and thousands if you want the Professional edition. They must have had an army putting this thing together.
modified on Thursday, June 25, 2009 6:28 PM
|
|
|
|
|
Howdy Fellow's:
I've been searching information about WPF's transitions on the web.
I'm trying to develop a "slide" transition to make my appllication look smother, but I keep encoutering issue with all the examples I've found on the net.
in the transition, the image flicks in the borders. I don't want this to happen, but all the examples seem to have to same problem.
I also tried to run my applicattion on a faster and newer machine, but the result was the same. Could it be that windows XP handles the bitmap effects and transitions with software instead of using the hardware?
Thanks for the help.
Cheers
|
|
|
|
|
fgimenez wrote: Could it be that windows XP handles the bitmap effects and transitions with software instead of using the hardware?
No. Windows XP handles all our transitions just fine. Do you have a good video card ? Are your drivers up to date ? What are you doing exactly ?
Christian Graus
Driven to the arms of OSX by Vista.
"! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
I can do things with my brain that I can't even google. I can flex the front part of my brain instantly anytime I want. It can be exhausting and it even causes me vision problems for some reason. - CaptainSeeSharp
|
|
|
|
|
I'm new to all the wpf developing so I'm building a very simple animation. There is a rectangule with a gradient on the screen and I move it from left to right. That's all.
The size of the rectangule remains the same, only it's position changes.
I'm using the Expression Blend to create the animation and the see the XAML code. The animation looks generated is this one:
<Storyboard x:Key="TextAnimation">
<ColorAnimationUsingKeyFrames BeginTime="00:00:00" Storyboard.TargetName="{x:Null}" Storyboard.TargetProperty="(Panel.Background).(SolidColorBrush.Color)">
<SplineColorKeyFrame KeyTime="00:00:02" Value="#FFFF0000"/>
</ColorAnimationUsingKeyFrames>
</Storyboard>
<Storyboard x:Key="testAnimation">
<DoubleAnimationUsingKeyFrames BeginTime="00:00:00" Storyboard.TargetName="rectangle" Storyboard.TargetProperty="(UIElement.RenderTransform).(TransformGroup.Children)[3].(TranslateTransform.X)">
<SplineDoubleKeyFrame KeyTime="00:00:00" Value="0" KeySpline="0,0,1,1"/>
<SplineDoubleKeyFrame KeyTime="00:00:01" Value="340" KeySpline="0,0,1,1"/>
</DoubleAnimationUsingKeyFrames>
<DoubleAnimationUsingKeyFrames BeginTime="00:00:00" Storyboard.TargetName="rectangle" Storyboard.TargetProperty="(UIElement.RenderTransform).(TransformGroup.Children)[3].(TranslateTransform.Y)">
<SplineDoubleKeyFrame KeyTime="00:00:00" Value="0" KeySpline="0,0,1,1"/>
<SplineDoubleKeyFrame KeyTime="00:00:01" Value="225" KeySpline="0,0,1,1"/>
</DoubleAnimationUsingKeyFrames>
</Storyboard>
As you can see, the propertys being changed are the X and Y positions.
The problem is that as the rectangule moves throught the screen, the borders flick( you can see how they are been drawn very quickly) and this gives a very shaby effect.
Is there any other way to do this? All the examples and libreries I've found have the same problem.
Again, thanks!
Cheers
|
|
|
|
|
I am beginner, trying to understand Silverlight2Chat application. I followed instructions on Build a Silverlight 2 Web Chat Application[^]to create Silverlight2Chat project in visual studio. My solution explorer show the project exactly as in the picture on the above link.
In the web.config file I changed the connection string as follows:
<add name="LinqChatConnectionString" connectionString="Data Source=[STUDYMG];Initial Catalog=LinqChat;Integrated Security=True;" providerName="System.Data.SqlClient"/>
I created two records in dboUsers, and one record in dbo.Room tables.
Now to see how it works, I right click on Silverlight2Chat in the solution explorer in Visual Studio, then choose 'View in Browser', It shows me the login page, I enter credentials and then click on login button, but nothing happens.
I also did 'View in Browser' for Silverlight2ChatTestPage.html, which also shows me the login page, but nothing happens when I enter credentials, and click on login button.
What am I missing?
|
|
|
|
|
You need to actually run the app instead of just viewing it in a browser.
Try choosing Debug/Start new instance or hit the F5 key.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I did try running the app with F5 key and ctrl+F5. but still nothing happens when I click Login button after entering credentials.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
