AusTEX

Agree completely. The RCF is a much faster, better, simpler interface. Too bad that JKI doesn't show it more love.

Anyone able to use the LVOOP Assistant with 2013? I can't get it to work - I get various errors when I try. I don't know if I didn't install something right or if something else is goig on.

Thanks for the info. I like the quick drop functionality as well, especially since it works every time. But I think the way the right click framework worked was so much better IMHO. I like being able to right-click on something and a list pops up of the functions that can work on what I've selected. Much better than having to memroize a bunch of shortcut keys or having to do more mouse clicks. Looks like I'll have to commit myself to drinking the quick drop kool-aid (I hope its grape).

I just tried to get the JKI right-click framework working in LV 2013. It seems very hit or miss on if it works, mostly miss. Anyone else using JKI RCF with LV 2013? Is it working for you?

I've been using Hg via TortoiseHg and really like it so far. I was able, with the help of especially Ton Plomp (thanks again Ton) to get merging working - and it works well. So far I haven't found any downsides to Hg.

Thanks for the great info Ton! I can now merge with no problems. Derrell

Has anyone using Mecurial been able to get merging working with Labview 2011? If so could you please walk me through how you did it? I've been trying to switch from SVN to Mercurial and getting merging working is my last hurdle. I've installed LVMergeHG and I have it specified as the tool to use for 3-way merging in the Hg global settings. When I open the TortoiseHg Workbench window I can see that I have a branch that I want to merge back into the main trunk. If I select the 'Diff to local..." option, LVDiff runs and I can see the to VI's I want to merge together. If I select the 'Merge with local" option I get a popup window, Prepare to merge, that shows info on the two VI's I want to merge. When I continue by clicking the 'Next' button I get the following: % hg --repository C:\Documents and Settings\D\Desktop\ZZ merge --verbose --tool=internal:fail 6 resolving manifests 0 files updated, 0 files merged, 0 files removed, 1 files unresolved use 'hg resolve' to retry unresolved file merges or 'hg update -C .' to abandon [command returned code 1 Mon Apr 09 16:33:47 2012] I can't see anything that looks like LVMerge is trying to run. I'm sure I'm probably doing some wrong or don't have something setup correctly. Any ideas?

Has anyone been able to get merging to work with Labview 2011? I'm trying to make the switch from SVN to Hg. I'm using TortoiseHg and I really like the concept of how Hg works. I have LVDiff working but I'm struggling with merging. I've installed LVMergeHG and I have it specified as the tool to use for 3-way merging in the Hg global settings. When I open the TortoiseHg Workbench window I can see that I have a branch that I want to merge back into the main trunk. If I select the 'Diff to local..." option, LVDiff runs and I can see the to VI's I want to merge together. If I select the 'Merge with local" option I get a popup window, Prepare to merge, that shows info on the two VI's I want to merge. When I continue by clicking the 'Next' button I get the following: % hg --repository C:\Documents and Settings\D\Desktop\ZZ merge --verbose --tool=internal:fail 6 resolving manifests 0 files updated, 0 files merged, 0 files removed, 1 files unresolved use 'hg resolve' to retry unresolved file merges or 'hg update -C .' to abandon [command returned code 1 Mon Apr 09 16:33:47 2012] I can't see anything that looks like LVMerge is trying to run. I'm sure I'm probably doing some wrong or don't have something setup correctly. Any ideas?

I'm look for recomendations, suggestions, experiences, etc. folks have had using remote repository hosting with places such as bitbucket or sourceforge, etc. I'm thinking of switching to remote hosting and I would like to hear how this has worked out for others. I'll probably be using Mercurial for my source code control. Are there any useful advantages to using places like Bitbucket as opposed to just having a remote directory out there in the 'cloud' somewhere for repository hosting?

I have an application where I have to call a third party dll to do some calculations. Sometimes these calculation can take a long time and I would like to be able to provide the user with a stop button so they can abort the calculation. So far I haven't been able to figure out how I can abort the dll before it is finished. I thought I might be able to use the taskkill command (this is on a windows XP machine). I can use the taskkill command to shut down any exe that is running but either it doesn't work for stopping a dll or maybe I don't have the syntax right. I also tried using the VI server to abort the vi that calls the dll but that didn't work either. Any ideas on how I can abort the dll?

Thanks for the great help! Now that I understand things better I have some playing around to do. Thanks again

Thanks for the info. I'm still trying to wrap my head around the normals array and how many points it takes to define 1 surface normal. You mention that the length of the surface normal must be 1 (except for special cases) so does this mean you must have two points to define a surface normal? If not, how is the length calculated?. If I have a square surface in the xy plane defined by four points with its center at 0,0 and I have the surface normal binding mode set to 'per primitive' then if I read your info right the surface normal should be relative to the center of the surface face at (0,0,0). So would the surface normal array be: an array with one element (0,0.1) or an array of two elements (0,0,0) and (0,0,1) or am I completely misunderstanding the whole surface normal concept?

I looked at the 'calculate normals.vi' and it looks like it might be specific to the example it is used in instead of a general purpose vi. I am clearly ignorant about the different mesh settings, especially when it comes to the normals array. So lets assume that I want to draw a square surface. I create a vertex array with the following points: 0,0,0 1,0,0 1,1,0 0,1,0 so this should give me a square in the XY plane and would define a primitive (am I correct so for?). If I set the ColorMode and NormalMode to 'Per Primitive' then should the ColorArray and NormalArray each contain just one element? Does the NormalArray need one or two points to define the surface normal? I would think there would be two possible values for the NormalArray depending if you are looking at it from the top or the bottom. Is this correct? Assuming you were looking at it from the top what does the NormalArray need to be? I would think if it were defined by one point it would be (0.5, 0.5, 1) or if two points it would be (0.5, 0.5, 0) and (0.5, 0.5, 1). If you were looking at it from the bottom the X and Y would be the same but the Z value would be -1. Also, if this is correct what importance is there to the Z value? Should it be 1 or 100 or does it matter?

Thanks for the info. The VI I used to calculate the normals is called 'calculate normals.vi' (I saved it using a different name) that I found in the 'Using Meshes.vi' example that ships with labview 2010. I'll have to go back and look at what that vi is doing. Do you know if there is a way to get the normal array info that is used with the built in functions for drawing cubes and cylinders? Also, can you be more specific about the other properties that make things nicer?

Here's the code in lv 2009 3d shapes 2009.zip