Data binding

[PB666]

Running into a little snag, ok admittedly, big snag of unfamiliarity here. Im trying to share information between several routines. In one case i want to gather information about files and stuff using standard classes, but once i get this done i want to trash and burn the class stuff.

For this reason the program originates inmain gathers the file info in microsofts standardized file entry gui and then loads the data into a form for review in a listbox control, the problem is that the list box won't update using update or refresh commands. Reading on line it says that updates are privare to the form class from which the object was launch but that you can update by creating a data binding object.

I just wanta know is this a whole nother project in itself requiring a different language?

Edited November 30, 2015 by PB666

[Steel]

I just wanta know is this a whole nother project in itself requiring a different language?

I don't know your specifics, or even what language you're using, but I'm struggling to imagine a problem in this context which would require a change of language to solve

[PB666]

Well the only example ms gives is in XAML. The listbox has data binding entries in the properties, I have no idea how to attach then the filename dat i want presented in the box. This whole data binding stuff is out of the blue for me, there are things that i used to do in vb6 which simply can't be done anymore by the easy route. Now apparently only very specialized controls can do that. I hear chatter about this in the discussion groups but no clearly defined solution is given.

[nohelmet]

You can try asking on a programmer's website (like eg stackoverflow.com). But make sure to indicate which language you're using, show what you've tried, and be more specific in what you're trying to do.

[Yourself]

Well the only example ms gives is in XAML. The listbox has data binding entries in the properties, I have no idea how to attach then the filename dat i want presented in the box. This whole data binding stuff is out of the blue for me, there are things that i used to do in vb6 which simply can't be done anymore by the easy route. Now apparently only very specialized controls can do that. I hear chatter about this in the discussion groups but no clearly defined solution is given.

Well if it's XAML, then you're using C# and WPF. And if that's true, you're in luck, because I deal in both routinely. If it turns out you're actually using WinForms, though, you have my condolences. Judging from your post it sounds like your actual project is in WinForms (the ListBox control in WPF doesn't have any sort of Refresh or Update method and even if it did WPF is designed in a way that you'd never use it) and through your Googling you've accidentally stumbled into answers for WPF which is an entirely different beast (a much more powerful one, in fact).

Anyway, if you need help, you're gonna need to be way more specific. Without details the best I can do is start giving generic non-specific advice or otherwise trying to guess at what your actual problems are and neither of us has that kind of time.

[PB666]

Well if it's XAML, then you're using C# and WPF. And if that's true, you're in luck, because I deal in both routinely. If it turns out you're actually using WinForms, though, you have my condolences. Judging from your post it sounds like your actual project is in WinForms (the ListBox control in WPF doesn't have any sort of Refresh or Update method and even if it did WPF is designed in a way that you'd never use it) and through your Googling you've accidentally stumbled into answers for WPF which is an entirely different beast (a much more powerful one, in fact).

Anyway, if you need help, you're gonna need to be way more specific. Without details the best I can do is start giving generic non-specific advice or otherwise trying to guess at what your actual problems are and neither of us has that kind of time.

I'm going to have tonrestructure the gui, the vs control classes are not optimal and even less well documented.

[Alshain]

Well if it's XAML, then you're using C# and WPF.

Unless he is using Visual Basic and a Windows Store project. Or any combination of the 4. WPF is not exclusive to C# and XAML is not exclusive to WPF.

[PB666]

[quote name='Alshain']Unless he is using Visual Basic and a Windows Store project. Or any combination of the 4. WPF is not exclusive to C# and XAML is not exclusive to WPF.[/QUOTE]

So this is the basics.
Windows forms (from 1987 to present) has a runtime implimentation in C++, C#, VB, VB6 .. ... . . . . , Currently you have class implementation in whatever language you program in partial class as the constructor, and looks like the backdoor is C and C++. Microsoft is not adding new components, but they are maintaining compatibility
-well developed dialog boxes
-Programs that do not need 3D implementation, fixed format texted (like PDF), or Media players.
-Programs that only need GUI or GUI+
-Problems are in the interactions, VB6 gave way to Net, which markedly changed the way classes were handled. The old data sharing has changed many times, for example OLE, gone, its replacement, gone, etc.

WPF - ([URL]https://en.wikipedia.org/wiki/Windows_Presentation_Foundation[/URL]) originally targeted for XML, XAML is employed to simplify the conversion. 2006, Microsoft .NET Framework 3.0,
- Uses generic design, skins can basically replaced most elements of the gui
-Forms, video, graphics, fixed format text, .. . . .
-Problem is Windows 8 introduced WinRT, which has been haldheartedly accepted, this is followed by win10 with a push toward WUP, and WPF is platform specific for the most part.
-Microsoft Expression Interactive Designer, provides a front-end design tool for backend programming via XAML.
-Because of its generic design some features of windows tool box are missing, you have to essentially reprogram the tool to reimpliment the feature (example the multicolumns feature of a list box is missing). Microsoft however has built a database of WPF 'objects' that can be used, if you can find them in the mess that is now called MSDN.

WinRt (Windows Runtime) hit the scene with the genuinely unpopular Windows 8. ([URL="https://en.wikipedia.org/wiki/C%2B%2B/CX"]C++/CX, [/URL]and the [URL="https://en.wikipedia.org/wiki/Managed_code"]managed code[/URL] languages [URL="https://en.wikipedia.org/wiki/C_Sharp_%28programming_language%29"]C#[/URL], [URL="https://en.wikipedia.org/wiki/VB.NET"]VB.NET[/URL], [URL="https://en.wikipedia.org/wiki/JavaScript"]J#[/URL] and [URL="https://en.wikipedia.org/wiki/TypeScript"]TypeScript[/URL]), it is managed using C++, and based on [URL="https://en.wikipedia.org/wiki/Component_Object_Model"]Component Object Model[/URL] (COM) that allows interfacing from multiple languages. UNfortunately there are problems developing code COM because the support is not what it should be.
-Allows code to run on a greater variety of devices.

UWP universal windows platform. ([URL="https://en.wikipedia.org/wiki/C%2B%2B"]C++[/URL], [URL="https://en.wikipedia.org/wiki/C"]C#[/URL], [URL="https://en.wikipedia.org/wiki/VB.NET"]VB.NET[/URL], or [URL="https://en.wikipedia.org/wiki/XAML"]XAML[/URL]) Back door is C++ but supported in C++, VB.NET, C#, and [URL="https://en.wikipedia.org/wiki/JavaScript"]JavaScript[/URL].
-allows developers to create and distribute Universal Windows applications across all [URL="https://en.wikipedia.org/wiki/Microsoft"]Microsoft[/URL] platforms that support the UWP