LabVIEW
buttons dans les onglets
Jim,
Your solution is from a UI perspective about the same as mine, however, you made some strange choices that I don't recommend.
- It is sufficient to have a single event case for all button handing, it simplifies the code and code maintenance. Your version requires N instances of the value property node and N+1 event cases.
- I don't understand your choice for "switch until released" mechanical action with "mouse up" events. Seems exotic and convoluted.
- It is not recommended to write to "value" property nodes for soemthing like this, A local variable would be much more efficient and simpler.
Here's basically my solution (with the buttons no longer floating). It is much more scaleable. For example it would be trivial to change the number of buttons while in your case you would need to duplicate entire event cases, complicating the code.
Altenbach,
thank you for your input. As most of my training has come in the last year from this forum, the remainder of it has come from trial, and obviously error.
altenbach wrote:Jim,
Your solution is from a UI perspective about the same as mine, however, you made some strange choices that I don't recommend.
- It is sufficient to have a single event case for all button handing, it simplifies the code and code maintenance. Your version requires N instances of the value property node and N+1 event cases.
I like the elegance of the boolean array, but once you exceed 4 or 5 buttons handled by the event, the text exceeds the view in the case ring, and thus becomes unreadable. Is this not undesirable?
I don't understand your choice for "switch until released" mechanical action with "mouse up" events. Seems exotic and convoluted.
Probably ignorance on my part. I like the momentary switch because I never have to set or reset it's value. When not pressed it is false.
- It is not recommended to write to "value" property nodes for soemthing like this, A local variable would be much more efficient and simpler.
True
Here's basically my solution (with the buttons no longer floating). It is much more scaleable. For example it would be trivial to change the number of buttons while in your case you would need to duplicate entire event cases, complicating the code.
I don't understand what you mean by "buttons floating". While adding a button to the array is easy, doesn't the inability to easily read the case ring reduce it's scalability?
Thanks again for your insights. BTW thanks also for the link you used to have for the Dukes of Ted. Neat music. Are they still together?
