there is a 3rd solution, which is a controller that calls ReadData(x, y) and calls Analyse( x,y ). That controller could be the Blackbox message loop. Or it could be the response to a button press or some other event. This makes the user - that's us - the boss.
B
From: BlackBox [mailto:BLACKBOX{([at]})nowhere.xy
Sent: 01 April 2011 12:18
To: BLACKBOX{([at]})nowhere.xy
Subject: [BLACKBOX] Don't Call us & ReadKey & long running commands
Dear BlackBox Users.
There are too many questions about ReadKey. Now lets have a look from the other side of the sky.
I'll start with a simple long running application. Its task is reading and analysing measurement data. This task can be divide into two PROCEDURs (or MODULEs). One for reading and collecting the data and another one for analysing and calculating them.
There are 2 different solutions for writing such a program:
1. The analyse solution:
In the "PROCEDURE Analyse;" is a loop which is calling "ReadData(x, y);" and works with it.
2. The read solution:
In the "PROCEDURE ReadData;" is a loop which is reading data and is calling "Analyse(x, y);" .
The question is: Who is calling? "Don't call us, we'll call you!" Who is the boss? The analyser or the reader? Why should we have a boss (main program)? Why isn't it possible that both procedures are calling each other? What about both procedure having equal rights. Calling is equal to Return (symmetry).
Why should I have a long running command with my own windows process message loop? Why can't I call the BlackBox message loop? I mean: One call runs ones thru the BlackBox message loop and then it returns to the caller. Nothing will be frozen.
With best regards
Helmut Zinn
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
Received on Fri Apr 01 2011 - 13:30:42 UTC