Bug in quick-drop insert

The recently introduced quick-drop features are simply great. Unfortunately, there is a small bug in the "insert" functionality:
Select the wire to the right of the branch point as shown here:
Now open the quick-drop dialog box, type "Increment" and hit Ctrl-i to insert the VI. You get the following result:
The VI is inserted to the left of the branch point instead of the selected part of the wire (as of LV 2010 f2 Windows 32-bit).
Fixing this would make the feature much more useful!
Thanks,
Andreas Hoenselaar

Hmm, I don't know off-hand if I'll be able to fix this, because of the following:
1. The selection list property returns a Wire reference...I don't
know if there's a way for me to figure out which segment of a wire is
selected.
2. The Insert method only takes a Wire reference...there's no way to
tell it a particular segment of the wire on which you want the insert
to take place.
I'll look into it, but I'm not hopeful it can be fixed without some changes to the internals of VI Scripting...
Thanks for the bug report.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Similar Messages

Duplicate Quick Drop Item Names

So at NI Week Darren showed off some neat Quick Drop functions. I asked a question about how do I add items from my user library. The answer was it already does this automatically. But when I went to my quick drop search it couldn't find a few items I was looking for. After some testing I now realize that's because there exists on the palette two seperate VIs with the same name and Quick Drop appears to be picking one.
So is there a way to support having multiple quick drop functions to VIs that are on the palette? Is there a way possibly to specify the relative (or absolute) path to the VI I want to drop? At least then I can create a short hand command to bring up the function I want.
The two functions I've seen this on is the the "Wait (ms)" and the "Enqueue Element". OpenG has made a very nice Wait function with the option to pass through errors, and abort on an occurance. But unfortunatly it is named the same as the native function. Internally we have also implemented a wrapped function for the Enqueue Element function and given it the same name. We can rename our function to be something else like "Enqueue Element Hooovahh Edition" but we can't go around renaming OpenG functions. Thanks.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Okay so I believe the issue is not the name of the VI. You see the name of the OpenG VI is actually "Wait (ms)__ogtk.vi" But this isn't what the quick drop will index as the name. Quick drop indexes the name of the window if it is different then the name of the VI. So if you go to the Window Appearance on the OpenG VI you'll see that the Window Title is "Wait (ms)" which is the same name as the native wait primative.
To demo this I've attached two VIs. One named "Wait (ms)2.vi" and "Wait (ms)3.vi" paste them into your 2012 user.lib, then run the Refresh Palette (or restart LabVIEW). You'll now see both VIs under the user library category. But when you go to quick drop and type "Wait (ms)" you only see the primative and number 2 but not 3. This is because the native wait comes up and not the "Wait (ms)3.vi" which has the same window title as the native VI.
Another way to demo this is just to install the OpenG Timing functions then go to quick drop and try to drop the OpenG Wait, or Tick Count. Both of these are quite handly to insert onto a error wire but quick drop can't do that at the moment.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
Attachments:
Wait ms User.lib.zip ‏9 KB

Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

Hi all. Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop). This really slows things down! Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini. Has anyone seen similar, and/or any hints towards a solution?

Jeff-P wrote:
As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini" might indicate that the labview.ini file cannot even be created... strange...
LabVIEW Champion . Do more with less code and in less time .

Fax and modem via Drop & Insert card (VWIC 2MFT-E1-DI)

Currently installing pair of 2610XM rtrs with Drop & Insert cards (VWIC 2MFT-E1-DI) between them.
At each side there is PABX connected via E1 to Drop&Inser card, and 2Mbs leased line between locations.
Configured 15 CH for data and 15 CH for voice.
Data works fine.
Voice services work fine as well, BUT!!!
- When trying to use analog modems between locations its not working
- When trying to send fax between locations, its hardly working (i.e. 1/10 success & even then copy is hardly readable).
All problems not present when I bypass routers and 2Mbs leased line with 120Ohm cable.
Any knowledge about similar problems?
Any tip for sorting this kind of problems, or this is by default behavior for such setup?

