PJM_labview

Since everybody is getting out of topic, let me add my voice to the chorum to say that I prefer spacemonger to the sequoia one (I dont like the 3d effect). I am actually evaluating spacemonger version 2.1.PJM

This is pretty much an echo of my own though... PJM

It is here -->SearchVIEW<--PJM

or write a LV app that query google constantly about LV... PJM

Cool :thumbup: I did not know about this one (and I though I tried them all in the icon editor)! PJM

I download it, then I noticed some VIs (that I believe you made) were password protected. My interest pretty much dropped at that point. PJM

If my memory serve me well, these VIs are use by mathscript. Everything that came with your LV can be used. There are actually gems in vi.lib that are unfortunately not exposed on the palette. In regards to these script VIs, If you can figure out the abstraction NI build over scripting, I see no reason why you should not use them.Note: Here is a gem I found in that folder as well (Connector Pane Terminal Order.ctl) PJM

Here you go. Note: I also down convert it to LV8.01, since this appear to be the LV version of the original poster. PJM Download File:post-121-1159163183.zip

As far as I know (and I have investigated the issue), this can't be done with scripting. One thing though, I have not check in LV 8.2.PJM

I also noticed that too. I was just opening and closing a LVOOP project (nothing with share variable) and there was a VI that constantly asked to be saved (I was doing nothing on the project just open and close). It last a couple days then it stopped (for no apparent reason).PJM

The only way I know to achieve something somewhat similar is to switch to the Palette View "Category (Standard)" and then whichever palette is top most (this can be changed as seen below) will show up first. PJM

While relinking some VIs I got this message (in LV8.01). I think the and/or should go away... PJM

Nice! :thumbup: I did not know that either. PJM

With variant you can write generic utilities that will take anything as an input. From your statement I suspect that you are not using the OpenG variant tools. As an example, the OpenG variant configuration VIs allows you to read and write ini file with an extreme ease (compare to the native LV way) [see image below]. I have seen them beeing used (or used them myself) for many generic utilities such as XML tools (controls --> XML, XML --> controls), generic logger tool, a pyhton data to LV data and LV data to python data tool and many more. PJM

Welcome as well.And if you have a real need (although looking at your english I dont think this will happen) you might even get some answer to question asked in french (some of us have a vocabulary that extend beyond "merde" ). A bientot. PJM

Unfortunately I did not keep the code since I had to rewrite everything. But as best as I can remember it happen when, out of frustration, I try to copy 2 VIs from a class residing in a lvlib into another lvlib (note: I was working on a copy of the lvlib with the same class data). After reopening the new lvlib and remarking the copy VIs as belonging to the lvlib, I got 3 VIs with red x (the original one that was broken before + the 2 I add to the lvlib). I think I fix one of the red x, but eventually I could not fix the other 2 red x. From your detailed answer (thank you), I gather that in all instance (while debugging classes) the only errors to pay attention to are the one marked with a red x and everything else is basically broken because these red x errors; if this is correct, then why do I need to see all the other errors? this just add to the noise and does not make my job any easier. PJM

Have you check VI Package Manager?It allows to install the OpenG Goodies, and you get for free, among other things, a LabVIEW 7.x palette. See attached picture. PJM

I know about the red X, but why does VIs in the class that have no dependency whatsoever (whith the broken VI) are broken?. Basically, every member in the class is broken (and if you follow the error path [from VI to VI] you end up in a recursive list of errors). Why?Also, I end up in situation with several VIs with a red X where I was not able to figure out what was wrong. In my opinion, the class debugging is so poor that this greatly limit LabVIEW OOP usability. PJM

I could not agree more about the file dialog express VI. On a side note, it saddly seem that in the latest LV version, primitive overloading through right click option is getting to be the norm. So on answering your question 1) No I did not use it. But to access the primitive this is a pain (drop express) right click to see bd, open subVI and finally copy primitive. 2) I prefer small icon. Why: Real estate. As a style, I dont like code that waste space. 3) No 4) I use the daq assistant express VIs before generating the LV code form it (actually this is a pretty handy one) PJM

Hi,I believe, I had this happen to me once or twice (but on LV 8.01). A restart of LV did fix the issue. PJM

Hi Brad,Yes there is a way to do that. You can use the variant to data primitive. See attached image and example. PJM Download File:post-121-1156830220.vi

I will have to second that.I got VERY frustrated trying to debug simple LV class. A wire connected to the wrong input and the whole class is broken and the error windows return a huge amount of errors completely irrelevant. In some instance I could not even figure out what was going on and I had to recreate the class from scratch (what a pain). To make thing ever worse try to put a class in a lvlib... Enjoy the nightmare. PJM

HiI like your implementation (I especially like the now obvious way you got over the data copy issue I previously had). Attached is a revision of this ObjectByRef class. Download File:post-121-1156716022.zip It has the following major modifications (see code for details): Add support for name objects. Disable the set data (I dont think this should be allowed, too much potential for major screw ups). Change behavior of SetModifiedData so it always release the lock. Minor changes in several other VIs (most ot them regarding the timeout input). I have not decided yet if the copy method is really usefull, but I left it there. In regards to this point: "Clean up of member objects at time out and at object close, propably separate private _CleanUp routine should be used in all methods" I gave some though about this, and I think the timeout should return an error from within the private method whenever possible (meaning whenever we know what is the only possible situation that may have arised to return a timeout). For an example of this see SetDataToModify. About this point: "If class Close is called during simultaneous call to _Set Modified Data the data queue may be empty. How to avoid this situation?" I think this is a non isue since in that situation while you may get default data you will get an error because the queue refnum has become invalid therefore you can recover if you handle this error somewhere. I will have to give some more though to your other points. PJM Note: any comments are of course encouraged

I just saw this video on yahoo and.... <embed src='http://us.i1.yimg.com/cosmos.bcst.yahoo.com/player/media/swf/FLVVideoSolo.swf' flashvars='id=715691&emailUrl=http%3A%2F%2Fvideo.yahoo.com%2Futil%2Fmail%3Fei%3DUTF-8%26vid%3D23af1dde394f5f83347374a6b24ed662.715691%26fr%3D&imUrl=http%253A%252F%252Fvideo.yahoo.com%252Fvideo%252Fplay%253F%2526ei%253DUTF-8%2526vid%253D23af1dde394f5f83347374a6b24ed662.715691&imTitle=%25E6%259C%2589%25E4%25B8%2580%25E5%25A5%2597%2521%2521&searchUrl=http://video.yahoo.com/video/search?p=&profileUrl=http://video.yahoo.com/video/profile?yid=&creatorValue=bGVlY3BfbWU%3D' type='application/x-shockwave-flash' width='425' height='350'></embed> WOW! PJM