You are trying to replace an Event (AutoGeneratingColumn) with an object?
I think you mean and auto generated column with a customised datagridcolumn, therefore replacing one object with the same type of object just custom built. I would think this would be reasonable, be prepared for the column collection to object but I don't see how.
I would locate the column in the collection and customise it in place rather than replacing it.
Caveat - I have never done this either!
Never underestimate the power of human stupidity
Ah that makes more sense, I would still try and change the existing columns properties rather than replacing it.
In one scenario I know the content of the first 4 columns and change the individual formats in the afterautocolumngenerated event (the event name maybe wrong ). The remainder are from a pivot query and are not formatted.
Never underestimate the power of human stupidity
But "Enterprisy people" like web for mostly 2 reason:
1. it's "multiplatform" (you know it work on the 2% of mac and 05% of linux, and on iPad and smart phone, which are more common)
2. it's non brainer deploy once in on a webserver it's out there for every one, and that's the latest version!
For the update of desktop always a problem (you see, in some entreprisy environment, user CAN'T install anything, including update, the likely mandatory .NET framework, etc.) click once does a relatively good job in most case for .NET app and, on WIndows 8, metro app update seemlessly! (although there are curretnly some nasty limitation for .NET business app, like crippled file access, nosql access, this can be handled on the server side as, thankfully, WCF work in metro app!!)
Ok that´s all.
What I want do now is this:
From the Mainwindow.xaml for the button click of "button" I want send 3 path (variables) for the "image" "buttonlink1" and "Buttonlink2" situated in Window1.xaml.
The idea is to have many buttons in the Mainwindow.xaml and each one represent a fix for a software error, this buttons will keep different data. In the "image" I have to send the path of a .jpg that will show an error dialog box. In the "buttonlink1" I have to send the path of a .bat fix that will fix the issue. In the "buttonlink2" I have to send the path of a .bat that will remotely resolve the issue.
So my question is: How i can send this 3 variables (path) from Mainwindow.xaml to window1.xaml? and how "image" "buttonlink1" "buttonlink2" will read it and execute it?
Thank you in advance for your help, I am sorry for eventual grammar errors. If something is not clear, just let me know.
Maybe data flow isn't the right question, maybe application organization describes my quandary a little better. Here is what I am trying to do and could stand a bit of help getting there.
The app I am creating basically sits between two pieces of equipment and provides data management and communications management between the two. On one side is a piece of equipment that views its world as dealing with a single entity that provides a go no-go result. The other side is a piece of gear that can have of measurements to keep up with. Essentially all this data must be gathered, analyzed and a go no-go be sent. One side expects a TCP/IP server the other is a GPIB bus master. The comms are handled as that was the easy part.
Where I am a bit stuck is gluing all this together. The GPIB code and the logic to handle the data is done and runs as a task. The TCP/IP server is done and it runs as a task. I need to add one more piece of logic to handle the decision making plus have a UI that needs to be kept up to date.
Right now I have test programs for testing the comms etc. There I have the UI registering event handlers to get notifications of something happening. I use EventWaitHandles to notify the thin interface layers that sit about the comms. All works great! But when I put all this together..............???
I want areas of functionality as loosely coupled as I can for better reuse. In the UNIX world this is simple but in this world, not so much. My inclination is let the MainWindow code behind kick off each task and the tasks expose public methods or permit registering event handlers. But something about this doesn't feel right. In the UNIX world I would have started POSIX threads to handle each functional area and used message queues to facilitate data flow. That way synchronous functionality is grouped and asynchronous is grouped. But the Windows world doesn't seem to operate that way. What I have seen is all the classes/objects are gathered into a single app and there is a lots of "peeking" over the wall to do things which I think tends to make things very tightly coupled.
After a quick view, I see two things:
After calling the ctor of ViewModel, there will be Ivan, Stefan, Maria and Michael in the Persons collection. After calling ViewModel.Add() there will be only Maria and Michael, because you create a new collection.
class Person needs to implement INotifyPropertyChanged and after changing a property it has to call the PropertyChangedEvent.
Hope it helps
Last Visit: 31-Dec-99 19:00 Last Update: 23-Jan-18 2:32