Michael Aivaliotis

In LabVIEW 8.5, you can't add Auto-Populate folders in classes. Aeee Caramba!

Is there a reason for the different versions? Can you just publish the lowest version? Others can just recompile up. Otherwise, just indicate the latest version and please put all the other versions in the description.

Something about those 4 boys in the background seems so wrong...

QUOTE(LV Punk @ Sep 4 2007, 11:24 AM) First rule of all LabVIEW releases. Palettes will change.

All of this is nice and fun but any solution proposed is still something that is a hack onto the LabVIEW IDE. It also will be a tool made by someone or some entity that thinks they know what I want. What I would really like to see is an API for the rest of us. Something that allows anyone to create extensions to the environment. Event driven, shortcut driven, context sensitive etc. Ya, I know, it takes time and costs money and NI has their priority list... I'm just saying. Typing something into a textbox to get a function? Those icons on my pallete have names? Who would have thought. Now I just have to figure out what everything is called and I'm set.

Ya, perhaps a delete is in order...

QUOTE(orko @ Sep 3 2007, 02:02 PM) This is what I get as well. However, I didn't follow your point in the first post until now. The circled area is the key. You will also notice that if you double-click on the SubClust1.ctl in your example, the cluster has been replaced by an object icon. LabVIEW did the right thing but the question is, is it a bug, or an unfortunate side effect. QUOTE(orko @ Sep 3 2007, 02:02 PM) This to me says that even though the class data is private, it is still depending on the type definition from the old strict typedef after I converted them over. Well, what I see, is that in your MasterCluster class, you have two objects of the type SubClust1. MasterCluster is not accessing any private data. It contains two instances of the SubClust1 class. What has happened (i think) is that now the SubClust1.lvclass object control has been typedef'd. The actual private data is not linked to the typedef. Class private data is not a typedef anyway. It's a special Class Private Data type. If you open up the class private data structure and right click on the cluster you will see that you can't customize it. This means it's not linked to the typedef. QUOTE(orko @ Sep 3 2007, 02:02 PM) I guess I understand what is going on, and why...but I do not understand why this be desirable behavior... Why would I need to go through my entire class heirarchy after converting to classes and one-by-one disconnect them from their original typedef? As I discussed, the new class private data IS disconnected, so there is no real problem here. I agree it's a little annoying and perhaps an autodisconnect should take place, but if that happens then it might not be expected and could confuse those that expected it to behave the way it does.

QUOTE(Aristos Queue @ Sep 2 2007, 08:16 AM) The problem is that the environment doesn't do it how I like it. It's just not "smart" enough. You guys need to work on it some more. Don't get me wrong, I do use some of the new productivity enhancements: autowiring and (i love) autotool and Express VI configuration on drop (but i don't use Express VI's). Any others you want to query me on?

Are you trying this in LV8.5? I just tried what you described and it worked as expected.

I've used this with LabVIEW in the past with excellent success: Creating a (system tray) Notify Icon Using .NET Framework 2.0

QUOTE(Eugen Graf @ Aug 29 2007, 06:16 AM) You use the alignment grid? I never use it so I can't tell ya. I don't even show the lines.

Those of you that are familiar with facebook, and who isn't, can now join the LAVA group. have a great weekend!

I don't know those models but one suggestion I can make: Get dual core. makes a big difference in general.

The only way to create custom methods or properties is using the cool and awesome XControls which are only available on LV 8.x and above.

QUOTE(chrisdavis @ Aug 24 2007, 08:01 PM) That's it? Not nearly often enough in my opinion.

Maybe NI should take an example from this marketing video for Windows 386 as an example of how to promote multicore processing. Be patient, it get freaky towards the middle. <embed style="width:400px; height:326px;" id="VideoPlayback" type="application/x-shockwave-flash" src="http://video.google.com/googleplayer.swf?docId=4915875929930836239&hl=en" flashvars=""> </embed>

Today and tomorrow, there is a Google Test Automation Conference taking place in New York. http://www.youtube.com/view_play_list?p=7D3E685B59779C16 It's unbelievable how quickly these videos have gone up. QUOTE Question, how do all of you perform testing on your LabVIEW VI's?

QUOTE(crelf @ Aug 23 2007, 08:25 PM) That's Hot! QUOTE(Justin Goeres @ Aug 23 2007, 08:40 AM) "Engineers at the University of California, San Diego have constructed the highest-resolution computer display in the world – with a screen resolution up to 220 million pixels." Great, now I have to put a request in at JKI for a new monitor...

QUOTE(jaegen @ Aug 23 2007, 08:50 AM) I agree with jaegen on this one. Single EXE build needs to be a future feature. This restriction alone will turn off many from adopting Classes. Let's not forget that people (including myself) have been building successful test systems for 20 years before classes were introduced. Even without classes, work can still go on as usual - until NI forces us to use classes (which they probably will). I'm in favor of classes, I'm using classes in customer projects, but the more gotchas you present, the harder it is to convince people.

Fixed. I think this happens when the original image size is too big.

I would like to see the ability to locate a VI in the project tree. One way to expose this would be to right-click on a VI Icon (on the diagram or top-right corner icon) and select "Locate in Project" from the menu. This would open the project tree and highlight the VI in the tree.

I've been so busy these days, what with NIWeek and other personal\business stuff that this just went by unnoticed. I'd like to a draw everyone's attention to Ton's Blog. He's very active on my favorite topic of XControls. Good luck Ton and I'm looking forward to more great stuff on your blog and eventually cool new stuff in the code repository. :thumbup: http://forums.lavag.org/blog/tonsplans

QUOTE(i2dx @ Aug 20 2007, 01:24 PM) Why is this not the right place? NI never had a venue like this before and as such, had no way to properly release scripting until now. QUOTE(i2dx @ Aug 20 2007, 01:24 PM) e.g. If there were hundreds of users of my ADO toolkit, who would request a special feature in my forum, I guess, I'd consider this as spam. If there were hundreds of users for your ADO toolkit requesting features then I think you would implement the feature since it obviously is something you can sell. I think this is a good problem to have then having no users. QUOTE(i2dx @ Aug 20 2007, 01:24 PM) I think NI knows that there is a strong demand for this feature, but NI does not want to spread this feature right now (most probably due to "who should support this stuff"-reasons?). By being in NI labs, they are shielded from the support issue. Support happens through the forums. QUOTE(i2dx @ Aug 20 2007, 01:24 PM) third: I tried to make a post at the ni.com forums, but I don't know how. I have definitively an account and I am a registered member, but I couldn't find the response button to your post :blush: The reply button is right above my name: http://forums.lavag.org/index.php?act=attach&type=post&id=6693 If this is the real issue then just say so from the start.

QUOTE(crelf @ Aug 18 2007, 06:58 AM) Ya, I love that shirt. I also wore it to the Gingerman, but then I slept in it that night so then I couldn't wear it during the week. They sell them at the Austin airport, I suggest you all buy one next time you land in Austin so we can all wear them at the LAVA\OpenG BBQ. 70+ people wearing tie-die shirts makes for a cool photo. Throw in some 3D glasses from Irene and you can start to reach the fifth dimension.

PS. If you have any comments on the technical aspects of the video, lighting, camera angles, editing, audio etc., please post in this thread. If you want to comment on a specific video's content please add a comment at the bottom of the specific video. I'm excited to hear feedback on how we did. I'm not sure if I'll do this next year, but if I do, I would like to do better.