PJM_labview

Alternatively, if all else failed, you can generate it programatically (

Download File:post-121-1198880077.vi

PJM

QUOTE(osvaldo @ Dec 19 2007, 01:17 AM)

...

The only waveform that the probe does not browse is the Dinamic subtype...

I do not know how to create one to verify the probe! Suggestions?

...

How about like this?

http://lavag.org/old_files/monthly_12_2007/post-121-1198088545.png' target="_blank">

PJM

This is the "NI LabVIEW 3D Visualization Demos" from NI Labs.

PJM

Quick update: After the search finishes, LabVIEW hangs. Therefore, LabVIEW search function is unfortunately note usable on large project

PJM

The LabVIEW search dialog *appear* to slow down over time and when searching inside classes.

I just did a search on a project that had a lot of VIs (clones included) in memory. The first few 1000s VIs/Clones went very fast, but around 4000s, things start to degrade pretty quickly.

The entire search has been going for over an hour now (but it is close to the end).

Is this a know issue (this slowdown)?

PJM

Ya, you got to call Doctor Who. The Timelord will fix it up for you.

PJM

The CAR number for this issue is: #7178839

PJM

AQ, I did submit a bug report on this issue this morning. I will be posting the CAR when I get it.

PJM

Ok, I understand now.

This method (although deprecated in 8.5) should do this (I have not test it though).

PJM

Download File:post-121-1196981358.viLV8.5

Tomi,

I have used this VI buffer technique in the past several time (basicaly reading the VI as a text file and saving the end result as default in a string control). I don't understand why you say that LabVIEW will not recompile this VI. As soon you "extract" this VI to disk, it becomes like any other VI. I guess I don't quite understand your use case scenario.

Note: I have seen the scripting buffer function and while I never had to try them, I always though that the App:Open.VI from Buffer method was the equivalent of extracting the VI to a temp location and them opening a ref to it.

PJM

Ok, I will report it later today. Unfortunately I did not kept the corrupted VI (I just revert to my last known good copy in my source control). I will be working on that same class today, so I may very likely get that issue again. As to attached everything, I don't think this is going to happen. This class alone load 3600 VIs in memory.

Another issue (might be related). While editing this VI, LabVIEW periodically freeze with the hour glass cursor (it *seem* to be verifying the hierarchy) for about a min. Most of the time this is not critical (no crash), but every so often it crash. I might be getting these compiler error just when I am attempting to do an edit and LabVIEW start to hang up (this is just a though).

PJM

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)

We have a big project and none of our builds worked when we tried to use our 8.2 lvproj files. They just failed with errors with blank error descriptions. Everything was fine when we started from scratch (after a couple of wasted days and some tech support). The lvproj 8.2 -> 8.5 upgrade seems to be just hopelessly broken. :headbang:

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)

What is alt gr?

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)

Was this in LV8.5? If so then, yes, I believe I have seen some similar corruption but in my case LV complained about he BD being corrupt and unable to be loaded -- even when it was!

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)

... Has anyone else seen this? I was not able to recreate the issue.

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)

You cheat:

http://lavag.org/old_files/monthly_11_2007/post-2399-1194888954.png' target="_blank">

Ton

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