jcarmody

What did you have in mind?

I think of Endevo when I hear GOOP.

It rearranges states now, but without prompting the user. (I thought it would get annoying; I can add it later if it's needed/wanted; perhaps as a configurable item.) I had trouble implementing Undo for this operation so it's not in there. Also, it seems that there's not enough of the Event Structure exposed to let me include that yet. You can download it here. PS - I rewrote it using a better State Machine.

Is this the way to start? Except for choosing Color...

Can you tell me how to get a list of Selector Labels from an Event Structure refnum? I'd like to expand my CaseSelect RCF to accommodate those as well. Thanks, Jim

or, make it able to rearrange states! I hate the built-in method. I'll make it prompt the user in case the drag/drop was an accident. I thought about that, too. I was thinking about making it handle Event Structures as well. I've got some work ahead of me. Thanks for the input.

Have you seen this or this?

In that case, here's another iteration. CaseSelector.zip

I added a menu to the Tree to facilitate expanding & contracting. This has got to be it for today or I'm just going to get annoying... CaseSelector.zip

Done, thanks for the feedback. Done. I had added the OK button because I had always considered it bad practice to stop your program that way; it wasn't in the early versions. I agree though, it is nicer without it. CaseSelector.zip

Vell, Zaphod's just zis guy, you know?

Fixed issue where letting go of the scroll bar inside the tree acts the same as a selection. I didn't like that behavior. CaseSelector.zip

"I'm saying it because it's true. Inside of us, we both know you belong with TestStand. It's part of your workflow, the thing that keeps production going. If that project leaves the ground and you're not with TestStand, you'll regret it. Maybe not today. Maybe not tomorrow, but soon and for the rest of your life." Casablanca

Done. I've changed from double to single-clicking and I couldn't see how to make the PointToRowColumn do what you suggested, but I've implemented the same effect. Now, how about some constructive criticism on my coding/style? Please? Thanks! CaseSelector.zip

I've updated it to use a tree control. It indents states based on the presence of "-------" in the state name (ala JKI State Machine) assuming that these are section headers. Everything between them will be indented from the previous header and structures without this format will be presented without indenting anything. I also made it require a double-click to select a state so it would still be possible to expand/contract sections. The position of the scroll bar is persistent between calls (for the same Case Structure), but all sections are always presented expanded. CaseSelector.zip

I checked the llb and it looks Ok. There's obviously something wrong, but I haven't figured it out yet. I found another problem to fix - it won't select the first item in the list. I'll keep trying...

I used a Table with only one column visible (because it scrolls with the mouse wheel and the Array indicator didn't). A colleague suggested using a Tree but I didn't know how it would apply to a non-JKI State Machine Case Structure. I'll probably add the functionality to handle both, at least until the rest of the world is converted. This was my first plug-in and I wanted to understand the process before trying to get fancy. The window is resizable w/auto-grow (unless I botched that part of the llb, too). Alas, but I won't be at NIWeek. Is one of the helper tools, perhaps, the ability to right-click on the queue wire and insert an Add States To Queue? I'm going to do that if nobody else beats me to it. It'd probably be a good exercise for me. Cool, thanks. Will I be able to update that when I fix the problem François had? (I had to copy/paste from his signature to get that "c" with the "5" underneath...)

I had this problem, too, but THOUGHT I had it licked. There's a sub VI that presents the list and waits for a user input it never gets because the Front Panel never shows. I resolved the issue by setting the VI Properties to open & close the front panel as appropriate. It may be that an old copy made it into the zip file; I'll know more tomorrow when I get to the office in the morning (I'm currently restoring my laptop from a series of unfortunate events). I changed my approach and am not polling as I mentioned in the other thread. This one pulls the first element from the array of selected objects and tests to see if it's a Case Structure. If it is, it sends an array of frame names to the sub VI mentioned above. This has an event structure that waits until you select a state then returns the index to the RCF VI (which sets the VisibleFrame property). Thanks for trying this. I'll fix it tomorrow, but I think all it needs is the VI Property change.

Here it is. Unzip the contents into [LabVIEW]\resource\JKI\RCF\Plugins\CaseSelector Use: select a Case Structure, apply the RCF Menu Activation Keys, right-click and select CaseSelector. A resizable list will be presented with the selected structure's cases. Select one of the cases, the list will disappear and the selected case will be brought to the front. I'll certainly use this functionality, but I may prefer to put a VI in the LabVIEW project folder (so I can have the list persist as a floating dialog). So. Is this anything that you'd use or do I have a unique situation? CaseSelector.zip

I think I slapped my head too soon. I'm trying to detect that a Case Structure was selected in another VI so I need to detect an event at the Application level, no?

Doh! Duh... Thanks.

I'm doing this as part of the work associated with this post. I wonder if I can detect that a Case Structure has been selected by some method other than polling. I'd still have to poll to handle scrolling through the long lists. This sounds like a topic for another post on the VI Scripting forum... I'll try to figure it out myself first.

I started my LabVIEW life hating Auto Grow; I don't know why or when, but I started using it again a while ago. Anyway, now I only hate it when I'm pasting or typing into a string control near the edge of a structure. I think the only thing I like it for is when I'm trying to clean up my BD - it keeps me honest when resizing.

None, it's in the timeout case (which is also polling to see if a case structure is selected).

I fear I'm missing something obvious. I want to scroll an array indicator with the mouse wheel and this is what I came up with: Is there an easier way? Thanks, Jim