|
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.
Suggestions?
TIA,
Doug
|
|
|
|
|
|
Explain why the method works so crooked add to the collection and display DataGrid.Ispolzuyu binding in XAML
<Window x:Class="bild.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:sys="clr-namespace:bild"
Title="MainWindow" Height="519" Width="525">
<Window.Resources>
<sys:ViewModel x:Key="DataSource"/>
</Window.Resources>
<Grid>
<ListBox ItemsSource="{Binding Source={StaticResource DataSource}, Path=Persons}"
DisplayMemberPath="Name"
HorizontalAlignment="Left" Margin="49,21,0,201" Name="listBox1" Width="425" />
<Grid DataContext="{Binding Source={StaticResource DataSource}}" Height="149" HorizontalAlignment="Left" Margin="49,134,0,0" Name="grid1" VerticalAlignment="Top" Width="425">
<DataGrid
ItemsSource="{Binding Source={StaticResource DataSource}, Path=Persons}"
AutoGenerateColumns="False" Height="143" HorizontalAlignment="Left" Margin="36,0,0,0" Name="dataGrid1" VerticalAlignment="Top" Width="383" >
<DataGrid.Columns>
<DataGridTextColumn Binding="{Binding Age}" Header="Age" ></DataGridTextColumn>
</DataGrid.Columns>
</DataGrid>
</Grid>
<Button Content="Button" Height="23" HorizontalAlignment="Left" Margin="296,290,0,0" Name="button1" VerticalAlignment="Top" Width="75" Click="button1_Click" />
</Grid>
</Window>
using System;
using System.Collections.Generic;
using System.Collections.ObjectModel;
using System.Linq;
using System.Text;
using System.Windows;
using System.Windows.Controls;
using System.Windows.Data;
using System.Windows.Documents;
using System.Windows.Input;
using System.Windows.Media;
using System.Windows.Media.Imaging;
using System.Windows.Navigation;
using System.Windows.Shapes;
namespace bild
{
public partial class MainWindow : Window
{
public MainWindow()
{
InitializeComponent();
}
private void button1_Click(object sender, RoutedEventArgs e)
{
ViewModel r = new ViewModel();
r.ad();
dataGrid1.ItemsSource = r.Persons;
}
}
public class ViewModel
{
public ViewModel()
{
this.Persons = new ObservableCollection<Person>();
this.Persons.Add(new Person("Ivan", 23));
this.Persons.Add(new Person("Stefan", 34));
this.Persons.Add(new Person("Maria", 16));
this.Persons.Add(new Person("Michael", 78));
}
public void ad()
{
this.Persons = new ObservableCollection<Person>();
this.Persons.Add(new Person("Maria", 16));
this.Persons.Add(new Person("Michael", 78));
}
public ObservableCollection<Person> Persons
{
get;
set;
}
}
public class Person
{
public Person(string name, int age)
{
this.Name = name;
this.Age = age;
}
public string Name
{
get;
set;
}
public int Age
{
get;
set;
}
}
}
|
|
|
|
|
What is the exact problem?
After a quick view, I see two things:
1)
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.
2)
class Person needs to implement INotifyPropertyChanged and after changing a property it has to call the PropertyChangedEvent.
Hope it helps
Andy
|
|
|
|
|
Good Day All
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"
private void btnEnter_Click(object sender, RoutedEventArgs e)
{
_mainFrame.Source = new Uri("/MainMenu.xaml", UriKind.Relative);
}
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
Thanks
Vuyiswa Maseko,
Spoted in Daniweb-- Sorry to rant. I hate websites. They are just wierd. They don't behave like normal code.
C#/VB.NET/ASP.NET/SQL7/2000/2005/2008
http://www.vuyiswamaseko.com
vuyiswa[at]dotnetfunda.com
http://www.Dotnetfunda.com
|
|
|
|
|
Dear All, Good day.
Need your help on threading.
I want to use a wpf window as progress window across my project.
On the main UI thread while doing the business logics i need to open a new wpf window in separate thread as progress window and once the Business logic is done i want to close the same.
I googled and found couple of examples to open a wpf window in separate thread and with new STA.. but am not able to find how to close the same window once done.
My progress window doesn't allow the user to close it.
global variable
progresswindow _pw = new progresswindow();
ShowProgress()
{
_pw.Show();
}
HideProgress()
{
_pw.Hide();
}
MainThreadBusinessLogic()
{
LogicStarts...
ShowProgress();
LogicEnds..
HideProgress();
}
This is wat i wanted to do. But as the main thread is very busy it wont show the progress window i know. I used the background worker and showed the progress bar.. But the thing is i have different business logic which will work based on the users clicks.. so i may need to create different workers for handling those.
If i do something like above mentioned window as progress window i can commonly use the same for all places.
Hence request your help here my friends.
thanks in advance.
|
|
|
|
|
You are doing it all backwards.
All UI lives on the main thread (including the progress window)
All business logic lives on a background thread
When you need to update the progress dialog from the background thread, use Dispatcher.Invoke.
|
|
|
|
|
Hi Sledge,
Thanks for your reply.
And you are right i am doing in the back ward only.
But the thing is, I have more the 20 forms in my application which have different functionality. And even in single form i have more than 5 buttons which will do different business logic's. So that is reason i wanted to do this approach, other wise i need to create separate background workers for all buttons or single background worker with different parameters.. which is more messy.
So i planned to have a separate progress window which can be accessed across all the forms.
But as we know both are in same thread causing issue. i planned to open and use the new window in different thread.
Expecting your reply thanks in advance.
|
|
|
|
|
Hema Bairavan wrote: which is more messy
LOL... no, it's not. The way you have it now won't even work. The main UI will be completely unresponsive, have painting issues, etc.
You can use async functions, lamba expressions, etc.
Bottom line is, you'll have to move your business logic to the background thread in order to make your app work.
|
|
|
|
|
Try looking at the BackgroundWorker class. It provides an encapsulation for a worker thread that supports passing updates to the UI taking care of all the dirty cross-thread marshaling. It is very easy to use and supports aborting as well.
As for your progress window, you need to raise it when the first background thread is started and close it when the last background thread ends. You may want to consider creating the form at app startup then setting all of the thread progress notifications to call a notify update method on the form. The form could then determine if it needs to show/hide and which thread(s) progress to show. Again, if you use a backgroundworker, there is a thread complete event which fires when the thread is done making it easy to do something "on the way out the door". The progress window should be event-driven... only responding to events raised by the worker threads.
|
|
|
|
|
Hi All,
My actual probelm is related to user control view open in center of main parent window according to uploaded image.
Such as "WindowStartupLocation" property of window for window open in center location.But i want to user control view open in center of main parent window.
Thanks
|
|
|
|
|
hello ,
i want to ask about how can i rearrange elements inside wpf , i want to be able to move ( exp groupbox) and switch it's place with other groupbox and etc ...
exp: the bitdefender antivirus form .
M!dox
|
|
|
|
|
You can look at the Blacklight dock panels[^] to check if they give you the layout you are looking for.
|
|
|
|
|
Hi! Began studying wpf. Versed with custom control'ami. I create the control (simple button) from Control.
The question is - is it possible to not draw method OnRend (such as they call it), and make the template, the file generic.xaml? And still do not understand why does not my click handler.
файл MyButton.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows;
using System.Windows.Controls;
using System.Windows.Data;
using System.Windows.Documents;
using System.Windows.Input;
using System.Windows.Media;
using System.Windows.Media.Imaging;
using System.Windows.Navigation;
using System.Windows.Shapes;
using System.Globalization;
namespace My_Lib
{
public class MyButton : Control
{
public static readonly RoutedEvent MyClickEvent;
static MyButton()
{
DefaultStyleKeyProperty.OverrideMetadata(typeof(MyButton), new FrameworkPropertyMetadata(typeof(MyButton)));
MyClickEvent = EventManager.RegisterRoutedEvent("MyClick", RoutingStrategy.Bubble,
typeof(RoutedEventHandler), typeof(MyButton));
}
public event RoutedEventHandler MyClick
{
add {
base.AddHandler(MyButton.MyClickEvent, value);
}
remove {
base.RemoveHandler(MyButton.MyClickEvent, value);
}
}
}
}
файл generic.xaml
xmlns:local="clr-namespace:My_Lib">
<LinearGradientBrush x:Key="Gray"
StartPoint="0,0" EndPoint="0,1">
<GradientStop Color="PaleTurquoise" Offset="0" />
<GradientStop Color="#CCCCFF" Offset="0.5" />
<GradientStop Color="Teal" Offset="1" />
</LinearGradientBrush>
<LinearGradientBrush x:Key="Gray2"
StartPoint="0,0" EndPoint="0,1">
<GradientStop Color="PaleGreen" Offset="0" />
<GradientStop Color="#99CC99" Offset="0.5" />
<GradientStop Color="Green" Offset="1" />
</LinearGradientBrush>
<Style TargetType="{x:Type local:MyButton}">
<Setter Property="Width" Value="100"></Setter>
<Setter Property="Height" Value="40"></Setter>
<Setter Property="Template">
<Setter.Value>
<ControlTemplate TargetType="{x:Type local:MyButton}">
<Border
x:Name="ButtonBorder"
Width="{TemplateBinding Width}"
Height="{TemplateBinding Height}"
BorderBrush="White"
CornerRadius="25"
BorderThickness="2"
Background="{StaticResource Gray}"
Opacity="0.9"
>
<ContentPresenter x:Name="ButtonContentPresenter"
HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}"
VerticalAlignment="{TemplateBinding VerticalContentAlignment}"
Margin="{TemplateBinding Padding}"
>
</ContentPresenter>
</Border>
<ControlTemplate.Triggers>
<Trigger Property="IsMouseOver" Value="True">
<Setter TargetName="ButtonBorder"
Property="Background"
Value="{StaticResource Gray2}">
</Setter>
</Trigger>
</ControlTemplate.Triggers>
</ControlTemplate>
</Setter.Value>
</Setter>
</Style>
</ResourceDictionary>
файл MainWindow.xaml.cs
namespace MyComponentsTest
{
public partial class MainWindow : Window
{
public MainWindow()
{
InitializeComponent();
}
private void myButton1_MyClick(object sender, RoutedEventArgs e)
{
MessageBox.Show("sd");
}
}
}
|
|
|
|
|
We have an application portal where a user can logon and launch any of our applications they are authorised for. Currently this is written in ASPX launching Silverlight applications.
We now need to extend this to launch Excel workbooks but also to integrate the launcher with a control application. I would like to do this in Silverlight as that is where our skill set is and I REALLY like the browser deployment method. Silverlight out of browser may be an option (is it still available in SL5) but does that then require a different deployment method.
We have the xap and file locations and we assume the user has access to the network drive the Excel workbook is stored.
The question is whether it is possible for a user to launch Silverlight apps and Excel workbooks from within a Silverlight app.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
Hi.
I have a class "Files" that creates txt files, i want the progress bar and the multiline textbox in the xaml shows the process when its occurs.
I receive all the paramates at the MainWindows.cs and i see the progressbar1.value growing and the textbox1.text having the desired text but in the gui nothing happends.
WHY?
|
|
|
|
|
It's a semicolon at line 34 that's causing a problem.
You may wonder why I said that. Well, I said it because I can't see your code. How on earth would you expect me to be able to figure it out.
I would suspect that the issue you are facing is that you are doing all your processing on the primary thread, which will block the update of the UI until it's finished processing.
|
|
|
|
|
i really wondered!!!
here is the class that create the files:
class Farmonicior
{
private string sourcpath = string.Empty;
public string SourcePath
{
get
{
if (sourcpath==string.Empty)
global::System.Windows.MessageBox.Show("The Source Cannot be Empty!!!");
return sourcpath;
}
set {sourcpath = value;}
}
private string resultFolder = string.Empty;
public string ResultFolder
{
get
{
if ( resultFolder == string.Empty)
{
FileInfo fi = new FileInfo(sourcpath);
resultFolder = fi.DirectoryName;
}
return resultFolder;
}
set { resultFolder = value; }
}
public void FilesWork()
{
string line = string.Empty;
List<string> LinesList = new List<string>();
try
{
StreamReader StrRdr = new StreamReader(SourcePath);
while ((line = StrRdr.ReadLine()) != null )
{
if (line.StartsWith("LN"))
{
LinesList.Add(line);
}
}
StrRdr.Close();
}
catch (Exception ErrExc)
{
System.Windows.MessageBox.Show(ErrExc.Message,"Read Source.");
}
Singleton.Instance.ProgressBarMAX = LinesList.Count;
try
{
Singleton.Instance.ProgressBarVAL = 0;
string year = DateTime.Today.ToString("yy");
foreach (string item in LinesList)
{
string[] lineArr = item.Split('|');
string newfile = string.Format(@"{0}\{1}_{2}.txt", ResultFolder, lineArr[2], lineArr[3]);
Singleton.Instance.NewFilesPath.Add(newfile);
StreamWriter StrWtr = new StreamWriter(newfile, false);
StrWtr.WriteLine(string.Format("yy"));
StrWtr.WriteLine(string.Format("nn|tttttt"));
if (lineArr.Length == 8)
{
if (lineArr[7] != "")
StrWtr.WriteLine("qwertyui");
else
StrWtr.WriteLine("poiuytrewq");
}
else
StrWtr.WriteLine(string.Format("HR|{0}|{1}", lineArr[3], year));
StrWtr.WriteLine(string.Format("RTG|{0}|{1}", lineArr[5], lineArr[6]));
StrWtr.WriteLine("END");
StrWtr.Close();
Singleton.Instance.ProgressBarVAL++;
}
}
catch (Exception ErrExc)
{
System.Windows.MessageBox.Show(ErrExc.Message,"Create Files.");
}
}
}
Here the MainWindows.cs
public partial class MainWindow : Window,INotifyPropertyChanged
{
Farmonicior hrm = new Farmonicior();
public MainWindow()
{
InitializeComponent();
}
private void button1_Click(object sender, RoutedEventArgs e)
{
PrgrssBar1.Value = 0;
Microsoft.Win32.OpenFileDialog dlg = new Microsoft.Win32.OpenFileDialog();
dlg.DefaultExt = ".txt";
dlg.Filter = "Text documents (.txt)|*.txt";
Nullable<bool> result = dlg.ShowDialog();
if (result == true)
{
string filename = dlg.FileName;
SourceFileTxtBx.Text = filename;
hrm.SourcePath = filename;
ResulFolderTxtBx.Text = hrm.ResultFolder;
}
}
private void button2_Click(object sender, RoutedEventArgs e)
{
string selectedFolder = string.Empty;
FolderBrowserDialog selectFolderDialog = new FolderBrowserDialog();
selectFolderDialog.ShowNewFolderButton = true;
if (selectFolderDialog.ShowDialog() == System.Windows.Forms.DialogResult.OK)
{
Singleton.Instance.NewFilesPath.Clear();
FilesNamesTxtBx.Clear();
Singleton.Instance.ProgressBarVAL = 0;
selectedFolder = selectFolderDialog.SelectedPath;
ResulFolderTxtBx.Text = selectedFolder;
hrm.ResultFolder = selectedFolder;
}
}
private void GoBttn_Click(object sender, RoutedEventArgs e)
{
PrgrssBar1.Maximum = Singleton.Instance.ProgressBarMAX;
if (hrm.SourcePath == string.Empty)
System.Windows.MessageBox.Show("Must Select a source file");
else
{
foreach (string item in Singleton.Instance.NewFilesPath)
{
FilesNamesTxtBx.AppendText(item + Environment.NewLine);
}
FilesWork();
}
}
public void ProgressBarStep()
{
PrgrssBar1.Value++;
}
internal void updateProgressbarMax()
{
PrgrssBar1.Maximum = Singleton.Instance.ProgressBarMAX;
progresBarTxtBx.Text = "Total files: " + Singleton.Instance.ProgressBarMAX.ToString();
}
}
here the singleton
public sealed class Singleton
{
MainWindow MW = new MainWindow();
static readonly Singleton _instance = new Singleton();
public static Singleton Instance
{
get { return _instance; }
}
int progBarVal;
public int ProgressBarVAL
{
get { return progBarVal; }
set
{
progBarVal = value;
MW.ProgressBarStep();
}
}
int progBarMax;
public int ProgressBarMAX
{
get { return progBarMax; }
set
{
progBarMax = value;
MW.updateProgressbarMax();
}
}
List<string> newfilePath = new List<string>();
public List<string> NewFilesPath
{
get { return newfilePath; }
set
{
newfilePath = value;
}
}
private Singleton()
{
}
}
this is. I hope i copy enough. be nice if you see coding horrors. thanks.
|
|
|
|
|
As Pete said, you're doing all your processing on the primary thread, which will block the update of the UI until it's finished processing.
Have a look at the BackgroundWorker[^] component - it makes it easier to do some work on a background thread and show the progress in the UI.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Hi.
Thanks for reply.
If i copy the FilesWork function to the MainWindows Class everything works OK. this still means i need the BackgroundWorker?.
modified 3-Feb-13 1:42am.
|
|
|
|
|
Thanks Richard.
The BackgroundWorker works and GUI works also. I forgot the ReportProgress so takes me some time to implemente it.
|
|
|
|
|
Hello, I've managed to setup an example working for both RoutedEvent and AttachedEvent but it appears the difference between the two is just syntactical as "RoutedEvent" handler can be declared in XAML in same syntax as "AttachedEvent". (I understand the difference between AttachedProperty vs DependencyProperty clearly)
Because of formatting issue with XAML - detail here:
http://forums.codeguru.com/showthread.php?534049-RoutedEvent-vs-AttachedEvent&p=2103409#post2103409[^]
Any idea anyone? Thanks
dev
|
|
|
|
|
Please don't raise the same question in multiple locations. You've just made it harder for yourself to get a cohesive answer. I'm not going to create an account on CodeGuru just to answer this question when the forums here are perfectly capable.
On the surface, it would appear that the two items are the same because they have the same syntax. Well, this is true to the extent that an attached event IS a routed event. A routed event, however, is not an attached event. In other words, an attached event is a specialised form of routed event.
So, what is an attached event? Well, basically, it's an event that can be attached to another element without the other element having to be aware that this capability is present. If you think about it as being like an attached property for events then it starts to make sense. So, why do we have this? Well, it allows you to extend WPF through composition rather than inheritance.
|
|
|
|
|
Pete O'Hanlon wrote:
So, what is an attached event? Well, basically, it's an event that can be attached to another element without the other element having to be aware that this capability is present. If you think about it as being like an attached property for events then it starts to make sense. So, why do we have this? Well, it allows you to extend WPF through composition rather than inheritance.
I understand perfect "Grid.Row" is an "Attached Property" that it's not a property of "TextBox" itself for instance. I understand analogy when this concept extended to "Events". However - what's confusing is the SYNTAX: you can define an event handler to a RoutedEvent the same way/syntax as you would with AttachedEvent.
But if you see the sample I gave in MainWindow.xaml, I can subscribe to "AttachedEvent" and "RoutedEvent" from xaml in same syntax - the syntax which does not require "Instance" of "GrandChild" (i.e. "MainWindow" does NOT implement event GrandChildRoutedEvClick itself, which is declared in "GrandChild")
From MainWindow.xaml, "RoutedEvent" handler setup like this:
<br />
local:GrandChild.GrandChildRoutedEvClick="GrandChild_GrandChildRoutedEvClick"<br />
From MainWindow.xaml, "AttachedEvent" handler setup like this:
<br />
local:GrandChild.GrandChildAttachedEvClick="GrandChildAttachedEvClickHandler" <br />
Despite in "MiddleChild.xaml", I setup handler to "RoutedEvent" the "Propery way"... what's real diff between Routed/AttachedEvent besides phylosophical or syntactical ...?
<br />
[local:GrandChild x:Name="Junior" VerticalAlignment="Stretch" GrandChildRoutedEvClick="GrandChild_GrandChildRoutedEvClick"/]<br />
What I am saying is, you can define a DockStateChanged event with syntax of a "RoutedEvent" - not "AttachedEvent", and in some parent control couple layers up, setup event handler using syntax as you would consuming an "AttachedEvent"
dev
modified 30-Jan-13 5:11am.
|
|
|
|
|