Thanks for tip, sorry for delay in reply (I was on leave).
re synchronization, it is properly synchronized (as you can see in output attached.
All other phone services/functions (standard voice calls, CallBack, CLIP etc.) and data transfer is working fine. If any problems with link sync I suppose there should be some problems with those as well.
rtr#sh controller e1 0/0
E1 0/0 is up.
Applique type is Channelized E1 - balanced
Description: Connecton to 2Mbs leased line
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20011015, FPGA: 11
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (530 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 1:
! each Interval equals 900 Secs (15 min)
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 2:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
! etc, etc. Data in Interval XX:

Quick drop window issue

The Quick Drop window is now expanded (see below) and I don't know how to return to its original size. What should I do ?
Message Edité par chilly charly le 08-31-2008 04:29 PM
Chilly Charly    (aka CC)
         E-List Master - Kudos glutton - Press the yellow button on the left...
Solved!
Go to Solution.
Attachments:
Quick Drop issue.png ‏26 KB

Ben a écrit: [...] let me guess! ctrl-T ?
Missed !
I have gone through all combinations without "succes"
Chilly Charly    (aka CC)
         E-List Master - Kudos glutton - Press the yellow button on the left...

Drop insert in receiver system with multiple clients

Hello,
does TDMS handle drop-insert technology in a multiple client receiver system automatically?
What can be the impact for the other clients when they are working while data deletion in the
receiver client?
Regards Karlheinz

Hello Karlheinz,
Good, question is straight and clear now.
please refer to steps mentioned in oss note 1433553 to make sure that TDMS should not consider drop_insert in TDMS migration.
Regards,
Amit Sharma
Solution
You have the possibility to set a Global Parameter for setting the deletion
scenario to overall array delete. In the following a description of the
proceeding.
Check if the global parameter GLOBAL_NO_DROP_INSERT exists
and that it is set to 'X' in the receiver system.
Call the Migration Server Overview(tcode cnv_mbt_tdms).
Expand the tree until you get your package.
Mark the package number so that it is highlighted.
In the menu click on Goto->Global Parameter.
When you have correctly positioned your cursor on a package number you
will see in the application toolbar buttons named with the exection targets,
system name and client number. You can also see if a connection to the listed
system is working (checkmark) or not (lightning).
Click on the button
'RECEIVER' to get the global parameters from the receiver system. This is where
the Global Parameter has to be set.
The global parameter entries will be
delivered empty and for the parameter you want to use you have to set the value.
An initial global parameter has no value in the column 'Client'.
Mark the row with the global parameter
'GLOBAL_NO_DROP_INSERT'.
Press button copy text (third button).
In the menu bar click on the drop-down box of the insert button and choose
the item 'Insert in new row' in the selection list (forth button from
left).
In column 'Client' enter the client where you want to use the overall
scenario array-delete. If you enter the value 'ALL' then the setting is valid
for all clients in the system.
In the column 'Parameter Value (from)' enter the value 'X'.
Save your settings.
If the parameter already exist you have to check whether the correct
client is set. If the column 'Client' includes the deletion client or the value
'ALL' then no further settings are required. Otherwise you have to copy the
Global Parameter as previously described and change the value in the column
'Client' with your deletion client. Take care that the value in column
'Parameter Value (from)' is 'X'.
From now on the generation of deletion
programs will use this information to create the deletion programs with deletion
scenario ARRAY-DELETE.

Ship Quick Drop Object Shortcuts with LabVIEW

In my daily work, I'd guess that over 90% of the time I drop something with Quick Drop, I use an object shortcut name ('cs' for Case Structure, 'rn' for Property Node, etc.):
You can configure object shortcuts by clicking the Configure button in the Quick Drop window. I've often suggested that people download and use my Quick Drop Palette Object Shortcuts for Right-Handed Developers to be able to drop most objects without ever having to move the left hand from the keyboard and the right hand from the mouse.
But in order for you to benefit from having object shortcuts, you either need to (1) create your own or (2) download mine from the link above. Neither of these options are particularly discoverable, nor do they make it easy to get started with the feature.
I propose that NI start shipping a pre-defined set of Quick Drop object shortcuts with LabVIEW so that everybody can have access to them from the start.

EWiebe wrote:
Good Idea.
Thanks! Please kudo my good idea.
EWiebe wrote:
If you select an item in quick drop box, it should show in quick help (CTRL+H) the standard short information about this item.
This idea has already been posted here. Please go kudo that one, too.

Why quick drop don't pop out with CONTROL SPACE in Labview 2010

I get can quick drop out from the menu, but not from CONTROL + SPACE.
What gives? Is there any setting to activate? Did you encounter this issue before?
I use Labview 2010, Windows 7, Acer laptop.

The setting is at Ctrl+. But it's not working.
I change it to Ctrl+', and typing Ctrl and ' works.
Well at least now I know how it works

[ANN] Find Static Events Quick Drop Plugin

Hi,
Just added a quick drop pluging over here (.ogp).
It will list all static events linked to a selection of controls, indicators, terminals, locals or static control references.
Hope it's usefull to someone.
Wiebe.

Christie wrote:
Hi GerdW,
(Tongue in cheek) I don't like terminals! Whenever I need to copy a piece of code, terminals get duplicated. I move all my terminals off to the right of the diagram of my main VI, except for booleans that are used in event structures. Whenever I need to show a hidden control, I know where to find the terminal... sort of.
Well I guess I don't use them much in subVIs, but in front end VIs it would really help a lot if it was easier to create local variables for the 20 configuration input controls or sensor display indicators I've just created.
Cheers
Control click drag will copy without copying the terminal
CLA, LabVIEW Versions 2010-2013

LabVIEW 2011 quick drop ctrl-key shortcuts don't work

I've noticed that none of the Ctrl-Key shortcuts used in the Quick Drop menu work. For example, Ctrl-T doesn't move the terminal labels and Ctrl-R won't remove and rewire. Is there a hidden setting that I have missed?
Thanks!
CLD Certified

I am just now encountering the same problem, only renaming the INI file didn't do the trick like above. As a matter of fact, the INI key "QuickDropKeyboardShortcutMappings" doesn't even exist in either the renamed (bak) or the newly created ini file.
Since I have grown to rely on the handy QD shortcuts this is starting to really annoy me...
I have checked that I can open all the files in the respective LV version (using 2011+2013 and sometimes got these mixed up with the newly saved shortcut VIs when distributing them to all the 4 LV-Quickdrop folders (x86 and x64)).
Funny thing is, the VI lists in the QD plugins folder and the DQ window, shortcut tab, greatly differ, see pictures attached. Any hints? Otherwise I am going to reinstall since a repair didn't help either. Tried that already as well.
Attachments:
QDshortcutVIs_infolder.PNG ‏14 KB
QDshurtcutVIs_inQDwindow.PNG ‏20 KB

Starts with 15fps and quickly drops to 1fps

I don't know what changed... it has been working fine for the past couple of years. For the past couple of months my video starts with 15fps and quickly drops to 1fps -- I still receive 15fps. . I have feeling it is either my cable provider or my Vonage strangling my bandwidth (both are the same since day one) maybe some settings were changed. When I do a speed test...up and down numbers are average or above for my cable provider.
Quicktime is set to 1.5...T1/Lan etc.
iChat bandwidth limit is set to none (tried all choices).
Imac G5 1.8 Ghz Mac OS X (10.4.9) iSight/cable/Vonage lynksys RT31P2 /Airport express

Hi jw_17,
Have a look at this page http://www.ralphjohnsuk.dsl.pipex.com/page16.html
Most likely it it is a background process.
In addition to the culprits found when Tiger came out listed on that page also open up Activity Monitor and check how many Widgets are active (shutting them down is best).
Also check if a Print Monitor is listed as most likely this is Stuck and can be Force Quit from the button top left of Activity Monitor.
The other possibility is that SpotLight is Indexing.
11:10 AM Tuesday; May 8, 2007

Quick Drop - Non UI blocking / cancel while first loading

When first launching the Quick Drop tool it can take a while. This isn't a problem in itself, but the fact that you can cancel the loading or continue working in the background is. This is especially annoying if you launch it by mistake.
Not a major thing, just something that could be improved.

When first launching the Quick Drop tool it can take a while. This isn't a problem in itself, but the fact that you can cancel the loading or continue working in the background is. This is especially annoying if you launch it by mistake.
Not a major thing, just something that could be improved.

Quick Drop list won't update during search

My Quick Drop started acting up today. Normally, when I begin typing, the list under the search box will update to show all of the possible matches. This is no longer happening. It still tries to autocomplete the search field, but the list doesn't update. [screenshot attached]
I'm running LabVIEW 2009 SP1 on Windows XP 32-bit.
For what it's worth, LabVIEW crashed went on vacation early last Wednesday evening, just before I was
getting ready to leave for the weekend. When I returned to work this morning, Quick Drop was no
longer functioning properly. I don't know if these two events are
related, but I figured that it was a possibility.
I've tried rebooting my PC and renaming the LabVIEW.ini file and restarting LabVIEW with a fresh configuration, but no luck.
Any help would be greatly appreciated!
Solved!
Go to Solution.
Attachments:
Quick Drop.JPG ‏29 KB

Thanks for the additional info. I don't think the window position issue is related to the search results updating issue. (Incidentally, there's a fix in LabVIEW 2010 for when there are bad window coordinates for the Quick Drop window stored in the INI file).
Anyway, I still think that NI-SEARCH is the culprit, but since you can't reliably repair your installation, we can't know for sure. So instead, I'd like you to try the following workaround:
1. Go in [LabVIEW 2009]\resource\dialog\QuickDrop and rename QuickDrop Launch Window.vi to be QuickDrop Launch Window.bak.
2. Save the attached QuickDrop Launch Window.vi below to [LabVIEW 2009]\resource\dialog\QuickDrop.
Now try Quick Drop and see if the results update properly. Basically, I modified the shipping version of the main Quick Drop UI to use the old LabVIEW 8.6-style of matching results instead of the NI-SEARCH mechanism. Let me know if this fixes the problem.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman
Attachments:
QuickDrop Launch Window.vi ‏103 KB

Quick drop list doesn't come up anymore :( LV2009f2

My quick-drop list doesn't come up anymore when I press ctrl-space. When I initially press ctrl-space (after loading LabVIEW) my machine behaves like it is loading the drop list (LabVIEW lags, and my hard drive thrashes for about a minute), but no drop list appears. My computer is kinda slow and outdated (hense the long inital load times of the drop list) so that may be the issue. I'm running a 1.6GHz Centrino w/ 1.5GB of ram and Windows XP SP3.
I've tried rebooting. I was using the drop list quite a bit before it stopped working. I would like to avoid a full reinstall of LabVIEW over this.
Any advice?
Thanks!
-Nic
Solved!
Go to Solution.

Just grasping at straws but...
In the LV .INI file there is a line
"QuickDropPosition="
That apperas to save where the QD window waas when last used. Maybe yours is set for an off-screen position.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Quick drop demonstration video

Hi,
Whenever I've attended a LabVIEW event it always seems that the inevitable "wait...how did you do that?" question comes from the audience when an instructor is demonstrating quickdrop.
Does anybody know if there are any videos online that we could reference when attempting to learn quick drop? So we can practice along.
Thanks,
Solved!
Go to Solution.

Here is a 45-minute video that I put together for Virtual NI Technology Days. It covers a ton of tips and tricks for faster LabVIEW development.
http://www.ni.com/webcast/3311/en/
If you want to skip to the good stuff, I talk about Quick Drop for 15 minutes in this presentation. Start at 1:38 for that.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Bug in quick-drop insert

Similar Messages

Maybe you are looking for