When creating VI from [either] dispatch in LVOOP, auto generate a title on front panel to be edited

[plyons.gks]

I'm having trouble posting a picture on here for some reason but here is what I mean:

http://i.imgur.com/ihhn7gm.png

When right clicking on a class to generate a new VI, say with dynamic dispatch, have LabVIEW automatically place some large text at the top of the front panel.  I do this with just about all parent and child classes to make sure I don't end up getting confused due to their similar layout or appearance.  It doesn't take for ever to double click and type, and then select again and do 'ctrl+' a bunch of times, but I know I would find it extremely helpful if there was some large text there to begin with.

Does anyone agree?  Does anyone do this already?

Thanks

-Pat

PS- it would also be nice if there was a better way for me select an Idea Label (I typed in LVOOP and it didn't like it, So now I've just put UI and usablity...)

[AristosQueue (NI)]

So, let me see if I get what you're asking...

You have a parent class and a child class. Both of them have an instance of X.vi. You want large text on the panel that says "Parent.lvclass" on one and "Child.lvclass" on the other.

Do I have that right?

I am open to the idea of making the two VIs more distinguishable if that's a problem for folks, but I need to know more about why the current mechanisms for distinguishing the VIs are not enough for you before I can say what the right fix might be. There are two unique ways already to recognize which panel is which:

1. The title bar of the VI has the class listed first before the VI name
2. The panel of any dynamic dispatch VI already has a colorful cube of the specific class on it as one of the inputs. You can't not have that input.

What makes these two mechanisms insufficient for you? What does the text on the panel provide that the text in the title bar or the icon on the cube does not?

Separate question: Do you have the same problem distinguishing the two diagrams? Would you put the same text on the diagram as well as on the panel? Or is the code differences on the diagram sufficient to distinguish?

[tst]

And ignoring AQ's general and valid questions, which I believe you should answer, I would like to point out that you can already make this change today - go into <LV>\resource\framework... and find the LVclass VIs (sorry, I don't feel like digging up the details). Some of them should be template VIs for the DD VIs and some of them should be callback VIs which are called after the VI is created. You can use those to automatically place the text on the FP and change it.

That said, I would suggest avoiding that and understanding why the existing mechanisms aren't enough for you.

[plyons.gks]

You have a parent class and a child class. Both of them have an instance of X.vi. You want large text on the panel that says "Parent.lvclass" on one and "Child.lvclass" on the other.

Thanks for the reply!

Yes, this is what I'm reffering to- Although I had no idea about the options tst brings up, (didnt think of that myself ...) I guess I may have posted this too early, and should have made a forum post. I apologize if I'm wasting your time here!

1. The title bar of the VI has the class listed first before the VI name
2. The panel of any dynamic dispatch VI already has a colorful cube of the specific class on it as one of the inputs. You can't not have that input.

 I do see these two indications, but in the past they have not been "in my face" enough to keep me from making the stupid mistake of putting code in the wrong places (not just between parent and child, but between siblings too).  With many windows up from various siblings etc while working I feel like my risks are greater... As a result, I've started putting big notes of text so I don't mix any of these up.

Others may see this as totally unecessary, I just wanted to post up and see if anyone else could benefit from it.

Oh and yes, I also do this with the block diagram too, just to be clear when im shuffling windows around... 

Thanks for the time

-Pat

ps- sry I missed the quote option in the upper right... 

[AristosQueue (NI)]

No problem.

The VIs that Tst mentions are:

resource\Framework\Providers\LVClassLibrary\NewAccessors\OverrideRetooler\Custom User Scripting For New Override VI.vi

--- Allows you to add custom scripting to the VI generated by New >> VI For Override...

resource\Framework\Providers\LVClassLibrary\NewAccessors\BaseAccessorScripter\Custom User Scripting For New Simple Accessor VI.vi

--- Custom scripting when creating an accessor (two other similar VIs are also found nearby for array accessor scripting

resource\Framework\Providers\LVClassLibrary\NewAccessors\VIRetooler\CLSUIP_CreateNewVI.vi

--- affects new VIs in classes -- this might be password protected... I don't remember.

[plyons.gks]

Looks like only that third one is password protected- I'm not even sure what to do if I could get into it haha- it doesn't appear to be a template, but I don't really know what's going on at this level, seems a bit over my head and I don't think I'm willing to go experimenting by myself here... (password protected for a reason I presume). 

Thanks for the info

-pat

[MaryH]

Although improving how to tell which class a VI is associated with is a good idea, this particular mechanism for doing so creates noise that it seems most developers would need to wipe out, just creating more work for users when creating override VIs. Alternate ideas for identifying the VI's class association should be proposed as new ideas.