Shame that Draw Graph with Events.vi is no longer in the Example Finder.
Yes, that was a nice one....
I like my program like this. I post my finished solution so that the next guy can use it. Since I am a labview newbie I expect you to find some problems with this. But it works, I like it and I've seen worse. Cheers!
I expect you to find some problems with this.
Well, it was a quick redo of what I was doing in a bigger program. The tab control was in fact supposed to be inside the while loop. And I already fixed the data flow thing in my real program.
But I don't really see a problem in "hiding" the event structure in the case structure. Since everything that can trigger the event structure disappears for any user when the tab is changed (at least that's what happening in my real program) I'd like to remirror that in the block diagram. If there is really a reason why I shouldn't do that, then I know, that I don't need the case structure. But it cleans up my block diagram and helps my successor to understand that this is only relevant for the respect tab case (so in my big program there are other tab cases where other stuff happens). But please explain why I NEVER EVER should do that.
Unlabeled LED: ... "press Enter to draw" --> you dont have to press the led you can use your Keyboard to press ENTER and I really like this. I think it's intuitive.
Typically the tab terminal does not need to be connected to any code (or case structure), because the event structure can assume that the FP is on a certain tab from which control has been operated.
It is a very bad habit, for example if events are triggered for an event structure that is not in the dataflow (e.g. in a different case), they will accumulate forever in the event queue and the code has no way of ever servicing them. If the case ever switches, the oldest event will trigger which might be very stale and irrelevant.
Können wir Deutsch reden?
this is an English forum so you should speak English too!
Wenn du unbedingt Deutsch reden willst, kann ich dir das deutschsprachige LabVIEWforum empfehlen. Es gibt schließlich Gründe, warum es hier bei NI.com u.a. französische, spanische, chinesische Unterforen gibt - aber eben nicht direkt auch ein deutschsprachiges:
well my englisch seems to be to bad to understand you. Können wir Deutsch reden?
I speak graphically, so here's a very quick draft to give you some ideas how to simplify things. Arguably less code.
(Also be careful with mechanical actions of booleans. For example your "clear" button is "switch until released", creating two events, one for the press and one for the release. Latch action is more normal to use in almost all cases.)