LabVIEW
What are your thoughts about this "double queued command"
@Christian_M wrote:
The Turducken is a very good analogy!
But you could also prepare and eat the three birds individually (I think I would prefer that).
In other words you could separate your clusters containing the commands and variants into individuall queues.
It seems that you allready designed some parts of your application, so for my opinion an OOP implementation would be a huge impact.
Christian
I see what you are saying. I will have to think about the separation of the command clusters into two queues in order to achieve the result I want. On the other hand, you are right that I have parts of the application already designed and changing to OOP would be impractical at this stage. Nonetheless, I can always apply OOP concepts to my next project 
Ben wrote:
I am not free to post an example but I write a little and wave my hands a bit...
Look at the DAQmx implementation. After saying what you want you hit it with a start task and DAQmx is the expert at getting it started. We use the same DAQmx consruct if the widget is a PCI card a USB device or whatever.
In the old DAQ version we had to route wires while observing the phase of the moon and swing a dead cat over our heads (not offence to those cat lovers out there).
In my I/O libraries I support just about every widget I have touched ove that last year or two. They range from SPI devices to serial to DAQmx etc. I have implement the I/O library such that I select which flavor I want to use then tell it here is the config file, "Go configure yourself".
With the very little code you showed us it looks like your sender is micro-managing what is happening at the other end.
I don't mean to offend. I am only trying to help while at the same time put out some ideas for the community to concider or crush.
Take care,
Ben
You are not offending anyone (at least not me. I am not a cat lover myself either). It is always great to learn new concepts. I think I am starting to understand what you mean with the "Expert Pattern" but I will have to leave a background process running on my head for a while trying to put all the pieces together. Referring to the DAQmx example, what you are saying is that I could have a VI that configures a LV object with various available options (similar to how a "Create DAQmx Channel" does) be called first, and then call an executing VI with the already configured LV object as input (similar to the "DAQmx Start"). In this way , all the configuration is not happening on the sender side. Man, I don't think I will be able to sleep tonight thinking about this pattern
@jarcTec wrote:
... Man, I don't think I will be able to sleep tonight thinking about this pattern
I find a couple of beers on the front porch with The Princess* helps with that sitution.
Ben
* The Princess = My wife who has a masters in IS and politely pretends I am making sense.
