-
Jun 14th, 2013, 03:32 PM
#1
Thread Starter
Junior Member
Best way to notify user an external program is stil running.
Hi guys,
I am wondering what might be the best way to notify a user that the external program they are connected to is still running?
The app I am updating from VB6 to VB.Net previously would plot real-time data points on a graph. I have recently found out that there is absolutely no need for the graph or the data. Along with that, the customized user control that the previous developer created was unnecessarily complex (so I am trying to avoid re writing its functionality in VB.Net). With that said, I am looking for an idea similar to the previous control in that it provides real-time feedback...
Any help/ideas would be great, thank you in advance.
-
Jun 14th, 2013, 04:23 PM
#2
Re: Best way to notify user an external program is stil running.
Creep up behind them and shout "Boo!"
Not really a lot to go on there, is there? Is this external program started from your application? What does 'connected to' mean? Will the world shatter into tiny pieces of diamond and float away into space if the external program goes on running. Does any of it, in the face of the size and complexity of the Universe actually matter? Will it ever stop raining?
As the 6-dimensional mathematics professor said to the brain surgeon, "It ain't Rocket Science!"
Reviews: "dunfiddlin likes his DataTables" - jmcilhinney
Please be aware that whilst I will read private messages (one day!) I am unlikely to reply to anything that does not contain offers of cash, fame or marriage!
-
Jun 14th, 2013, 11:47 PM
#3
Re: Best way to notify user an external program is stil running.
Your description and question are rather vague. What does "connected to" mean? Are you starting the the other app? Are you making a TCP connection or the like? Are you asking for visual feedback to be displayed in your own form? You need to provide a FULL and CLEAR description of the problem. The more that we have to guess, the less chance you'll get the help you want. If we guess and guess wrong then it's a waste of everyone's time.
-
Jun 17th, 2013, 07:25 AM
#4
Thread Starter
Junior Member
Re: Best way to notify user an external program is stil running.
My app starts NIDAQ (National Instruments Data Acquisition) with a button on my interface. It allows the user to decide whether or not they need the data provided by National Instruments. I am looking to send visual feedback to the user from my interface after they have chosen to start NIDAQ (with the button click) and start running a speed or torque test (doesn't matter which one). From there I would like to notify the user from my interface that their current test is still running and hasn't seized up.
-
Jun 17th, 2013, 07:59 AM
#5
Re: Best way to notify user an external program is stil running.
Originally Posted by UpperN9ne
From there I would like to notify the user from my interface that their current test is still running and hasn't seized up.
Remember when I said:
provide a FULL and CLEAR description
What exactly does "seized up" mean?
-
Jun 17th, 2013, 08:26 AM
#6
Thread Starter
Junior Member
Re: Best way to notify user an external program is stil running.
Seized up would usually imply that their test has stopped, wouldn't it? Can't get much clearer than that. Sorry.
I will figure it out myself.
-
Jun 17th, 2013, 08:51 AM
#7
Re: Best way to notify user an external program is stil running.
Originally Posted by UpperN9ne
Seized up would usually imply that their test has stopped, wouldn't it? Can't get much clearer than that. Sorry.
I will figure it out myself.
I assure you that you could get much clearer than that. What does "stopped" mean? Does it mean that the process has completed? That the application is not responding? Something else entirely? Thanks very much for wasting the time of those trying to help you. If your ability and, more importantly, desire to explain the problem clearly is anything to go by then you probably won't figure it out yourself, but I wish you luck.
-
Jun 17th, 2013, 09:11 AM
#8
Thread Starter
Junior Member
Re: Best way to notify user an external program is stil running.
I was merely asking for suggestions to go about a process of notifying a user that "something" was running or not. Yes, that is a very vague request and I intended this because I was looking for a multitude of ideas. I was not looking for a specific answer, I was looking for more of a possible guideline. As far as me wasting your time, you have full control over whether or not you respond to this thread. To blame me for you replying to my thread is absurd. If you had no desire to help, rather just criticize and insult me, then I thank you for wasting my time.
-
Jun 17th, 2013, 09:43 AM
#9
Re: Best way to notify user an external program is stil running.
Originally Posted by UpperN9ne
If you had no desire to help, rather just criticize and insult me, then I thank you for wasting my time.
I had every desire to help but my repeated requests for relevant information were apparently falling on deaf ears. Again, I assure you that you could get much clearer than the description you provided. If it was clear then I wouldn't have been been asking for more. If Rapunzel had asked prince Charming to rescue her from the tower and then repeatedly refused his requests for her to let down her golden hair, would you not consider her to be wasting his time? If you had provided an adequate description of the problem then you'd have had a solution by now. You haven't so you don't. It looks like it will stay that way for the time being.
-
Jun 17th, 2013, 09:46 AM
#10
Re: Best way to notify user an external program is stil running.
Originally Posted by UpperN9ne
My app starts NIDAQ (National Instruments Data Acquisition) with a button on my interface. It allows the user to decide whether or not they need the data provided by National Instruments. I am looking to send visual feedback to the user from my interface after they have chosen to start NIDAQ (with the button click) and start running a speed or torque test (doesn't matter which one). From there I would like to notify the user from my interface that their current test is still running and hasn't seized up.
Will you show the code that is used to start NIDAQ?
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|