i2dx

the appended VI should list all SubVIs of a VI. But the array is empty ... Download File:post-885-1142281377.vi I am affraid, it will not work at all, but - as I never give up - I'd like to ask, if someone has an idea/tip whatever to get the list of SubVIs? [edit: minor typo]

I have to admit, I can't remember so I am not really sure, but I guess, it was in german before the installation of the 8.0.1 patch Off topic: please give me an english lesson: how can I express in english, that I can not really remeber: google tells me "darkly remember"?

me too, but I really hate it, if I want to know how it works and can't figure it out

I am swearing like a trooper every time I have to use LabVIEW. Especially the PDA Module really drives me crazy. I find it extremely hard for a power user to get used to the new "features". And after 3 month I have to admit, I really hate it. This could be off topic maybe, but I want to ask some questions: Why are there unwanted spaces (with the width of the scrollbars) at the bottom and on the right side, if you compile a VI? This was fixed with LV 6.1! Ok, you can set the panel size now in the "Window Runtime position" properties, but this are a lot of extra clicks for every VI. What is that "defer decision" button god for, if the VI is not a subVI and I want to close it? Why are Typedefs not marked as modified, if they are opened with a different platform? [This is a REALLY nasty bug!] Why is there no tooltip with the coordinates, when you move the FP with the "hand" cursor? Why is the "Front panel Position"-field missing in the "Window Runtime position" properties? This would make it easy to build a clean layout. Why can't I decide on the sub panel itself, whether there are scrollbars, or not, anymore, instead I have to remove them at the inserted VIs, but they still appear for a tick in the IDE...? and so on and so on and so on ... BTW: where is the :throwLV8: smiley? Maybe you think I am a defeatist, and maybe I am, but I'l like to annotate as a statement of defence, that I also am a perfectionist, and LV is far from an improvement compared to LV 7.1. My point of view is: why do I pay for a SSP when things become worse, my work is constrained and I am getting an active gastric ulcer? please dont hesitate to flame me, if I am wrong;)

now i see it, too ... I have an english LabVIEW, but my example finder is german ...

ok, I admit, I feel like the last fool, too ... I have seen that palette view, njkirchner is using several times. but I can not figure out, how to get this view. who can help an old man to cross the street?

hmm ... i am not quite sure, maybe it's a bug, they declare as a feature, now I am still missing the possibility to decide wether to show or not to show the data nodes. I can remember this was possible in LV 6.1?

it should be in the function palette (top level ...) how did you place it in the palette "by hand"?

ok, thank you! I will forward this to the "labviewforum.de"

may I ask, who is using it and how it is running? I would really appreciate some feedback! Why I made it and how I use it: I use it, when I start a new project. I have a "Programm Template", which is about ~50 VIs "big", which contains the basic functionality, wich I need in allmost every project: - queued statemachine consiting of 2 loops, one for the event handling, the second for the states - database connection - errorhandling and errorlogging - some tools like configuration load and save, finding the working path, etc ... When I start a new project, I copy this "Project Template" with the "Duplicator Tool" to a new folder. This worked very well with LV 7.1, it's a little bit anoying, that i have to create the vilibs and the project hierarchy "by hand" in LV 8, but i hope, I will soon have the time to fix that out, too. The Duplicator tool has a "Prefix Rename Function", because I use a prefix on every VI-name in the project. For example in the FeXXX Quality Survailance System I use the Prefix FeQSS_, which means, all VIs (except system VIs or VIs from the vi.lib) have these letters before their "real name". e.g. the main VI's name is "FeQSS_main.vi" When starting a new Release of that Project, I copy the entire Project hierarchy into a new folder (e.g. Source Code R2) with a new prefix (e.g. FeQSSR2_), which enables me, to keep the old and the new VIs open simultanously, if i need to. The second way to use it, is to extract specific parts of a project and copy it with the entire hierarchy to location with a new prefix. Please give me some input, and no doubt, I can bear up severe criticism or if you should think, it's useless. [i am a tough guy - SOFTware developer is my second life ]

maybe the project duplicator tool helps ? Post#2432

Jim, thank you for your tool! I have posted the link to your tool in the german labviewforum.de and one user is complaining about errrors: The masscompile finished with about 100 (error 1)s in the log file ..

that's why we call the sales people "ferengis" in Germany!

I think, it's an improvement. if there is NO value, you should see NO Value. I agree, that would be fine. But, how to make sure that there is a difference between "NaN" and the minimum Value? e.g. if the minimum Value of the scale is 0, you wire -10 to the e.g. tank, it will only show a very small line at the bottom of the tank, which can be quickly overseen, and does not differ much from an "empty tank"

hey, and what is about me? If this is now the beginning of "kenjo enterprises" (maybe be a 20 billion dollar company in 2010)? I wrote the solution. BTW: PWM with DIOs is somewhat cool. I only used them for relays, etc before ...

hmm ... i don't think there is a solution with LV Scripting.

i'd like to attach, that IMHO it's not nice to post the same question in several forums, because reading + solving a problem costs time. and I thinks it's not fair to bother more persons than necessary with a problem. furthermore, if someone spends time to solve your problem and gets the answer: thank you, but the solution from XYZ at the VerySpecialLabVIEWforum is much better, he /she will be rightly disappointed or angry.

as far as i know, this will not work. if you try to start a VI, which is NOT reentrant and which is a subvi of an other running vi, via VI server, you will get the error 1000: The VI is not in a state compatible with this operation.

i like 7.1.1 most the event handler helps a lot and the small dots to increase a structure are a very good feature

hmm ... nice idea. if you need default input for testing, try this: CreateFarts.com :-D

maybe he thinks of renaming the files, instead of renamig a directory? @entropy Post #2432 maybe this one can help?

my installer told me that it is installing the German version, although I have the english LV Version installed ... my fears, that after the install my former english version would be a german one did NOT come true <puh>

sounds like you should check the path to your database in the exe ... or do you use a system dsn?

me, too ... me, too ... ==> FULL ACK in the name of all other Gods here, I want to thank you for saying this :-) @kenjo: you can get some help in the example finder: help--> find examples (search for sound ...) or take a look at this: SoundCard Example

First of all: You have been warned (from me!) (I am one of these unlucky creatures, who has to work with the PDA Module, and because, I am the dumbest brick of all, I thought it would be easy to developed a bigger client/server application and now I have to debug & fix it.) the PDA Module can create VIs, which run on a PDA. If you need interaction with a VI, running on your PC, you will need some networking e.g. Bluetooth or TCP/IP and you have to code that on your own. Luckly there is a PC + PDA TCP/IP Demo in the example finder, which shows you how it works and helps you to avoid the common pitfalls (e.g. CR/LF-Mode crashes the PDA-VI ...). I have no experience with the new shared variables on a PDA, I tried to create one (it was my first ever ...) but it "failed valiadion", whatever that means ... If you think about the LabVIEW Remote Panel functionality, i give Yen a 100% ACK ...