![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
3:34pm - Geez, I was all set to go to the Library today to work and I got a tweet from them saying they'd be closed today due to heating problems, so I had to hike all the way through the snow to the McDonald's. Ahh well.
I'm going to start off today by trying again to find some decent documentation on XAML and Data Binding in WPF Appliations. I almost got it working last night by poking elements around but I never really knew what I was doing, and I don't like that. Programming is typically an exact science, and I feel that's how it should be.
5:31pm - I've been at it a couple hours now and I've found some better documentation here: https://docs.microsoft.com/en-us/dotnet/framework/wpf/advanced/xaml-overview-wpf
But it's not perfect. I can't just do like with C# and put in a class and get a great bit of info with use cases and examples and everything. Still, hopefully with more reading I'll understand what I'm doing.
I also got into a deep argument about my views on Intellectual Property laws which took up a lot of my attention, but it seems to be over now.
6:25pm - Geez but this text is dense. I'm still pouring over it but it's going slow.
6:42pm - Oh I think I've found some good reference at last. Here's the thing I'm actually working with: https://docs.microsoft.com/en-us/dotnet/api/system.windows.controls.treeview?view=netframework-4.7.1
7:36pm - Well one thing I've been able to confirm so far is that I was right about the data binding only working with properties. So there's that at least.
7:39pm - I just tried making a change in the XAML to see if it would fix or break my program. It did neither. I'm not getting any errors and the functionality is still the same, even though I rebuilt it.
7:50pm - Huh, I got it working, sort of, though I barely understand how. Basically, I switched out the Nodes property of the dialogue for the dialogue itself and it created a blank tree root followed by the three nodes.
But now that I'm starting to understand how this works I'm more sure than ever that I'm doing it wrong. I shouldn't be trying to force my Dialogue structure into a TreeView, I should be translating it into a different data format in the application and saving it differently.
At least, I think so.
So basically I need to make an internal format for the editor to use for representing the dialogue.
I'm thinking something like, each dialogue node is a new branch on the tree, and options have two branches.
Yeah that makes sense given the internal structure!
Okay let's make a class for that...
8:49pm - Alright! It works! Nowmy brain's a bit fried though, so I think I should take a break.
9:27pm - I tried to take a break but my brain just gave me the runaround. Instead I'm going to head home and have something to eat with Rob, maybe work some more after but probably just relax and play until bed.
I'm going to start off today by trying again to find some decent documentation on XAML and Data Binding in WPF Appliations. I almost got it working last night by poking elements around but I never really knew what I was doing, and I don't like that. Programming is typically an exact science, and I feel that's how it should be.
5:31pm - I've been at it a couple hours now and I've found some better documentation here: https://docs.microsoft.com/en-us/dotnet/framework/wpf/advanced/xaml-overview-wpf
But it's not perfect. I can't just do like with C# and put in a class and get a great bit of info with use cases and examples and everything. Still, hopefully with more reading I'll understand what I'm doing.
I also got into a deep argument about my views on Intellectual Property laws which took up a lot of my attention, but it seems to be over now.
6:25pm - Geez but this text is dense. I'm still pouring over it but it's going slow.
6:42pm - Oh I think I've found some good reference at last. Here's the thing I'm actually working with: https://docs.microsoft.com/en-us/dotnet/api/system.windows.controls.treeview?view=netframework-4.7.1
7:36pm - Well one thing I've been able to confirm so far is that I was right about the data binding only working with properties. So there's that at least.
7:39pm - I just tried making a change in the XAML to see if it would fix or break my program. It did neither. I'm not getting any errors and the functionality is still the same, even though I rebuilt it.
7:50pm - Huh, I got it working, sort of, though I barely understand how. Basically, I switched out the Nodes property of the dialogue for the dialogue itself and it created a blank tree root followed by the three nodes.
But now that I'm starting to understand how this works I'm more sure than ever that I'm doing it wrong. I shouldn't be trying to force my Dialogue structure into a TreeView, I should be translating it into a different data format in the application and saving it differently.
At least, I think so.
So basically I need to make an internal format for the editor to use for representing the dialogue.
I'm thinking something like, each dialogue node is a new branch on the tree, and options have two branches.
Yeah that makes sense given the internal structure!
Okay let's make a class for that...
8:49pm - Alright! It works! Nowmy brain's a bit fried though, so I think I should take a break.
9:27pm - I tried to take a break but my brain just gave me the runaround. Instead I'm going to head home and have something to eat with Rob, maybe work some more after but probably just relax and play until bed.
