|
Hello,
I'm implement some UI application.
The problem i have is how to fire events between two threads ?
Thread A (ui main window/wpf) launch thread B (console app project) with the logic of the app. here i have some recursive algorithm, which generate some question to the user.
Then by event i fire this question to the main ui window and update the ui with the relevant question (any other way to do it ?)
After the user see the question he needs to insert some answer, and according to this input the recursive algorithm continue it's execution.
The problem is how to idle the recursive execution (while the user decide what to answer...)
I was thinking to use background-worker/busy waiting, but is it possible to fire events between threads ?
Thanks for help
|
|
|
|
|
And it's a cross post - don't spam the forums, select 1 and wait for a response.
Why do you feel you need to have multiple threads for what is a very simple process.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
then how can i implement it by using single thread ?
|
|
|
|
|
Why would you launch a console app? From the sound of things, you are trying to communicate across PROCESSES, not threads.
|
|
|
|
|
I started with console, i'll move it to class library, and eventually i'll add a dll as a reference.
|
|
|
|
|
First of all, you are not really dealing with multiple 'threads' here. Yeah, each process executes on its own thread, but you are really not writing a multi-threaded application.
You are writing two applications.
Your question is REALLY about how to get the two applications to talk to one another.
There a bunch of ways you can do that. Use sockets, use web services, etc...
But first ask yourself the big question....
WHY are you forcing yourself to use this design?
What is requiring you to set this up in this way?
|
|
|
|
|
what do you mean "why i forcing myself..."
I implemented some algorithm, and now i want to ad an ui...
also i would like to build some data base of users, ans store there their profiles.
so far i have three different projects (for each layer) what wrong with that ?
|
|
|
|
|
You need to go back and look at your wording though...
You state that you main application (you call Thread A) is a windows/wpf application and that it launches 'a console app' (that you refer to as Thread B0 that takes care of some backside processing based upon the answer, but no matter there...
The fact that they are separate processes is a bit concerning because now you are spinning of a completely different application (process) that you have specified as a console application to do processing in the background, when in reality it sounds like what you really want to do is just create a new process that is part of your existing application, throw it up on a new thread so it can run independently of the main thread (not a bad thing) and then do your processing as needed.
In reality, if you use separate physical processes, you ARE creating different threads. Each individual process gets it's own thread of execution... but now you need to deal with inter-process communication options like pipes, web services, sockets, etc...
I would just build a class to contain your additional processing, spin an instance of that up internally and use events to pass data back to the main thread when you need to update something visually. Dealing with an app that has multiple individual PROCESSES can be a real pain to maintain, debug, and extend latter on.
|
|
|
|
|
Thanks for the detailed answer...
First, my logic is not a console app, it started with console, but then i wrote it from scratch as a dll.
AS your advice, i put my logic into additional class, and i use events to pass data, but i still have some problems with the recursion which should be idled when it waiting to the users answer...
|
|
|
|
|
Sorry, I have been away for a while on vacation...
I am a bit confused when you mention recursion... if you are just sitting there waiting for a user to answer a question then you are really not using recursion.... you really just need to let that thread spin on and wait for a request from the client. Just put the processing in your separate thread into a loop that keeps it cycling until it gets a request from the host to perform some processing. Because it is on a separate thread it will not interfere with processing while it is just waiting.
Usually you just wrap everything in your thread function inside a do loop that watches for different flag settings to know when it needs to abort and end or process some data.
|
|
|
|
|
Hi,
When i say recursion, i mean that the flow of the algorithm will repeat it self depending the user input
|
|
|
|
|
We have many windows services on several servers.
How do you suggest to build a silverlight 4.0 application which monitors these services on servers?
I am thinking to have a functionality to check the status of each service on each server every so often i.e. every few seconds...
What are your thoughts please?
Thanks
|
|
|
|
|
You'd have to communicate with a backend web service, which polled these services to see if they were running or not. The Silverlight application would trigger the web service periodically (say every 10 seconds) and the results would be updated in a notifiable object.
|
|
|
|
|
Do you mean like having a timer inside a WCF to monitor changes every so often?
And then use the silverlight to check the WCF?
Please elaborate.
Thanks
|
|
|
|
|
I'd initiate this from the Silverlight side if I were you. Have Silverlight request the information from the service at timed intervals.
|
|
|
|
|
Do you mean to have the silverlight app to call the (WCF which checks all the windows services) ?
Thanks
|
|
|
|
|
|
|
You could also building an SL4 options with OOB option and COM support, but this could check windows services running on the client and not on the server.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
My latest tip/trick
Visit the Hindi forum here.
|
|
|
|
|
Again on with my quest to learn WPF controls and improve our standard controls library to make it easier to use within a MVVM environment.
In this case I am looking for sggestions for how to best implemnt a standard button.
I would like to create a standard button which has an image and caption.
I understand that this is easily achieved using xaml, but ideally we would like a standard implementation so the button could be used in the following manor.
<CustomControls:StandardButton ButtinImage="Logout.jpg" ButtonCaption="Button Text"/>
How would you achieve this?
1. Inherit from the button class and add dependancy properties
2. Use Attached Properties and a style
3. Inherit fron UserControl using dependancy properties fro the image and caption
Thanks for your time
Just racking up the postings
|
|
|
|
|
I would, personally, go for 1 or 2.
2 is good if you are clear on how to create attached properties.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
My latest tip/trick
Visit the Hindi forum here.
|
|
|
|
|
If i go for one, I am assuming that I can do away for a controltemplate and just set the content to be an image object and a label programitcally based on the dependancy properties.
Does this sound right?
Just racking up the postings
|
|
|
|
|
If you want to have a bit of fun, you could always create a Blend Behavior which set the Content of the button.
|
|
|
|
|
Not sure that sounds like fun...
Just racking up the postings
|
|
|
|
|
It does to me (and it's very easy to do).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
