Request For Community Programmers
-
-
Afraid I dont follow. Source? Misleading?
Thanks for the kind offer MorteSil, I may take you up on it if I get really stuck
No worries, just make sure you expose everything you want to bind to as a public property in your code behind (.XAML.cs), and don’t use any List objects (Use ObservableCollection instead). Once you figure out the intricacies of binding, WPF is pretty straight forward, as long as you have a general understanding of XAML…
-
Still working on this Blu? I see you updated your Git a few days ago.
Minor suggestion for your XAML:``` Use a StackPanel inside another Grid for your layout. Then you don't have to set your Margins or Alignments independently for every control. You can nest StackPanels and set Orientation=Horizontal for items on the same line:
Setting up Column and/or Row Definitions allows you to segment the grid into specific areas, setting up a true "Grid" inside your item. Setting the Height or Width on 1 column or Row will adjust the size and force the other one to take up the remaining available screen space. Use Grid.Column or Grid.Row to assign the element to a certain area of the container grid. More Content in the second grid area.
One big advantage to WPF in using lots and lots of grids, is you can cut/paste an entire grid to move segments around instead of adjusting individual margin elements for each control in a group. I tend to wrap almost everything in a grid, at least everything that needs to be grouped somehow.
-
Still working on it. Or at least still intending to. This is basically the busy week of the year for my current job. Havent turned the computer on much, havent had time.
Without knowing how grids work, is this a good thing? Coming from web design, where we started out using tables for layout and moved deliberately away from that, and towards using margins/padding instead.
Binding is confusing me. The idea is straightforward enough, the implementation not so much. And that for just a single line string…
-
This post is deleted! -
Not having done much GUI programming on the windows platform myself, but have you looked into the python / qt combo or electron?
Electron seems to be all the new hotness today, but it’s BIG. Python/QT will give you nice cross-platform support at a lower memory footprint and most likely faster prototyping / turnaround times.
All the best, Uwe
-
This post is deleted! -
This post is deleted! -
You know, I knew that, but didnt even stop to consider users might still be using 32 bit. Sigh. Thanks for the catch.
-
This post is deleted! -
Well, the latest commit can now use the Extract function of 3ddbbuilder, so thats something. I guess Ill want to dip my toes into multithreading now too. It locks up for several minutes while thats happening, and I guess I need a way to display the output from the program to the user.
Changed it to prefer 64 bit over 32 bit, if both are available. Apparently Visual Studio defaults to preferring 32 bit.
Not seeing it as being a great alternative to just using the command line, to be honest, but its a good exercise so far.
-
One big advantage to WPF in using lots and lots of grids, is you can cut/paste an entire grid to move segments around instead of adjusting individual margin elements for each control in a group. I tend to wrap almost everything in a grid, at least everything that needs to be grouped somehow.
The issue with WPF is that it’s been obsoleted by MSFT and only works on some platforms. Apologies for the bikeshed-level comment
How much far are you into the project? Got any low-hanging fruit for people not familiar with the codebase?
-
was that meant for MorteSil’s thread, LODEditor-Replacement? If so, it is sounding promisingly close to release. Hopefully when that happens, it also becomes open source (I can hope!).
If it was meant for here, then its all low hanging fruit here, and very little actual ‘codebase’ as its just a GUI wrapper for the existing CLI tool, 3ddbbuilder.exe. Probably if an actual programmer was working on it, it would be done by now. Im just an amateur Turns out having to stop what you are doing every line to google how to use language features really slows you down. Who knew?!
I didnt know that WPF was obsoleted already. Which platforms does it not work on?
-
This post is deleted! -
This post is deleted! -
Sounds like WPF or WinForms is where I should be for this, then. I suspect that for the forseeable future, managed code is for the best, for me.
-
This post is deleted! -
Guessing there’s probably more Falcon users on XP than on Windows 8 and 10. Does WPF work on those platforms?
Starting already to see the drawbacks to the mega monolithic object design. Google says I should have “MVVM” design instead. Probably going to skip that for this. For the immediate future anyway.
-
This post is deleted! -
Yeah, more commits have happened. 12 of them, in the last week. Only issue so far is inelegance, and repeated code. Not a functional issue so much as looking at the mess Ive made so far. So far, it works. I understand there’s benefit to making something that works instead of getting bogged down in planning, too.