-
Posts
6,196 -
Joined
-
Last visited
-
Days Won
104
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by Michael Aivaliotis
-
-
The thing with LabVIEW is, either you "get it" or you don't. Those that don't will never change, so don't bother. Our job is to try and find those that "get it" and help them grow.
Hmm, that sounds like a religion.
-
Featured sounds like 'studied and selected' (perhaps paid?), but it looks like it incorperates the last addition. Is that correct?
Ton
For now it's stuff that I feel needs to be featured.
-
2
-
-
Jon,
Please can you edit your LV Assistant page so that the link for the Icon Editor API actually looks like a link. Only when you mouse-over does it become apparent it is a link (this is in Chrome). I had to search the internets to try and find it and finally, like Jim, stumbled on this page.
Thanks!
and again, great tool :-)
For some reason, links on the LAVA CR pages look a little different. I'm working on fixing this.
Edit: This is now fixed. The links on the LAVA CR match the look on the rest of the site.
-
I hate, hate hate hate the new probe windows....
The new Icon editor is next on the list.
I'd like to add a bit more to this so I don't sound harsh. I like the idea of overhauling the probes and the icon editor. It's a step in the right direction. They just both need improvements to make them really useful for me and not get in the way of my workflow. They're not there yet.
-
I hate, hate hate hate the new probe windows....
The new Icon editor is next on the list.
-
In Vista, User Access Control was a pain. However, this is much improved in Windows 7. I hardly get any confirmation dialogs except when installing software. Even though I now work off-of a Mac and have delegated Windows 7 to a VM, I have to say that I really like the new control panel in Windows 7. It's more task centered and makes more sense to me than the old way.
-
I seem to always be using LabVIEW 32 bit. The executables built work on 32bit and 64 bit Windows.
-
Thats pretty much what I said... and I get no kudos
, shucks...
Ok, I gave you a kudo too.
It's one of those things where even though I read something over and over
, it takes the right set of wording or mindset to just make it "click" in my mind... or maybe I'm just getting old.
-
Actually, it is. In the BD page, there's a transparent free labels check box.
Aaaah! Seriously?
That's it. I just never clicked on that setting before. I just assumed that if it wasn't transparent then it would be white. I guess at some point in the past, NI decided to make free labels yellow. Because I swear they used to be white with black borders.
Anyway. Thanks for forcing me to try it.
-
I've seen this somewhere a few years back but haven't been able to figure it out recently. I want to change my default free labels to have a light yellow background and a black border. I like that style for comments a lot. I thought this could be done via the LabVIEW options, but It's obviously not there. Then I remember someone created a palette item which you could drop on the diagram to do this. Any ideas?
This would be a great feature to have built into LabVIEW. But actually a better code commenting tool is sorely needed anyway.
-
Curiosity. It's interesting that you pronounce VI as "Va-ee" instead of "Vee-eye". Does anyone else do this? Just curious.
-
If you want to jump to Danny's presentation click on slide #17.
-
Thanks everyone for the suggestions and comments. In the end, I used one of jgcode's tools. It's funny how, you don't realize the value of the LAVA code repository (or LAVA) until you run into a problem.
-
The code now checks for LabVIEW version and mass compiles if IDE is newer.
Actually this is not required anymore since VIPM 2010 already does a mass compile after installing packages now.
-
There's a few programmatic solutions on this thread
Thanks. I'll definitely dig into that.
-
scripting is your friend.
I figured. Maybe someone can help?
Edit: It seems like there is some hope by using the Search and Replace text feature that's built into LabVIEW. I think this will work for now.
-
The problem I have is that when I rename the class, I end up with object controls and indicators that contain the label of the original class. Is there an easy way, outside of manually renaming, to do this? Maybe someone has a tool out there?
Not sure why LabVIEW doesn't do this for me. I can't be the only one with this problem.
-
1
-
-
There's no way that I know of. BTW, you should remove the changelog from the description since this is now built into the LAVA CR website.
You can probably remove old versions of your submission as well, to clean things up.
-
This LAVA Code Repository Download is no longer distributed or supported by LAVA.
Please follow this link for further support.
-
I can use notifications to do what I want, but it is not quite what Iwas looking for, more something like the bookmarks on the Dark side.
I think the "Like" feature is new! It is currently working for CR items due to the recent update to the CR pages. However, this feature will soon be migrated to the forum topics as well.
So, stay tuned!
-
Yes. This is it.
-
Please Kudo this suggestion. I think it's a great idea and should be seriously investigated by NI for future implementation. Perhaps in 2012.
I'd also like to see some programmatic support as well. Via a scripting property. Copy and paste properties. It should be smart so that it ignores incompatible properties instead of failing.
-
That's a good question Cat. There doesn't seem to be a search field for that in the Advanced Search for Members. I think it's an oversight.
Since you're trying to kill some time. Go over to the Invision forums and make a feature suggestion: http://community.invisionpower.com/forum/298-ipboard/
-
I'm responding to user interface events using an event structure. However, some of those events are coming from a signaling property node. Is there any way from within the event structure to detect the difference between actual user generated events?
"I hate LabView" topic
in LAVA Lounge
Posted
True, LabVIEW has limitations. That's why we're all here pushing the limits right?
It's also true that you can have a successful lifelong career in LabVIEW and even run a software company that uses LabVIEW to its core, without ever having to touch a sigle line of text code. Oh, and it's fun too.![yes.gif](http://lavag.org/public/style_emoticons/default/yes.gif)
The nice thing about all this: I never even once throughout the years doubted my decision to base my career around LabVIEW.