Jump to content

How to get your team members aster LV developers


Recommended Posts

We all know that Quick Drop is a good tool to make you faster, and in combination with shortcuts, you’ll be even faster.

 

To get all LV developer in my team to use the same shortcuts, I push the same shortcuts to everyone, but how do you remember all the different shortcuts?

To solve that I made a small Quick Drop Practice application, feel free to play and modify it so it suites you.

And if you have time to improve it, upload your version :-)

 

How it works:

It reads your current QD BD Shortcuts, and adds them to an array.

It then opens an empty VI BD and asks you to drop a VI (e.g. Build Array), on the BD.

If you haven’t figured out the shortcut within 5 seconds, it shows the shortcut so you can memorize it.

After it find the right VI on the BD, it deletes it and moves to the next shortcut.

 

Have fun.

attachicon.gifQDpractice.png

attachicon.gifQD-Practice.vi

You have too much time(or quick tools) Mikael...

Link to post
Share on other sites
You have too much time(or quick tools) Mikael...

My job is to make sure my team works faster and more efficient, and also have more fun, I just need to add some high scores as well then we can have a competition :-)

  • Like 1
Link to post
Share on other sites
My job is to make sure my team works faster and more efficient, and also have more fun, I just need to add some high scores as well then we can have a competition :-)

Very neat.  How do you distribute the quick drop shortcuts to your team?  I've been using VIPM, I wasn't sure if there was anything else people use.

Link to post
Share on other sites

I use SVN :-)

It's so easy.

We have a shared LabVIEW 2012 repository, that all the companies LV computer check out into their LV 2012 folder.

TortortoiseSVN will of course complain that there are files in the folder, but that's fine.

 

In this repository I've not added all files under the LabVIEW folder, but most stuff under user.lib (where we have the companies common VIs, and of course OpenG) and instr.lib (where we all the shared instrument drivers, more than 100 lvclasses)

But I've also checked in all RCF files needed, the QD plugins and of course GOOP Development Suite.

 

To update the LabVIEW.ini file with QD shortcuts, we have a VI in the repository that updates the shortcut so everyone gets the same.

 

I found this way easier than vipm, to make sure all development system uses the right sets of VIs.

I suggest you try this, it's so easy, and has been working really good.

//Mike

Link to post
Share on other sites
I found this way easier than vipm, to make sure all development system uses the right sets of VIs.

I suggest you try this, it's so easy, and has been working really good.

 

The main problem with this (other than that you need to edit reuse code directly in user.lib, or vi.lib, which is what NI recommends now) is that when you have a new version of LV you now have a repository which has VIs saved in version X used for version X+1, X+2, etc. If you save them (because LV will ask you to after recompling, unless they have separation enabled), then when you want to update, you will get conflicts. If you want to edit the reuse VIs, then you have to do in the oldest LV version, which is reasonable until you get to a point where you want functionality which isn't in the old version. Then you have to decide to skip the functionality, stop using the old version or force the old version to only update to version X of the code.

Link to post
Share on other sites
I found this way easier than vipm, to make sure all development system uses the right sets of VIs.

I suggest you try this, it's so easy, and has been working really good.

//Mike

I'm also going to side on Yair with the version issue.  At times I've had up to 9 versions of LabVIEW installed on my machine at once.  Unless you have a separate folder (or repository) for each version of LabVIEW there are going to be some issues for me using it.  And if you do have a separate location for each version then, when there is some bug fix I now need to fix it in each location.

 

Also I don't know how I feel about editing a users LabVIEW.ini.  On the one hand it should be no different then adding tools menu items, or quick drop functions, but for some reason I feel like the LabVIEW.ini is a place for a user to customize LabVIEW the way they prefer it.  What about the dreaded Auto Tool argument?  Am I to force all developers to not use Auto Tool (or force them to use it)?  Sure the majority of the settings we can all agree on (insert auto-feedback, terminals as icons, separate compiled code), I'm just thinking about the few that are user specific.

 

I also like the fact that I can take one VIPC file which can contain all internal and external reuse code, and settings, and take it to a computer that is offline.  There are many times where a PC will be in an environment where internet is not an option and bringing reuse tools and components (as well as SVN) are difficult.  Now I just grab one VIPC which is a snapshot of the reuse used on a project.  This is also great for configuration management because years down the road I can say exactly what VIs were used from the user.lib.  I guess SVN could do that too with revision tracking so that's not as big of a deal.

 

I'm glad it works for you but there are too many reasons for me to not use SVN for these types of changes. 

Link to post
Share on other sites

Yes, I do have a repository for every LV version :-)

Also every time I release/build an exectutable, I tag both the Project Folder (e.g. MyTestSystem-PN:123546-Rev:C12-2012-05-03) and also my LabVIEW repository (LabVIEW2012-2012-05-03-MyTestSystem-PN:123546-Rev:C12), that way I can alwasy get back to the environment I had when I did the build.

 

In case you don't have an internet connection, I would go with a VIPM package.

 

For the LabVIEW.ini file, we only update shortcuts to use a company defined shourcut list, but the VI we run to update the LabVIEW.ini file also updates all your prefered settings.

So the user selects his name in a drop down list and then it will configure all his LabVEIW.ini files to his taste.

Yes I did mean all, this is how my LV folder looks like.

 

post-941-0-37545400-1367544109.png

 

 

 

Link to post
Share on other sites

If anybody have time to update it and make it better and more fun/addictive to use, please feel free to share.

I thought about adding it in the Project Secondary provider start-up VI, so the users have to get X of Y correct QD placements within z seconds, before it lets then continue using LabVIEW.

