aart-jan

Very good reason! thanks Jim. I think I may apply it to my user.lib VI's as well as projects.

occurences, notifiers and queues all have the global scope and are not tied to dataflow. For notifiers counts the same as occurences: why does the event structure not handle notifier events? It would be a great alternative for the wait on occurence/ notifier functions. I know the event structure is mostly meant for user (front panel) events, but NI has not been limiting it to just that. It is not so much that I can't solve my coding problems, it just seems to me that implementation would become more eloquent and simple. Maybe they could develop a new structure for this; like a case structure that can process programmatic events of various kinds.

I am struggeling to find the best way to deal with occurences. Especially the wait on occurence is a pain. It requires a while loop and only detects an occurence when waiting on one. Occurences seem to have something in common with.. event structures, and oh, wouldn't be nice if there was something like an "occurence event." I know I could register an occurence as a user event, but what's the use of that? What I would like to see, is an occurence event!

I am wondering what is the use of the mangle and unmangle vi's from OpenG. I know they can add or stip a namespace from the vi name, turning name.vi into name__namespace.vi. Is this useful just to be able to recognize what software the vi belongs to, or is there other intentions? Thanks!

Not a clue why my head gets diverted to silly stuff like this, but the result is fun. See attached code (LV7.1). It is a custom boolean control that has a ring picture animation on mouseover and value change. The code is not good, it was the control behaviour and look I was after. With LV8 xcontrols it should be possible to condens all the code in one control node. haven't tried it yet in the beta. Also at this point I don't know how the event passing works with xcontrols. Download File:post-1175-1128822838.vi

Although I never got to LV scripting yet, I do know that the "supersecretpropertiesetc" entry in the Labview ini file no longer works in LV8 (duh..). Will this be the end of labview scripting (for now)? VI's will be approximately 55% smaller in size..read the release notes! How did they do that? What will be the implications? How do you make a single file out of a project? I didn't figure it out yet.

I know I haven't got the fastest response time, but what I do is in real time The PDA module only has some kind of make believe vi server: it only supports a few properties. That seems to be the most obvious problem to me. It gets even more annoying, because it also behaves inconsistent with clustered data that is any more than simple.

I would like more key control while programming, such a silly things like F2 to edit etc. Maybe ways to quickly select a terminal or node by typing the first few letters of the label. Labview sure is "mouse heavy."

Took me a while to discover this one: merge vi's. Have a chunk of code you seem to be making over and over again? Put it in a vi and place the vi in your user library. Then choose the menu "tools>advanced>edit palette views" and find the vi in the user library. Right click the vi and select "merge VI." I often use it for subvi's combined with control references that can instantly add certain functions to programs. Also useful to add frameworks to vi's that you create by "creat subvi" etc etc.

I believe there are plans to support drag and drop in the next version of LV

Reentrancy is something you use for subvi's. You can set a vi to be reentrant in vi properties, but if it is a top-vi, Labview will not open the same vi twice. Furthermore, events can only be embedded in subvi's if you fire them programmatically using "user events" aartjan