Darren's Weekly Nugget 05/04/2009

One of the nifty features of LabVIEW 8.6 was the ability to edit the properties of multiple objects at the same time.  Most of the literature on this feature focuses on editing front panel objects, but did you know you can edit the properties of block diagram objects as well? 
For most diagram objects, the property list is pretty limited (or nonexistent). For the functions above, the only properties you can change are the adapt to source option on the Output Configuration of the functions, and whether or not the functions' labels are visible.  There are other objects (particularly constants) with more useful configuration options.  For example, you can change the items in multiple enum and ring constants at the same time.  For string constants, you can change several formatting options.
How has the ability to edit properties of multiple objects (either FP or BD) been particularly useful to you LabVIEW 8.6 users out there?  And what properties would you like to see be editable on multiple objects that aren't there yet?
Message Edited by Darren on 05-04-2009 04:06 PM
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman
Attachments:
diagram_select.png ‏2 KB

Thoric wrote:
I created a mock-up of my application's panel (one of them, anyway) that has 48 identical controls within a large tab of an otherwise empty vi. It uses the same type-def for the controls. I tried using multi-property, and it worked with lightening speed! So, on the second tab pane, I created another 48 controls, from a second type-def. I tried multi-property for this new set of 48, and it worked, but slower. I re-selected the first 48 controls, and although it worked again, it was slower still.
So I created a third tab pane (my application has six panes by the way), and another 48 controls. Now it's starting to grind to a halt. Multi-select takes a long time to populate the Properties window, and a good long time to affect any changes too. A disproportionately long time. In fact, as I look at it now, LabVIEW has frozen
I do get trouble with my LabVIEW installation, with things like Quick Drop crashing occasionally, so maybe this slow behaviour won't be seen by others?
(Actually, while I've been writing this and playing with the multi-property tool, LabVIEW has frozen on me three times. I wonder if something more serious is amiss...)
Thoric,
I tried multi-select properties on 48 controls on the UI you gave, and I didn't see any of the slowness you've described (running a 2.4GHz(x4) quad core with 4 GB RAM here).  The first launch of the properties page took a few seconds, but each launch after that was very quick.  And applying the changes only took a few seconds.  I also tried the same operation in the LabVIEW 2009 beta and saw pretty much the same speed.
Also, I've never seen Quick Drop crash.  Do you have problems with other applications on your computer besides LabVIEW?
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Similar Messages

  • Darren's Weekly Nugget 06/15/2009

    One of my favorite features of LabVIEW 8.6 is Linked Tunnels.  I can't believe I haven't written a nugget about these yet!  In case you haven't heard, wiring tunnels in multi-frame structures is a lot easier in LabVIEW 8.6:
    See those tiny white triangles on outer edges of the string tunnels?  Those indicate the input/output tunnels are "linked".  There are two equally awesome use cases for linked tunnels:
    You are adding a new pass-through wire on an existing case or event
    structure that already has a bunch of frames.  When you pass the wire
    through one of the diagrams, if you right-click the output tunnel you just created and choose Linked Input Tunnel > Create & Wire Unwired Cases
    to link the input and output tunnels that bookend that wire, it will
    automatically wire up those tunnels in every other frame of the
    structure.
    You are adding a new frame to an existing case or event structure that already has linked tunnels.  When you add the new frame, all linked tunnels will already be wired together on the new diagram.
    I like this feature so much, I tried to figure out a way to show it off in my NI Week 2008 keynote demo.  But since Tim only gave me 10 seconds to write my VI, I wasn't quite able to squeeze it in. 
    Message Edited by Darren on 06-15-2009 04:54 PM
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    Fantastic!
    This is a great feature that I was not aware of.  Thanks Darren. 
    Using this feature when creating State Machines or Event Structures will be very useful and highly appreciated.
    You should definitely show this during NI Week.  This is a feature that has been long awaited....  (by me)
    RayR

  • Darren's Weekly Nugget 03/30/2009

    Here's a quick tip when dealing with path data types.  Sometimes we have to deal with paths that have a value of <Not A Path>.  A value of <Not A Path> can be formed in many different ways...one way might be if you're trying to build a path with the Build Path function, and you accidentally wire an empty string into the "name or relative path" input.  If you want to test how your code handles a value of <Not A Path>, it's not as simple as typing "<Not A Path>" in a path constant or control.  You must operate click the little path symbol on the left side of the control/constant and change its value from "Valid Path" to "Not a Path":
    If you try to type the text "<Not A Path>" into the path control/constant, LabVIEW treats that value as a relative path to a folder/file named "<Not A Path>", which is *probably* not what you were wanting to check.  The Not A Number/Path/Refnum? function is the easiest way to programmatically tell if a path value is truly <Not A Path>.
    Message Edited by Darren on 03-30-2009 06:12 PM
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman
    Attachments:
    not_a_path.png ‏3 KB

     Darren said:
    You must operate click the little path symbol on
    the left side of the control/constant and change its value from "Valid
    Path" to "Not a Path"
    As
    an integrator, we've gone almost exclusively to system controls to keep
    things from, dare I say, "looking like LabVIEW".  Any way to do what
    you've suggested with the System Path Control?  I can get the <Not A
    Path> type into the control, but not by copying / pasting.  Run the
    attached VI.  Notice that when you click in the first path control, it
    highlights "<Not A Path>".
    -Jason
    Message Edited by LabBEAN on 03-31-2009 02:05 PM
    Certified LabVIEW Architect
    Wait for Flag / Set Flag
    Separate Views from Implementation for Strict Type Defs
    Attachments:
    Not A Path -- System.vi ‏6 KB

  • Darren's Weekly Nugget 08/03/2009

    One helpful LabVIEW feature that add-on developers frequently utilize is the fact that you can place VIs in the [LabVIEW]\project folder to create new entries in the Tools menu.  Did you know that you can also place VIs in the [LabVIEW]\help folder to have them appear in the Help menu?  Or the even less well-known [LabVIEW]\wizard folder to have them appear in the File menu?
    This functionality has been around for a long time, and there are even some private VI Server properties that help you determine the VI from which the menu option was selected.  In LabVIEW 2009, I added a VI to vi.lib that will give you this information (it basically just wraps the private properties).  Check out [LabVIEW]\vi.lib\VIServer\Menu Launch VI Information.vi.  This VI will return the App reference of the owning app for the VI from which the menu item was selected, along with the VI name.   You can then wire these items to an Open VI Reference function to gain access to the VI from which the menu item was selected.
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    I will reply myself
    Checked/works in LabVIEW 8.6:
    File and Help - menu: Tools>Options> Menu Shortcuts
    There is no such option for Tools menu 
    And observed behaviour: defined this way shortcut is active only in this session LabVIEW - shortcut disappear after LabVIEW restarting, item in menu still existing  
    Message Edited by Zbigniew StS on 01-07-2010 03:16 PM
    Regards
    Mikrobi (Zbigniew St. Sobków)____________________________________________________________
    "You can lead a horse to water, but if you can get him to float on his back you've got something."

  • Darren's Weekly Nugget 08/24/2009

    Does it bother you that you have to use values of 0, 1, or 2 to set the disabled state of a control/indicator?  It never really bothered me, I guess because I just got used to it.  But lots of people think that it should be an enum instead.  Well, I don't know how it didn't make it into the Upgrade Notes, but have you seen the Disabled Property in LabVIEW 2009?
    So now you don't have to do a number-to-state translation in your head whenever looking at the Disabled property.  Of course, you're also losing a lot of diagram real estate.  I'll let you decide if it's worth it or not.  As for existing code, your old U8 constants will stick around, and you'll see a coercion dot on the property:
    I wouldn't worry about the coercions, they're not hurting anything.  I don't plan on going through all my existing apps to change them over, although I will probably start using the enum in new apps.
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    Once upon a time it was policy of NI to remove as much enums from the IDE as possible, since they all need to be localized for every IDE language, something that was basically not possible, so I wonder how this looks in the french or german version of LabVIEW.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • Darren's Weekly Nugget 08/31/2009

    A while back, I wrote a blog post about my preferred Tools > Options settings.  Today I'm going to highlight a few of those, and some others, that make my life easier as a LabVIEW programmer.  Note that I used LabVIEW 2009 to compose this list, so the organization might be slightly different if you're using an older LabVIEW version:
    Front Panel > General > Connector pane terminals default to Required: CHECKED - This option often saves me some debugging time that I used to spend discovering instances where I forgot to wire a new terminal on a subVI I've written.
    Block Diagram > General > Auto-insert Feedback Node in cycles: UNCHECKED - Every time I'd see a Feedback Node magically appear in my code while wiring, I didn't want it there.  With this option unchecked, Feedback Nodes only appear if I actually drop them.
    Block Diagram > Wiring > Enable auto wiring: CHECKED - Gets the wiring right 95% of the time, and I just press the spacebar the other 5% of the time to drop the object without auto wiring.
    Controls/Functions Palettes > Loading > Load palettes during launch - Assuming you haven't been hiding under a rock for the past year, you should already know that this is the option you must select if you want Quick Drop to be immediately usable after launching LabVIEW.
    Environment > General > Skip Getting Started window on launch: CHECKED - Just saves me some launch time speed that I lost with the Load palettes during launch selection.
    Environment > General > Maximum undo steps per VI: 99 - I don't think I've ever gone back 99 steps, but I know I've gone back more than 8 (the old default value) many times, and I've probably gone back more than 30 (the new LabVIEW 2009 default value) a few times too.
    Environment > Saving VIs > Enable automatic saving for recovery: CHECKED - This option has really saved me a few times when LabVIEW decided that it just couldn't go on anymore.
    Source Control: ENABLED -We use Perforce for source control in LabVIEW R&D, and it's really handy to be able to check in/out my VIs directly from the LabVIEW project window. 
     Are there any other Tools > Options settings that make your life easier?
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

     Good nugget Darren.
     The very first thing I do when I show up in front of the computer at a client site or installing a fresh version of LabVIEW is to set the Options.  
    I totally agree that the automatic feedback node should never be set as default.  As a matter of fact, it should be removed from the Options list.
    Darren wrote:
    Block Diagram > Wiring > Enable auto wiring: CHECKED - Gets the wiring right 95% of the time, and I just press the spacebar the other 5% of the time to drop the object without auto wiring.
     I've always disabled the auto wiring because of bad experiences with it with LV7.x  It was driving me nuts (which became a permanent condition)
    I didn't know the trick with the spacebar.  Maybe I'll try it again with LV2k9 when I get a chanceto work with it.
    Darren wrote:
    Controls/Functions Palettes > Loading > Load palettes during launch
    - Assuming you haven't been hiding under a rock for the past year, you
    should already know that this is the option you must select if you want
    Quick Drop to be immediately usable after launching LabVIEW.
    Unfortunately, I have been hiding under a rock...   A Unix based rock called VxWorks.  
    I always use the palettes and want them near.  I also right click to get the pallette.  I do sometime struggle with setting the palettes to my liking..  Although I do recall that we can copy some sort of ini file which will "copy" our settings from one PC to another and make that life easier...  I seem to recall  tst posting something about it.
    Darren wrote:
    Environment > Saving VIs > Enable automatic saving for recovery: CHECKED - This option has really saved me a few times when LabVIEW decided that it just couldn't go on anymore.
    Very important.  It's been useful a few times already.
    Darren wrote:
    Source Control: ENABLED
    -We use Perforce for source control in LabVIEW R&D, and it's really
    handy to be able to check in/out my VIs directly from the LabVIEW
    project window. 
    I also use Perforce at the moment...  or rather when coding with LabVIEW.

  • Darren's Weekly Nugget 08/17/2009

    Block Diagram Clean Up was one of the premiere features of LabVIEW 8.6.  It was a little rough around the edges at that time, but some great improvements have been made in LabVIEW 2009.  For example, you can now invoke diagram cleanup on a selected portion of your diagram.  If you have diagram objects selected, and you press Ctrl-U (or the cleanup toolbar button), only the selected items will be cleaned up...the rest of your diagram will remain unchanged.  Also, diagram cleanup in LabVIEW 2009 is a lot better about keeping your free labels within the same proximity of objects they were near before the cleanup.  It's still not perfect, but it's far better than the behavior in LabVIEW 8.6, which was to indiscriminately move all labels to the corner of their owning diagrams.
    So if you were not satisfied with diagram cleanup in LabVIEW 8.6, I think you should give it another try in LabVIEW 2009.  After all, that's what I'm doing. 
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    I used to frequently copy code to a New Untitled VI, do a clean up and paste the code back...  But yeah, now its pretty cool...
    Message Edited by NitinD on 08-18-2009 12:39 PM

  • Darren's Weekly Nugget 08/10/2009

    The Parallel For Loop is one of my favorite new features of LabVIEW 2009.  With most desktop computers containing two or more processors these days, it's nice that LabVIEW already enables us to write parallel code without a second thought.  But the Parallel For Loop takes things one step further by allowing us to configure some For Loops to run their iterations in parallel across multiple processors.  You can check out the link above for a complete description of the feature, but I figured I'd focus on one specific tip for using the Parallel For Loop that I think needs extra attention.  When you run the Parallel For Loop Detector (Tools > Profile > Find Parallelizable Loops...), it will detect all For Loops in your code that could potentially be parallelized.  You can run this option from the toolbar of a project to analyze all VIs in the project, or from the toolbar of a VI to analyze just that VI.  When you browse the results of this analysis, be careful about nested loops.  The Parallel For Loop Detector will detect *any* loop that could be parallelized, but as a general rule, you'll want to avoid parallelizing a loop that resides within another loop that can be parallelized.  This is because there is some extra overhead before and after the loop execution that is responsible for setting up the parallel iterations, then combining the results once the iterations are complete.  This overhead is negligible for a top-level loop because it only happens once.  But for a nested loop, that overhead will occur every time the nested loop runs, and the parallelism overhead may end up taking more execution time than just letting the loop run serially in the first place.  So I recommend sticking with parallelizing only top-level loops, or at the very least, benchmarking your code if you decide to parallelize nested loops.
    Message Edited by Support on 08-10-2009 02:09 PM
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    Cory K wrote:
    But are you saying you can have multiple processors working on a single loop?
    I didn't even think that was possible.... 
    YES!  If iterations of the loop do not depend on previous values it can be parallelized.  Thus it can have one CPU working on the i=0 case and another on the I=1 case if they don't depend on each other.  These are not loops executing in parallel, but the frames of the single FOR loop executing in parallel.
    It is a good question about unwrapping code in multiple parallel For loops.  I can see how the multiple unwrapping could cause problems with the optimization.  It is a good question about the general rules for nested loops.  For example if a loop of count N is inside a loop of count M what is the time for a large range of N and M in the 4 cases
    1. both N and M serial
    2. N parallel M serial
    3. N serial M Parallel
    4. both N and M parallel
    For the student,
    build a test harness for all 4 cases taking an input integer P and doing some significant calculation in a nested parallel FOR loop.
    produce 3 color image plots for N and M from 2 to 2^p by factors of 2, normalize the times for case 2, 3, and 4 to the times from case 1.  Plotted as a function of N and M all on the same Z scale for comparison.
    Bonus credit, run the code while stepping the number of CPUs used from 1 to 8....

  • Darren's Weekly Nugget 11/02/2009

    Are you familiar with LabVIEW design patterns?  Using a well-known design pattern for your application in LabVIEW can decrease your coding time, and decrease your maintenance time.  LabVIEW ships with several design pattern templates that you can access from the File > New... dialog:
    Some of the most common patterns include Producer/Consumer, Master/Slave, Queued Message Handler, and of course, the ever-popular State Machine.  For more details about standard LabVIEW design patterns, check out this LabVIEW Application Design Patterns presentation.  It's a few years old at this point, but still very relevant.
    And what about programming with LabVIEW Classes?  There are many object-oriented design patterns that are applicable to LabVIEW Class programming.  For more information, check out this document on the LabVIEW Community website.
    Message Edited by Support on 11-02-2009 12:24 PM
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    gchristi1 wrote:
    Having said that, I wish the NI people would improve the templates. When I took the CLD exam, I started with a template and spent too much time molding it to look like my template.
    Opinion? When you took the exam, was a native template of use to you?
    When I took the CLD exam, I did not use any of the shipping templates.  What specific changes would you recommend to make the NI templates better?
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Darren's Weekly Nugget 02/09/2009

    Shortly after NI Week 2008, I found out that NI employees could take the NI Certification exams.  Previously this was not allowed.  Once I found out, I took the CLAD, the CLD, then the CLA.  Don't worry, I passed them all. 
    Over the past few weeks, I've posted information on my LabVIEW blog detailing how I prepared for each exam.  I recommend checking out my articles before you plan on taking any of the LabVIEW Certification exams:
    Preparing for the CLAD
    Preparing for the CLD
    Preparing for the CLA
    -D
    P.S. - Check out past nuggets here. 
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    NIquist wrote:
    Just out of curiosity, why would NI not want their employees to be certified in the very products they sell and support???
    I'm not certain about this, but I *think* it was simply a manpower issue. Up until recently, they didn't have enough staff to grade exams submitted by both customers and NI employees.
    -D
    P.S. - I'm glad you like the blog!  I have tons of ideas for articles, it's just a matter of finding time to post them.  The certification exam prep articles were highly-anticipated though, so I knocked those out first. 
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Darren's Weekly Nugget 06/22/2009

    Today's nugget deals with gracefully closing a LabVIEW built EXE window.  Most everybody knows the trick of using the Quit LabVIEW function at the end of a built EXE to close its window.  In fact, you may have even included some extra logic, like with a Conditional Disable Structure or the App.Kind property, to make sure Quit LabVIEW doesn't run while you're developing and debugging your VI in the LabVIEW editor:
    Have you ever noticed, though, that sometimes when you quit a LabVIEW built EXE, you see a brief flicker of the toolbar?   This can happen if you have your VI set to have a dialog window appearance (so that there is no toolbar), and you run the Quit LabVIEW function after clicking the "Stop" or "Exit" button that you created on your VI's front panel.  In this case, the built EXE, upon going idle, will show a toolbar (with the Run button) for an instant before the panel closes.
    To avoid this toolbar flicker, you can make one simple change to the code above:
    By calling FP.Close, you are telling LabVIEW to hide the front panel of the VI/EXE first before exiting.  This way the extra cleanup that LabVIEW must do can occur without the front panel of the built EXE showing, and we never see the toolbar flicker.
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    Sebster:  Yes, it will work, but you should clear the error before you execute the code. Furthermore you will need to get the reference to the calling VI (or the top level VI).
    Darren: Thaks a lot for the hint, the FP.Close was really new to me. Maybe you adress the other side (splash screen while loading) in a further nugget.
    Felix
    www.aescusoft.de
    My latest community nugget on producer/consumer design
    My current blog: A journey through uml

  • Darren's Weekly Nugget 06/08/2009

    One of the little-known features of string controls is the Update Value while Typing option:
    With this option selected, a Value Change event will fire with the Event Structure any time a character is typed (or deleted) in the string control...this is different from the normal behavior of pressing Enter or clicking away from the control to commit its value.  Update Value while Typing can be very handy for UIs that require immediate processing of the value being typed.  One example I can think of is the password entry field on some websites that assesses the "strength" of your password as you type it.  Another simpler example that I've done several times in my UIs is keeping the OK button disabled until a valid value (i.e. non-empty, or unique) is typed in a string.
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    I think Partha is simply saying that he would like the combo box to have the same "Update Value while Typing" option that string controls have.  I agree that this would be handy...maybe Partha could write an entry in the LabVIEW Idea Exchange for this? 
    Quick Drop actually uses a Combo Box on its UI (I did this so I could utilize the built-in autocomplete functionality of the combo box).  The way I simulate the "Update Value while Typing" functionality with a Combo Box is that I've registered for a Key Down event on the Combo Box, and I update things appropriately when keys are pressed on the Combo Box...effectively implementing my own "Update Value while Typing".
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Darren's Weekly Nugget 04/13/2009

    In LabVIEW 8.6, I included a set of VIs in vi.lib\UserTags for assigning tags to objects in your VIs (or to VIs themselves).  Tags are basically just name/value pairs that you can assign to any VI or any object in a VI.  Tag names/values are persisted when you save the VI after assigning a tag.  There are several possible use cases for tags, here are just a few:
    Marking certain VIs with tags so they can be easily identified by plug-in frameworks.  For example I could assign a certain tag to VI Analyzer test VIs so that the VI Analyzer would not load any test VI that did not have this custom tag set.
    Including configuration information for controls/indicators on custom UIs to avoid having to synchronize with a separate database.  When I worked on the Simulation Interface Toolkit many years ago, I stored model parameter mapping information for front panel controls/indicators as tags in the controls/indicators themselves.  That way, if you renamed or deleted a front panel item, I wouldn't have to go searching in a separate database to figure out which object needed renaming or deletion...the parameter mapping information simply stuck around with the renamed control (or disappeared along with the deleted control).
    Assigning unique identifiers to front panel decorations.  This use case was discussed in this thread.
    Prior to LabVIEW 8.6, tags were only available with private VI Server methods...in fact, the VIs in vi.lib\UserTags wrap these private methods, with a few caveats attached:
     You cannot store refnum or LabVIEW Class data in a tag.
     Internally, I append "user." to the beginning of any tag name set by these VIs.  That way, we can be sure that user tags do not generate name conflicts with any existing internal NI tags that may already be set on VIs or objects.
    What other use cases are out there for VI/object tags?
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    Darren wrote:
    In LabVIEW 8.6, I included a set of VIs in vi.lib\UserTags for assigning tags to objects in your VIs (or to VIs themselves). 
    Let's see if I understood correctly.  The tags are assigned to objects within the VI and not to the VI itself.  Each object within the VI can have one or more tags assigned to it.
    How would someone access these from outside LabVIEW?
    R

  • Darren's Weekly Nugget 08/08/2006

    As of this morning, LabVIEW 8.20 was officially announced at NI Week 2006.  I am going to use the next few Darren's Weekly Nuggets to describe some features I personally added to LabVIEW 8.20.  These are the kind of features that (hopefully) make people say, "Whoa, cool!", yet aren't quite big enough to make it as bullet points on marketing material.
    For starters, I'll mention the Remove Breakpoints from Hierarchy utility that you will find in the Edit pull-down menu of any open VI.  Selecting this menu option will remove any breakpoints you have set in the current VI (i.e., the VI from which you selected Edit > Remove Breakpoints from Hierarchy), along with any breakpoints in the current VI's subVIs.  A summary dialog then comes up and indicates how many breakpoints were removed from each VI in the hierarchy.
    I've seen this feature request a number of times on the NI Discussion Forums, so I hope the word gets out to everybody who has wanted this feature in the past.
    -D
    P.S. - Check out past nuggets here.
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    hallelujah!  thanks to NI for listening!  I've been wanting that feature for sometime now. 
    2006 Ultimate LabVIEW G-eek.

  • Darren's Weekly Nugget 08/02/2010

    Just in time for NI Week, LabVIEW 2010 has released!  Over the next several weeks, my weekly nuggets will highlight some of my favorite features in LabVIEW 2010.
    Cool LabVIEW 2010 Features Part I:  Replace and Insert with Quick Drop
    Soon after I released Quick Drop with LabVIEW 8.6, one of the first requests was the ability to do Replace and Insert operations with Quick Drop instead of the palettes.  Well, it took a few releases, but we finally got it:
    Replace with Quick Drop
    Select one or more diagram objects, press Ctrl-Space to bring up Quick Drop, type a palette object name (or a project item if you have one or more LabVIEW projects open), press Ctrl-P, and all the objects you had selected on the diagram will be replaced with the object name you specified in Quick Drop.  And yes, it does do the replace "correctly" with Compound Arithmetic...
    Insert with Quick Drop
    Select one or more diagram wires, press Ctrl-Space to bring up Quick Drop, type a palette object name (or a project item if you have one or more LabVIEW projects open), press Ctrl-I, and a separate instance of the object you specified in Quick Drop will be inserted on each wire.  I also included special functionality when Ctrl-Shift-I is pressed.  I call this "Smart Insert".  With Smart Insert, a *single instance* of the object name you specify will be inserted on multiple wires.  As an example, if you select a refnum wire and an error wire, press Ctrl-Space, type "Property Node", and press Ctrl-Shift-I, a *single* property node will be inserted on both the error wire and the refnum wire.
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

    I would argue that the expected behavior for Ctrl-Space....Select....Ctrl-P for the 1/x function replaced by a Compound Arithmetic should be:
    =====> 
    not what it currently is:
    ====> 
    This, BTW, is what the "Replace" menu does, so there is no benefit really in using the Ctrl-HyperSpace projection (at least to me).
    And similarly for (-x) and x^2.

Maybe you are looking for

  • Can I stream the BT Sport app to my TV?

    Can I stream the BT Sport app to my TV? The BT Sport app is compatible with both Apple TV and Google Chromecast devices, allowing you to watch video from the app on your television. For either to work, the device on which you are running the BT Sport

  • I want to pick the Exp.GL A/c of GRN with the help of IR Doc.(INv.Verifica)

    Dear All,         CAn i know how can i pick the GL Account of GRN Doc.No.with the help of Invoice Doc.No.(Inv.Verification).From which table i can take these information. Please answer me immediately so that i can also reward point & the requirement

  • Tutorial on: Easy to use custom scrollbars

    Hey everyone i seen a few discussions around that people need customscrollbars i have now gathered to must easy to use out of the box project It works down to IE6 and works in all device - nicescroll $(function() {                    $("#thisdiv").ni

  • Transfering iTunes/iPod to a new computer

    Hello! I recently purchased a new PC and am trying to transfer all of my files from my old machine (Windows XP) to the new one (Windows Vista). I am wondering a few things... 1- is there a way to transfer my playlist names/content from my old compute

  • Can't launch executable from SQL Server Agent Job

    I'm trying to launch an .exe from SQL Server Agent Job and basically nothing happens. I created a job, with 1 step, type is Operating System (CmdExec), run as sql agent service account, and in the command box I typed "start notepad" (no quotes). The