Maybe depending on their score, they'll need to do it more often :)

 

So suddenly when they do a LabVIEW2012-folder update, they get this function installed automatically.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By awang_synovus
      Name: RCF LVS Conversion Toolkit
      Submitter: awang_synovus
      Submitted: 20 Mar 2015
      Category: *Uncertified*
      LabVIEW Version: 2009License Type: BSD (Most common)



      Hi Everyone,
       
      We have recently developed a toolkit that allows you to use Quick Drop plugins in Right Click Framework or LabVIEW Speak platforms.
       
      Named RCF LVS Conversion Toolkit, this toolkit provides an easy solution for JKI Right Click Framework (RCF) and LabVIEW Speak (LVS) lovers who want to use a quick drop plugin in RCF or LVS.  Now, you wont be disappointed when you see a useful plugin not written in your favorite platform's plugin format.
       

       
      Procedures are simple:
       Open the toolkit by going to Tools Menu >> Synovus >> RCF LVS Conversion Toolkit...  Select the target Quick Drop plugin VI  Type the command name in Right Click Framework or LabVIEW Speak  Click OK  
      Now you can use the Quick Drop plugin in Right Click Framework or LabVIEW Speak platform
       
      Features:
       Automatically converts a QD plugin to RCF or LVS plugin format  Warns the user if repetitive commands are installed.  Provides an instruction as user clicks help button.  Helps the user navigate to the plugin folders (LVS, QD and RCF)  Modifying the functionality in Quick Drop VI will automatically update the functionality in Right Click Framework or LabVIEW Speak  
      Please let me know if you have any questions. Suggestions and comments are welcome 
       
      Note: RCF and LVS only update their lists of commands at startup. If you use the RCF LVS Conversion Toolkit when RCF and LVS are open, please restart these platforms.

      Click here to download this file

    • By awang_synovus
      Hi Everyone,

       

      We have recently developed a toolkit that allows you to use Quick Drop plugins in Right Click Framework or LabVIEW Speak platforms.

       

      Named RCF LVS Conversion Toolkit, this toolkit provides an easy solution for JKI Right Click Framework (RCF) and LabVIEW Speak (LVS) lovers who want to use a quick drop plugin in RCF or LVS.  Now, you wont be disappointed when you see a useful plugin not written in your favorite platform's plugin format.

       



       

      Procedures are simple:

       Open the toolkit by going to Tools Menu >> Synovus >> RCF LVS Conversion Toolkit...
       Select the target Quick Drop plugin VI
       Type the command name in Right Click Framework or LabVIEW Speak
       Click OK
       

      Now you can use the Quick Drop plugin in Right Click Framework or LabVIEW Speak platform

       

      Features:

       Automatically converts a QD plugin to RCF or LVS plugin format
       Warns the user if repetitive commands are installed.
       Provides an instruction as user clicks help button.
       Helps the user navigate to the plugin folders (LVS, QD and RCF)
       Modifying the functionality in Quick Drop VI will automatically update the functionality in Right Click Framework or LabVIEW Speak
       

      Please let me know if you have any questions. Suggestions and comments are welcome 

       

      Note: RCF and LVS only update their lists of commands at startup. If you use the RCF LVS Conversion Toolkit when RCF and LVS are open, please restart these platforms.
    • By MikaelH
      Is it just me that’s annoyed of the QD Insert item on wire function?
      If you have a diagram like this below, and you like to add a +1 here:

      The result becomes like this:

       
      Enough is enough, I can't live without this feature but I tweaked it so it actually works.
      Or at least it seem to work, please feel free to test it.
       
      Place the attached VI in the Plugin folder:
      ..resourcedialogQuickDropplugins
       
      Update the Insert.vi plugin and add this Sub VI here:
      Insert_GuessInsertPoint.vi
      (I've updated this sub VI)
      Did it work for you?
      Cheers,
      Mike
       
       

    • By bbean
      This Quick Drop (QD) plugin complements the functionality of the built-in QD plugin (CTL-Space-CTL-D) by wiring between selected controls, indicators, constants, and SubVIs.   

      Default Shortcut - [W] Normal Operation Wires selected nodes in left to right order.  Attempts to connect any common unwired terminals in between the far left and right nodes by checking the datatype, Name, or Caption. Holding Shift and the Shortuct: Wires controls to unwired far left Node terminals and indicators to unwired far right node terminals.     This is just something I put together as my first attempt at a Quick Drop plugin.  Something similar has been done previously to wire the corners of subVIs using the right click framework by user JCC_(SK): RCF Plugin - Wire Nodes by Corner - https://decibel.ni.com/content/docs/DOC-8386 . Code for this plugin was developed prior to knowledge of the JCC_(SK) RCF code and probably doesn't function as well since it hasn't been tested thoroughly. However this plugin is for quick drop and has some added capability to wire up all like terminals but can suffer from potential overzealous wiring. Just delete extra wires if necessary. Thanks to the NI guys for creating the QD template with good instructions.  Someone may have done this already but I'm putting this out for comment anyway.   <a href="http://www.screencast.com/t/PZhMafM2">WireAndConnectVideo</a>   http://www.screencast.com/t/PZhMafM2  
    • By spaghetti_developer
      Hi ALL,
       
      I've got some plugins for the quick drop built with LV2009. I used them many times. Now I'd like to used them on my labview 2010 and labview 2012 but I can't find the right location where to copy them! Where I have to copy them to be able to use them while I'm developing?
       
      Thank you guys in advance!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.