-
Posts
899 -
Joined
-
Last visited
-
Days Won
50
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by Phillip Brooks
-
-
-
Block die-her gram
-
QUOTE (jpdrolet @ Jan 15 2009, 12:24 PM)
There are two types of shortcuts; lnk and url
Maybe my contribution to the Code Repository (Resolve Shortcut Path) will help ...
-
QUOTE (jpdrolet @ Jan 15 2009, 12:24 PM)
There are two types of shortcuts; lnk and url
Maybe my contribution to the Code Repository (Resolve Shortcut Path) will help ...
-
-
-
-
-
Top 25 Most Dangerous Programming Mistakes
LabVIEW programmers aren't as concerned as others about the security aspect, but these same mistakes can break your code ...
- Improper Input Validation
- Race Condition
- Untrusted Search Path
- Improper Resource Shutdown or Release
- Improper Initialization
- Improper Input Validation
-
Apparently, this was a very convincing video!
http://digg.com/apple/Blogger_Mistakes_Oni...cbook_Wheel_PIC
-
Does anyone know if there is a vi.lib/ function, method, or property that can be accessed that will return the Context Help for a VI by file name? The file would not be loaded in memory, I want to supply the full path to the file only...
I want to create something similar to the way a project will show the Context Help for a VI when you hover over the name...
-
-
-
I started playing around with DropBox before Thanksgiving. While I was at my parent's house over Christmas, I scanned some old family photos and uploaded them them via the DropBox web interface to my 'drop box'. I had already configured my home computer to mount DropBox in the "My Documents" folder and my wife asked me how I found time load the pictures into the computer when we got home
It's a very simple interface, and offers 2 GB storage for free. I haven't experimented with it yet, but they also support revisions for files. It is available for Windows, Mac and Linux.
I learned about DropBox from this blog.
-
I started playing around with DropBox before Thanksgiving. While I was at my parent's house, I scanned some old family photos and uploaded them them via the web interface to my 'drop box'. I configured my home computer to mount DropBox in the "My Documents" folder and my wife asked me how I found time load the pictures into the computer when we got home
It's a very simple interface, and offers 2 GB storage for free. I haven't experimented with it yet, but they also support revisions for files. It is available for Windows, Mac and Linux, and
-
-
-
I have a <user.lib> LLB that's about ten years old. It's been updated and recompiled without problems for all these years.
During analysis for an upgrade (from LV 7.0/TS 3.0 to LV 8.6/TS 4.1.1), I discovered that several of the VIs contained in this LLB use non-standard names (contain /\<>? characters). TestStand 4.1 would go into an endless loop and hang when trying to load a step pointing to a VI in an LLB with a non-standard OS name. This was reported to NI, and is fixed in TestStand 4.1.1.
I'm concerned about leaving these oddly named files 'as is'. I've read a few problems/rants on the NI forums with respect to NI's use of these non-standard naming conventions in LLBs, and have a fear (probably unnecessary) that support for the LLB may be dropped in a future version.
So....
I can rename the VIs. All calling VIs will break, and all TestStand sequences will error when run.
My sequence files are stored as INI text files, so I can perform a simple 'search and replace' to fix the calls.
How can I programmatically replace calls to these sub-vis from within a vi? I've been poking around in the 'optional' App methods and properties, but haven't found much. The only promising thing was Linker:Read Info and Linker:Write Info.
I renamed one of the offending VIs. I used Linker:Read Info and was able to evaluate a VI that calls the renamed VI. It appears that the Path and delimited name are the same for a VI that cannot be found.
I know what the old name and new name will be, and they will have the same path. I plan to leave the renamed files inside an LLB for now, and if the LLB construct goes away or I want to start using source control, I will use the LLB Manager to convert the LLB to a folder and be done.
There are references to the Linker: methods in the wiki entry for Pseudopath, but I can't figure out how the methods work
-
Someone on the dark side mentioned the MiMo yesterday. They had the same idea as me (touchscreen use).
There was a link to this review...
http://technabob.com/blog/2008/12/01/nanov...ands-on-review/
-
QUOTE (jdunham @ Dec 21 2008, 04:53 AM)
I ordered one of these last week. I'll share what I learn when it comes in. It can be powered by USB (no extra brick/wallwart)
(This might be a cool display option for a PXI chassis if running under Windows! )
The technology is called DisplayLink. You use a driver and USB connection to drive a monitor.
Instead of carrying an actual display, you could get a USB/DVI or USB/VGA adapter and then borrow a customer or site monitor as your second display.
-
-
QUOTE (Cool-LV @ Dec 21 2008, 08:17 PM)
I think you've confused everyone by using the word 'translucent' (wikipedia).
What you seem to be describing now are transparent regions. If you want to combine overlapping images with transparent areas, you would create a masks of the images to be merged...
Use the Create Mask (not in base package) function.
-
QUOTE (Aristos Queue @ Dec 20 2008, 03:38 PM)
The canonical solution is the static VI reference, introduced in the same version that the case structure optimizations went in.And, for the record, if you change the constant to a control then LV won't optimize it out -- at least, not in any version of LV that has shipped yet. It is entirely possible that LV could decide in a built application, where the Front Panel has been stripped out, if the bool is not on the conpane, then the case structure could be optimized. Not that I'm saying that change is coming... I'm just saying that you probably want to use a static VI reference.
I don't know how to tag your post, but I feel compelled to do so...
-
I'm upgrading a bunch of 7.0 code to 8.6. When I load a 7.0 VI that uses a case structure with a constant on the block diagram to disable code, LabVIEW converts the constant to a hidden control and reports a warning while opening.
I think a constant causes the contents of the unused case to be optimized "out". If you're creating a new VI in 8.6 and have used a constant, maybe converting it to a hidden control will help...
C program crashes after calling Labview dll, because Labview runtime
in Calling External Code
Posted
Cross-posted on NI
http://forums.ni.com/ni/board/message?boar...ssage.id=380475