Phillip Brooks Posted January 10, 2009 Report Share Posted January 10, 2009 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... Quote Link to comment
crelf Posted January 10, 2009 Report Share Posted January 10, 2009 QUOTE (Phillip Brooks @ Jan 9 2009, 01:42 PM) 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 don't think you can get the context help window contents to update without loading the VI into memory. Here's something I used once to get the info of a subVI into the context help window: http://lavag.org/old_files/monthly_01_2009/post-181-1231529544.png' target="_blank"> Then the context help window will update when the user mouse-overs the Boolean. It's kind-of a hick, but it worked for the situation I was in back then. Quote Link to comment
Darren Posted January 10, 2009 Report Share Posted January 10, 2009 QUOTE (Phillip Brooks @ Jan 9 2009, 12:42 PM) 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 don't know of a way to exactly reproduce the Context Help window contents based on VI path only, but the private App methods "Get VI.Description", "Get VI.Title", and "Get VI.Icon" can get you pretty close. All of those methods take a file path input and do not require opening a VI reference. -D Quote Link to comment
Phillip Brooks Posted January 21, 2009 Author Report Share Posted January 21, 2009 QUOTE (crelf @ Jan 9 2009, 02:33 PM) I don't think you can get the context help window contents to update without loading the VI into memory. Here's something I used once to get the info of a subVI into the context help window: Then the context help window will update when the user mouse-overs the Boolean. It's kind-of a hick, but it worked for the situation I was in back then. This works fairly nice. ( see picture). I wish there was an Application method or property that would allow me to set the object of the context help so that I could specify a VI from MY tree based browser (like the Project Window does) Product suggestion entered... Quote Link to comment
Antoine Chalons Posted January 21, 2009 Report Share Posted January 21, 2009 QUOTE (Darren @ Jan 9 2009, 10:05 PM) I don't know of a way to exactly reproduce the Context Help window contents based on VI path only, but the private App methods "Get VI.Description", "Get VI.Title", and "Get VI.Icon" can get you pretty close. All of those methods take a file path input and do not require opening a VI reference.-D Here is a VI that gets VI name, icon and description and puts these into a picture control. I'm not sure it can be put into the help windows using functions from the Help palette or maybe by saving the picture into a file and feed the file into the windows but I think it's not really nice... Quote Link to comment
Phillip Brooks Posted January 21, 2009 Author Report Share Posted January 21, 2009 QUOTE (Antoine Châlons @ Jan 20 2009, 10:14 AM) Here is a VI that gets VI name, icon and description and puts these into a picture control.I'm not sure it can be put into the help windows using functions from the Help palette or maybe by saving the picture into a file and feed the file into the windows but I think it's not really nice... Looks good, I actually started working on something similar, then realized I would want to make an XControl that would take care of resizing the description like the NI context help. I realized I was going overboard, considering the tool I'm working on is a temporary one to help developers selectively compile VIs, LLBs or folders (without subfolders). I even started to look at how to shrink and grow the parts of the image like the real thing. You can export the interface for the VI and then play around with the 'wisker' and terminal locations to replace the full name with an index and add the datatype info below when the window is made very narrow. This is about as far as I got... http://lavag.org/old_files/post-949-1232466601.vi'>Download File:post-949-1232466601.vi Quote Link to comment
Antoine Chalons Posted January 21, 2009 Report Share Posted January 21, 2009 QUOTE (Phillip Brooks @ Jan 20 2009, 04:50 PM) This is about as far as I got... Cool :thumbup: Thanks for showing that ! Quote Link to comment
Phillip Brooks Posted February 24, 2015 Author Report Share Posted February 24, 2015 QUOTE (crelf @ Jan 9 2009, 02:33 PM) This works fairly nice. ( see picture). I wish there was an Application method or property that would allow me to set the object of the context help so that I could specify a VI from MY tree based browser (like the Project Window does) Product suggestion entered... Added to The Idea Exchange... http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Set-quot-Context-Help-quot-using-VI-Reference/idi-p/3094027 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.