PJM_labview

What are these things? I keep getting them quite often now (twice so far today). Typically happens when I try to close (or save) a VI belonging to a class. Also, they come in a group of 5-15 differents dialogs, and after that LabVIEW NEED to be closed (weird stuff happening otherwize). Edit: This is on LabVIEW 8.5 Note: In some instances, after these errors, some VIs becomes corrupt and are no longer compilable (see image below). PJM

How about like this. PJM

QUOTE(jdunham @ Nov 29 2007, 12:40 AM) I had a similar problem a while back. I could build just fine, but the build spec became uneditable (every changes I made broke the build). Recreating the project fixed it. PJM

QUOTE(TobyD @ Nov 27 2007, 08:35 AM) This is the right alt key on french keyboard. It allow access to more characters mostly "under" the numbers (see below). http://www.forlang.wsu.edu/help/kfrench.gif' target="_blank"> PJM

I could not agree more. PJM

I just came across this new search engine, and after trying it my first tough was: "why nobody though about organizing the answer this way before"! I my opinion, the organization ("document clustering") of the search results is very good. Now, if they could add some AJAX to make the tree more dynamic, this would be even better. PJM

QUOTE(Val Brown @ Nov 15 2007, 12:48 AM) I don't remember for sure, but probably in 8.2.1 (but it could have been in 8.5 too). I did not had any corruption. Restarting LV fixed it. PJM

QUOTE(TobyD @ Nov 14 2007, 03:51 PM) Yes, I have seen this 2 or 3 times already. Like you, I was not able to reproduce it. PJM

QUOTE(tcplomp @ Nov 12 2007, 09:36 AM) Incorrect answer. I start with a regular TAB size. The TAB resizing happens behind the scene. Resize the TAB and see for yourself. PJM

You mean like this? --------> Download File:post-121-1194887685.viLV8.5 PJM

Anybody has any idea what the error message below means? "Orphan Object will be deleted." I pressed CTRL + S then I got this error, then of course LabVIEW crashed. PJM Edit: This is in LabVIEW 8.5

Cool :thumbup: . I am looking forward to see these XNodes. PJM

I had the same problem. By error and trial I figure out that you have to change the icon of the help ability and the palette will display it. Just to be safe I typically put the icon I want in both the XNode and in the Help ability. If you don't have a help ability I think you can use the initialize ability icon. PJM

QUOTE(Tomi Maila @ Nov 5 2007, 01:33 PM) Well, I know by experience that you can call them from the DoubleClick ability. There are probably more but I don't know them. PJM

QUOTE(Tomi Maila @ Nov 5 2007, 05:37 AM) While I don't have a solution to your specific issue, I can confirm having seen LabVIEW preventing multiple call to abilities through the reply output. I also notice that some reply will be completly ignored. For instance, ReplaceSelf or AugmentSelf called from ResponToDrop have no effect. I have come to the conclusion that XNode could benefit from having an ability callable at anytime so the XNode data could be updated bypassing the XNode expected behavior. PJM

QUOTE(thevoiceover @ Oct 30 2007, 03:51 PM) Use the following code to write your own "HSL to RGB.vi" in LabVIEW. It does not take that long. /****************************************************************************** FUNCTION: HLStoRGB PURPOSE: Convert from HSL to RGB IN: Hue, Saturation, Luminance from 0 to 1 RETURN: RGB color (0xRRGGBB) COPYRIGHT:1995-1997 Robert Mashlan Modified for LabWindows/CVI, 1999 Guillaume Dargaud ******************************************************************************/ typedef unsigned char BYTE; // 8-bit unsigned entity COLORREF HLStoRGB(const double H, const double L, const double S ) { double r,g,b; double m1, m2; if (S==0) r=g=b=L; else { if (L <=0.5) m2 = L*(1.0+S); else m2 = L+S-L*S; m1 = 2.0*L-m2; r = HueToRGB(m1,m2,H+1.0/3.0); g = HueToRGB(m1,m2,H); b = HueToRGB(m1,m2,H-1.0/3.0); } return MakeRGB((BYTE)(r*255),(BYTE)(g*255),(BYTE)(b*255)); }/****************************************************************************** FUNCTION: HueToRGB PURPOSE: Convert a hue (color) to RGB COPYRIGHT:1995-1997 Robert Mashlan Modified for LabWindows/CVI, 1999 Guillaume Dargaud******************************************************************************/static double HueToRGB(const double m1, const double m2, double h ) { if (h<0) h+=1.0; if (h>1) h-=1.0; if (6.0*h < 1 ) return (m1+(m2-m1)*h*6.0); if (2.0*h < 1 ) return m2; if (3.0*h < 2.0) return (m1+(m2-m1)*((2.0/3.0)-h)*6.0); return m1;} PJM

What do you mean? this look very "Chic"! PJM

"The Consumerist is reporting that a Best Buy customer recently purchased a hard drive only to discover that the box contained six ceramic bathroom tiles instead of the Western Digital ..." Read More... I wonder if it cames with a chisel too... PJM

What you are experiencing is a LabVIEW bug I reported a while back. I actually though it was fixed, clearly this is not the case. Basically starting in LabVIEW 8.0, NI broke the variant capability to preserve the data name (see this thread). The good news, is that there is a work around. If you change your code as seen below everything works fine. PJM

I don't know if you care about the display side of it, but if you do, attached below is one way to do this. Note: OpenG VIs Required. PJM Download File:post-121-1193433707.vi LV8.2

QUOTE(Darren @ Oct 24 2007, 02:04 PM) Ah, that's too bad Well may be combining the use of VI inlining + XNode + XData Node something might be possible. Have the code in a subVI, have the XNode display an image of the code instead of the SubVI icon, then attached ear(s) to control execution (if possible/needed). When the user want to edit the XNode code, inline the subVI/Xnode... This are stream of consciousness ideas... might not lead to anything. PJM

QUOTE(rolfk @ Oct 24 2007, 01:13 PM) As per the wiki page: http://wiki.lavag.org/XNodes' title='LabVIEW Wiki article on XNodes' alt='Wiki article on XNodes' style="border-bottom: 1px dotted #3366BB; color: #3366BB; cursor:pointer; text-decoration:none;" class="wiki">XNodes, this is where the timed loop XNode code is located (vi.lib\Platform\TimedLoop\XDataNode\XDataNode.xnode). There is a lot of stuff in that folder (password protected of course). PJM

Well this have to be possible with the existing XNode stuff since I am pretty sure the timed loop (or timed sequence) is an XNode. Figuring out how to do what you describe though, is probably not going to be easy. PJM

QUOTE(mballa @ Oct 19 2007, 06:50 AM) Mark, Try this VI (LV8.5). This does work with and without the ini keys (I just tested it). It is pretty much the same that Ton post, except it does not use event registration. Notes: The VI Activation provide the app instance, so no need to launch it from any place special. To be able to see this event (to create it in the event structure) you have to enable the ini keys. Since (I believe) the Navigation Window is using this event to find out which VI has the focus, it has to work on every machine, regardless of the ini keys. Download File:post-121-1192810815.vi PJM