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.
i am building Kinect Application, obviously using WPF.. Now i have a problem with Navigation. I have a Window and others are Pages that will use a Frame in a Window. So the Window has Button to Main to the "Menu" so the Page that contains Menu's is called "MainMenu.xaml"
now when i navigate to the Menu Page , it shows my Menu page ,but the Window Button is not hidden.
So Before i used to have the code to navigate to the "MainMenu.xaml" in the loaded event of the Window so that it directly moved to the Menu, but my Problem is that still behind even if its behind my Kinect Gesture can click or touch the menu's in the "MainMenu.xaml" it looks like they are not out of scope.
When i move from **MainMenu.xaml** to the selected menu page i do it this way
(Application.Current.MainWindow.FindName("_mainFrame") as Frame).Source = new Uri("/Alphabets101/Menu.xaml", UriKind.Relative);
but still you will see that it tries to Access a "MainMenu" even if they are not visible on the screen
Spoted in Daniweb-- Sorry to rant. I hate websites. They are just wierd. They don't behave like normal code.