Michael Aivaliotis

QUOTE (BobHamburger @ Dec 6 2008, 11:24 PM) Thanks!

QUOTE (Justin Goeres @ Dec 6 2008, 07:39 PM) What kind of warning do you get when you change a typedef by adding, removing or renaming controls within it?

QUOTE (Aristos Queue @ Dec 4 2008, 05:06 PM) Knowing how the tool was built would be interesting form an academic point of view, but kinda useless for helping me develop better code I think.The diagram cleanup tool works great for low node count VIs. It seems that if you go above a certain node count it goes crazy and makes the diagram worse than better. Also it seems to start cleaning up from the top left and works it's way down and across. Can't confirm but it feels that way. Another observation is I don't think it tries hard enough to reduce bends in wires. Or perhaps this is in conflict with some other parameter. It should try to keep wires straight instead of doing this (this is in auto mode): http://lavag.org/old_files/monthly_12_2008/post-2-1228603538.png' target="_blank">

QUOTE (Darren @ Dec 6 2008, 09:12 AM) I'm perfectly fine with this. Where do I sign? In general I abhor dialogs. There are many reasons why, but primarily, they end up being like that pesky fly that keeps buzzing around your head that you keep on desperately swatting with your hand. You can never kill it, but just make it go away temporarily. Then it comes back and you swat it away again. All you want to do is get your work done but that pesky fly keeps buzzing around your head. That's what dialogs are. == Here I go hijacking this thread, but is it me or is the resolve conflicts dialog totally useless. I mean, I can never figure out what the hell it's trying to tell me and in most cases it seems like I only have one choice and it's already highlighted for me.

99 percent of the use cases is when you need to add terminals on a VI that has all the terminals full. In other words you need to change the pattern to add more space. You don't usually rename terminals or rearrange them. Not that I haven't done that. So in these cases LV relinks properly. I can see that if a relink occurred where terminals were swapped but not broken then this would be bad. However even with a manual relink, the end user rarely notices it because the wires shift around but the colors stay the same. I guess NI's taking the safe route and letting the user blame themselves instead of LabVIEW for the problems that may come down the pipe when the app doesn't work. In my opinion I would just prefer to let LabVIEW do the relink "like magic" and have %99 satisfied users delighted. Even if it means that %1 will swear at NI for breaking their app.

It wasn't me.

Wow, I just figured out the answer. Apparently this can be done using the "replace with" function. In the search results window. Just do a search on the VI then replace it with itself. Awesome!

Is there a way to autorelink all subvis when their connector pane changes? I currently have a bout 100 "relink to subvi" actions to do... And we all know programmers don't do anything manually. Edit: Correction... 675 SubVIs to relink.

QUOTE (crelf @ Nov 26 2008, 11:57 AM) Norm's joining NI? When did this happen? When was the official announcement?

Hey Mark, I just got your tweet about the video and just finished watching it. Great Job! Two thumbs up!!

I'm always logged into Google because it's my core information management engine. It powers my online life.

SearchWiki was announced yesterday. Please help LAVA, by commenting in a positive way, any LAVA related search results. Also you can bump up results too. This is probably Google's way of slowly allowing user defined search results. If so, let's give LAVA a head start. Link

I'd like to continue this thread as I think the diagram cleanup tool has a lot of potential and I'm hoping NI will improve it in the future. It's already saving me a lot of development time. One thing I haven't been able to figure out is how to compress horizontal spacing and remove a lot of white space. In the example below, I don't think it's necessary to expand the above structures. Should be like this: It seems like the tool tries to balance things out. If I delete the code below the structures then they become small when cleaned up again. It seems to expand the case structures to the width of the code below them.

QUOTE (David Boyd @ Nov 15 2008, 09:23 PM) Thanks for the report David. This is a new issue. I will look into it.

We can change the tag to Homework, which is an even more excellent idea! But please let's not use tagging as a form of passive aggressiveness. It just ends up fucking up the whole system. Also, anyone with a LAVA account can edit or delete a tag. Just like anyone can edit\delete or write a LabVIEW Wiki article. Don't expect a notification when your tag is edited. It's become part of the collective at that point. Freely editing tags makes the system work.

Does anyone know how to call the CreateEventA windows function in kernal32.dll? I'm not sure if my call is working. I always get 0 as the handle. Does that makes sense?

Please don't SHOUT and don't cross-post.

The LabVIEW Wiki is back up!

QUOTE (Daklu @ Oct 28 2008, 11:31 AM) The OGB performs namespacing by renaming the physical files on disk. When you wrap VI's in a library (lvlib) the filenames stay the same on disk but when they are loaded in memory they have a name prefix which prevents them from conflicting with other VI's in memory. They both do the same thing really but since the filenames on disk don't change (with the lvlib approach) then it's still possible to have a crosslink in certain situations. QUOTE (Aristos Queue @ Oct 28 2008, 04:25 PM) I've never heard of the OGB system so I can't do the compare/contrast that you asked for. I can understand not being familiar with it if you have not used it but stating you've never heard of it worries me.

Ya, thanks. That message means that I have to fix something. :thumbdown:

QUOTE (Aristos Queue @ Oct 27 2008, 10:30 PM) Ya, but it works right now... besides, that's why it's in the rusty nails forum. :thumbup:

I've attached an image so those without LV8.6 can comment. Looking at the built-in help docs for the copy function we read this: QUOTE

Found this on the web so I'll add it to the thread for good measure.

QUOTE (Gabi1 @ Oct 23 2008, 01:37 PM) Hey, are you trying to invent a new word?

ROFL, I wonder what she would think about LabVIEW