69 replies to this topic

[jgcode]

but I'm not sure it's intuative.

Agreed.
Sorry, I was out most of the morning, so I didn't spend as much time on feature some of it as I wanted to.
But wanted to get it out for feedback

My first goal was proof of concept (that I could script it).
I can always give it a facelift, now that I have the functionality.

So at the mo, you are cloning the active VI, i.e. QD'd VI.
I tossed up separating the functionality into another tool (but didn't for whatever reason) - so I have thought about that it may not be best suited where it is.

So for now (no proj int):
Maybe a dropbox of all VIs in the Class would have made more sense too? You could clone multiple methods at once, but that is not my usually use case.
I could make it a separate Tools Menu action that operates on the Active VI - that might make more sense?

[jgcode]

Nice job Jon! LVOOP Assistant is now my second favorite user contributed tool. (Hard to dethrone CCT, though I will definitely use this more than CCT.)

Thanks Dave

"Link to your own Static/Dynamic method (.vit) templates
Create your own Virtual Folder names etc..."

Both of these occurred to me while watching the videos. Being able to set my own templates would be more useful for me than defining custom virtual folder names. I tend to create virtual folders on an as needed basis depending on the class requirements rather than use a pre-defined set of folders.

My next step is to open this up.
The settings are what I like, but obviously people would have their own templates that they like - so I can point to those.

[Virtual Folders] The LVOOP Assistant gives me the option of adding my favorite folders anytime to the Class without the need to worry about syntax or scoping etc... (and if they already exist it just ignores it). You can start with a few and as your Class changes over time you can bang in more.

"Public Service Announcement"
Since LabVIEW is a contracronym is the first place, shouldn't it be LVIEWOOP? Or just LOOP?

I don't want to get bashed, so I am going with L-VOOP

[crelf]

Chris Relf... a man whose wisdom runs so deep he quotes himself!

My wisdom is both reentrant and reentrant.

Maybe a dropbox of all VIs in the Class would have made more sense too? You could clone multiple methods at once, but that is not my usually use case.

Yeah, that's a very rare use case for me. It's more of a clone class than a clone method.

I could make it a separate Tools Menu action that operates on the Active VI - that might make more sense?

I guess, but I ultimately want Project Explorer integration - so I can right click on a method and clone it <- make it happen.

Public Service Announcement

You're welcome.

[jgcode]

Project Explorer integration... ... <- make it happen.

I hear ya!

[huotom]

Feature Request: Clone a Method VI

I have updated the repository with a new version - you can now easily clone a method using this tool.
Supported Templates include:
4815 - 4x2x2x4
4833 - 5x3x3x5
4834 - 6x4x4x6
4835 - 8x4x4x8
(Assumes any other LVOOP Class Control is a data member or parameter).

Where drinking from a camouflaged can... ...makes you look tough.

Error occurs!
LV could not find addons\_ICON Library\scripting\_icon_lib_scripting.lib.

[jgcode]

Error occurs!
LV could not find addons\_ICON Library\scripting\_icon_lib_scripting.lib.

Thanks huotom.
Sorry, some files were missing from the build.
The new version (0.14.1) is up on LAVACR and has fixed this issue.

Cheers
-JG

[jgcode]

Shortcut to download latest version here

Changelist:
0.15-1 2010 09 26
- Added (): Name of Method VI being cloned is displayed on Clone Dialog
- Fixed (): Order of Virtual Folders in GUI did not match script
- Fixed (): Creating Constructor from Template did not replace Class Input Control (caused by refactoring for Clone method support)

Attached Thumbnails

• 

[Daklu]

This is for 2009 only? I'm not given the option to install the package for 2010.

[jgcode]

This is for 2009 only? I'm not given the option to install the package for 2010.

Hi Dave, as per the Readme, only 2009 is currently supported at the moment.
One of the next things I will be doing is testing it in 2010, to make sure its all good.

Are you moving up to 2010?

[Daklu]

Hi Dave, as per the Readme

You mean I'm actually supposed to read that? I suppose you faithfully read all the terms and conditions when you install new software too?

Are you moving up to 2010?

Already have, except for reuse code. Still doing that work in 2009.

[neil]

Jon,

Any way to change the font size for the banner? Mine seems to be using a bigger font than in your videos.

[neil]

This tool rocks!

Ammendment to my previous comment: all newly created classes have correctly sized banner text when set via the LVOOP Assistant

However, a class I created previously (when I still had the font size set to 10 in the Icon Editor) seems to still be using the using the old font size.

[jgcode]

Hi neil

This tool rocks!

Thanks for the kind words.

Ammendment to my previous comment: all newly created classes have correctly sized banner text when set via the LVOOP Assistant
However, a class I created previously (when I still had the font size set to 10 in the Icon Editor) seems to still be using the using the old font size.

I set the Class to defaults (8) if the IE2009 (layer) data was empty, and I always use 8 internally (so this hasn't cropped up for me).

The other reason is I decided to leave all other settings that exist alone is - in case they have been set for a particular reason.
But I could override the 10 to an 8 if this is always preferred (like I do currently for Caps)?


Also, would you mind posting a screenshot of what it looks like?

Cheers
-Jon

[neil]

The other reason is I decided to leave all other settings that exist alone is - in case they have been set for a particular reason.
But I could override the 10 to an 8 if this is always preferred (like I do currently for Caps)?


Also, would you mind posting a screenshot of what it looks like?

That would be great, I do not think I will ever change the font size. On my PC 8 and 9 do not seem to make any difference. I tried to fix this myself by digging inside the LVOOP Main window by aborting it (ctrl+. and various Abort.vis) none of these worked and I was not that interested so I gave up :-)

Will post a pic when I get home from work tonight.

Another thing. Don't know if this is related to the LVOOP Assistant or not, but it happened shortly after installing it. Once, when I went to the Class properties dialogue I got a bunch of LV errors and none of the sub-pages loaded properly. The errors were not fatal, and selecting the Properties again caused it to work fine. This has only happened to me once, and I have only been using 2010 for a few weeks now. Will keep you posted if it happens again and try and make a note/screencap of the error messages.

[neil]

ok, here are two pics showing the behaviour

The old class seems to use a big font, but when I use the assistant on a newer class, even if I type the same text it uses a smaller font.

Attached Thumbnails

• 
• 

[jgcode]

ok, here are two pics showing the behaviour

The old class seems to use a big font, but when I use the assistant on a newer class, even if I type the same text it uses a smaller font.

Yes, the reason for that is as explained above.
10-pt would still 'fit' if you always less characters.

Another thing. Don't know if this is related to the LVOOP Assistant or not, but it happened shortly after installing it. Once, when I went to the Class properties dialogue I got a bunch of LV errors and none of the sub-pages loaded properly. The errors were not fatal, and selecting the Properties again caused it to work fine. This has only happened to me once, and I have only been using 2010 for a few weeks now. Will keep you posted if it happens again and try and make a note/screencap of the error messages.

(Are you using the LECC2010 version - v0.16?)

Hmm, I saw this once too, but never with LV 2009, only in LV2010. And like you said it was fine after reloading. I can't seem to replicate it, but will have to keep an eye out.
If anyone has any info on this or seen anything similar before when working with Classes + scripting, please post

[neil]

Yes, the reason for that is as explained above.
10-pt would still 'fit' if you always less characters.



(Are you using the LECC2010 version - v0.16?)

Hmm, I saw this once too, but never with LV 2009, only in LV2010. And like you said it was fine after reloading. I can't seem to replicate it, but will have to keep an eye out.
If anyone has any info on this or seen anything similar before when working with Classes + scripting, please post

yup, using 0.16

[jgcode]

I uploaded a new version to LAVA - the main feature is native support for LabVIEW 2010.
The code now checks for LabVIEW version and mass compiles if IDE is newer.
I tried to optimize it as just compiling the directory takes a long time due to a few Libraries and Classes etc...
The workflow is pretty much copied from what I have seen using some JKI tools - so props to them.





Notes:

• Version 0.16 was entered in the LECC 2010 but was not added to the LAVACR.
• Version 0.17 just updates some support files for LAVA and is added to the LAVACR.

Cheers
-JG

Version History (Changelist):
0.17-1 2011 01 23
- Changed (): Rebuild for LAVA distribution. Support files changed only (no code changes).

0.16-1 2010 10 05 (LabVIEW Example Code Contest 2010)
- Added (): Support for LabVIEW 2010. Include Mass Compile option on first load
- Changed (): Now requires Icon Editor API v2.1-1 as dependency
- Fixed (): Popup on New Class Control resolves correct 'Current Icon'

[Michael Aivaliotis]

The code now checks for LabVIEW version and mass compiles if IDE is newer.

Actually this is not required anymore since VIPM 2010 already does a mass compile after installing packages now.

[jgcode]

Actually this is not required anymore since VIPM 2010 already does a mass compile after installing packages now.

Yes, that is correct however, for a normal VIs this is great.
For a larger dist with libraries and class I found it was much slower.
The reason being that all code in the directory was handled i.e. open/checked/compiled.
But due to the above VI relationships this was slow.

What I did to optimise it was to only point to a VI Tree so one VI gets handled.
I don't have any benchmarks recorded but it was actually something I wanted to discuss with you.