Ton Plomp

This is normal behaviour. LabVIEW stores an object (VI/CTL/XCTL) as a RELATIVE path, and if it don't succeed in finding such an object it uses the search sequence you can heavily tweak! (in options/paths/search paths) Then it has all the xcontrols in one namespace so only one can be loaded. What you could do is put the xcontrol in a library (foo1.lvlib:foo.xctl and foo2.lvlib:foo.xctl). I'm not so positive about lvlibs right now but maybe in the future (near or not so near ) they improve! Ton

Programming in pictures aouch..... But what sequence structure have you used? have a look at Darren's nuggets on flat sequence Ton

Hello Seoul, If I were you I'd contact the NI helpdesk. Because 8.2 is not released yet, so the beta help is you goal. Ton

Hello bbean, what code are you using? BTW i found an option in the context menu: This will add a context menu item on the subpanel, where you can open the BD, maybe something for you? And this code was succesfull for me: this is the code from the subpanel vi, it opens the BD if I click on the (running! sub panel VI) boolean Ton

Hallo Ealson, you could even format the string right into a timestamp: Good luck, Ton PS 20 MB shouldn't be problem if you program properly.

did remember but 8.0 is lightly faste (0.2 ms) Ton

I'm not sure, but my computer is something like yours. If i rememeber i'll test it this weekend at home on 7 and 8. Ton

Well if my measurement is correct you're not looking into chirpZ.... Ton

Well this is very usefull, for instance you are acquiring data at a hight speed and need to process this as well. You could 'give' them both a different core, this would mean that data acquisition and calculation don't come in each others way.. Ton

And ontopic, it just discoverd a rtm file for the project located at LabVIEW8.0\Resource there are several RTM, i'm not sure when they are loaded but I think you can edit you're right click with them Ton

Use strings they are automatically converted into the right format! Perhaps you should make the controls strings and convert them insde the VI! Ton

Hi All, as described here I am working on a toolbar for the LabVIEW development environment. So here it is. Beta 1, partially documentend and not well integrated with LabVIEW. The zip contains a project with documentation and the sourcecode. Use the ButtonLoaderDialog to start the toolbar. If you close the project the toolbar will be closed as well!!! System requirements are OpenG and LV 8. Have fun and let me know what your opinion is! Ton And a screenshot: One thing to mention. The BMP's used for the toolbar should be 40 pixels wide! Download File:post-2399-1152463695.zip

And it's getting even better, hopefully I have the time tonight (during Germany-Portugal) to finish Beta 1 (bad documentation. ) It's looking kinda neat. I am only looking for a way to launch the toolbar when LabVIEW kicks in. I found something at OpenG, but Jim stated these where version specific, it only showed LV7 <... Does anyone know if these still work (darn and now I can't find the info anymore :headbang: ) Found else it resides in the tools menu! Ton

And after that synchronize all instances, with arrows pointing down next to the run button. Ton

I'm not sure which of the 2 is usefull, so I enabled them both. One other question: How can I close a VI via VI-server, and let this event trigger the event structure. I assumed the 'FP.Close' method would trigger the 'Panel Close?'-event but it didn't. Now I have a User event 'close' but this is a bad workaround.. Any thoughts? Ton PS: For the lava repository, this is what I got so far: A method to add buttons (actually pictures), these pictures merge into one toolbar (just in the order they where added). I have the following 'events': Mouse enter Mouse leave Mouse move Mouse down Mouse up So far I have two buttons, one to close the bar, and one to save the BD/FP to a png (thanks to JP Drolet, Altenbach and ChillyCharly at NI-breakpoint) So I'm still thinking about changing button appearance (should be easy), remove a button, dynamic tip-strip, move the tool-bar, flatten the toolbar.. I hope to 'finish' the work next two/three weeks or so

Hi Rolf, I'm looking into a development toolbar... with some buttons like, Save, New, Open, Check In, Check out, Print, Save diagram, Build Documentation. I hoped this could be next to the controls in the edit-mode toolbar. But I'm almost there in making a floating toolbar. If i'm satisfied (and not that ashamed about the programming style) I'll put some here. Ton PS I think i'll have to dive into GOOP to get this working.....

Well i don't see my issue anymore after rebuilding from scratch, although I haven't added one nasty private property. I am working on a toolbar next to the open panels which move with the active panel. I hoped at LV8 there was finally a way to add your own button to the tool bar but no! :thumbdown: Ton

Does anyone have succecfully saved a VI which used the VI activation event (private one). Because the event behaves normal but then I try to save it I get an error: Does anyone seen this before? I want to use this to detect activating a VI. and get the co

Hi Jimi, Could you post some images of what you want, and some of what you got? Also have a look at the printing functions, you have the options to print the controls that are connected with description and images. If you save these to rtf-files you can import them into you're documentation. And you could go into the report generation toolkit and save them to word files HTML Help file generated: With the following options: or are you looking for this: Ton

This should do: Success Ton

Well the good news is you got already some interface method (DLL), the link you provided was a document to create DLL's with LabVIEW. You can skip this step. Have a look into the DaqMX driver set on your controls palette. These have a standard set of VI's to communicate like Open, Read, Stop and Configure. In these VI's are low-level VI's or functions. If you want to distribute you're code to other computers to be used INSIDE LabVIEW you should make an installer which puts your VI's in a subfolder of your instr.lib folder: (on winxp): c:\program files\national instruments\labview 8.0\instr.lib\MyDevice If i'm correct the inst.lib is an option in the installer as a target (or if i'm wrong at least the labview folder is a target. Experience with these settings and share your experiences! Succes, Ton

We were all once In which language is the driver written and how is it called? LabVIEW (on winXP) can communicate with DLL's, ActiveX, .Net search for these things in the help file and you'll find them. LabVIEW 8 has a tutorial to create a driver, this will solve some of your issues and generate VI's (icons :laugh: ) for you with a consistent look and feel The help-files shipped with LabVIEW are very good, if I compare it with VBA it is stunning. As a beginner I would rely more on the NI forums although these seem off-line today (OffTopic: am I the only one seeing this??) than this forum, it has much more discussions on 'beginner' level! Please search these forums very well. LV 7.1 VI's can be opened by 8, and 8 VI's can be saved as 7.1 although if I were you I decide to go with 8.0.1, LV8 has more events to detect and specially for your case the device driver creation. (which main target is GPIB devices but the functions should be alike. Succes, Ton

Maybe it's origin is the multi-panel construction? It would be nice if you could set it for every panel and corner! Ton

No laughs here, yes it is possible. There are 2 options (the easy expensive and the difficult cheap) Buy the report toolkit. Make your own toolkit. BOth make use of the excel activex software. It is possible to do but it is very hard. Ton

Hi all, in addition to the 'exit for loop' discussion over at NI, i have the following wishes: 'Merge Flat sequence structure', this would allow to merge two sperate sequence structures into one, 'Split Flat sequence structure', allow you to ad a sequence based on selected items 'swap sequence structure', swaps sequences 'dynamic select case', maybe based on rings any other options? Ton