Michael Aivaliotis

Why does this NOT excite me? Oh... I know why. Because Firefox was there first! Internet Explorer 7 Released.

I disagree. I continue using ini's and still will well into the future. XML is great but it's not very human readable.

That moon pumkin rocks! Never seen anything like that before.

Check out these pumpkin computers... http://www3.uark.edu/bkst/pumpkin/

OK, I'll start it off with my masterpiece.

Ya, the moment I read that one I thought of this thread. You beat me to it.

Someone from NI circa 2000 vs. now.

How come your icon editor isn't in the CR?

That's funny... My Dream App. I already have mine. It's called LabVIEW! :thumbup:

One thing I noticed was that one of your dialog boxes had text in German. It's fed by a constant on the diagram.

This is a nice tool. It will help the LAVA members edit their VI's before submission to the Code Repository! Hey, we're dogfooding . Some issues and suggestions: When I click load directory, the second time, it doesn't remember my previous folder I navigated too. It would be nice if it took me to where I was before. During navigation of the tree I got a pop-up error. I forgot to get a screen capture. The message said something about not being able to find the file: VI Path: \\windy1\wsw\LabVIEW\SW\Projekte\DIVERSES\ICON-Editor\SERVER-ICON-Editor.vi During text entry, there is no limit of the body fields. This causes the Icon to compress when too much text is entered. I recommend an autocalculation and a text entry hardstop if too long. When editing thr VI description, it would be nice to be able to resize the window. When editing thr VI description, it would be nice to have a button that when you select a group of text you click a button "Bold" and it would wrap the text in <B></B> tags automatically. The Reload old Icon does not work if you edit the icon, save it then doubleclick the VI to open it. You cannot reload old icon anymore. It's gone? It would be nice to have the ability to apply the colorset to a group of VI's at once. That's it for now. Keep up the excellent work!

Knowledge base is for material that is in mostly text and tutorial oriented. It could also be white paper type material. The code attached in the knowledge base is there to supplant the article.Example code goes in the code repository. There is already a scripting category here. The nice thing about knowledge base articles is that a single document can live and breath by many contributors. It's better than a forum thread because it evolves as one continuous stream of data-flow consciousness. . So all it takes is for someone to start an article and then others can augment it. It's like wiki because there is revision control of the article. If someone screws up I can go back to a previous revision. Here is the single place for VI Scripting examples... Please upload your code there. For now, please prefix the submission name with the word: "Example - " Articles and write-up, how to's, should go in the knowledge base. I have added links to both KB and CR at the top of the VI scripting forum here. Hey, look out, I'm facilitating ova eea..! I think we have some very talented people here who are interested in being a part of something cool. Go with the flow. I think we should submit things individually for now. It makes it easier to reference specific examples with a link and is easier to search. The more resolution the better. I agree. Also, to wrap up my input into this. In all instances, If you are just submitting code to LAVA to show people what you've done or just want others to use your stuff, I strongly recommend putting it in the code repository. Code submission within discussion threads should be limited to situations where you want to demonstrate a point, show your problem, bug reports etc. If you just want to submit code, please use the Code Repository. Every entry in the code repository Automatically gets a forum thread assigned to it anyway, so discussions on the code can continue there. Please make sure you follow the guidelines for submission, we like clean documented code here. This isn't the LabVIEW Zone you know...

I agree, you can customize the status message text on the fly so even if the dialog doesn't do it for you can format the string and feed it in. I prefer that the dialog does a lot of the work for you. Thanks for the code. I'll make sure to incorporate it into the next release. I'm planning a lot more features for this code in the future. I just wanted to get the initial version out and get feedback. I'm planning on making it more customizable so you can make it look more to your liking. I'm planning on adding a configuration action where you would pass a cluster of parameters that would setup behaviour on start-up.

It's a pleasure to see a LAVA member comming forth and contributing tutorial\example type material. Hmm, perhaps we should open up a Scripting category in the Code Repository... :thumbup: . This code Should go there under an "examples" subcategory.

Nice idea. I guess time remaining has to be an estimate based on how long it took to execute a certain amount of work? Also a built in tally of time elapsed would be nice.

Take a look at this example code I posted a while back: http://forums.lavag.org/index.php?s=&s...post&p=8956

Your problem is described in detail but honestly there could be a million things wrong. I would look at the notifier. Perhaps you're missing notifications? Try using a queue instead.

File Name: JKI Progress Bar Dialog File Submitter: Michael_Aivaliotis File Submitted: 24 Oct 2006 File Updated: 24 Oct 2006 File Category: User Interface JKI Progress Bar Dialog V1.0.0 Copyright

Why?

Jesus guys, so tell me, what in the GUI gives you the slightest hint that holding down the mouse would give you this menu. A clever UI trick but not very usefull if only a handfull of people find it.

Just for shits and giggles, what would it take (money fame whatever) for a LAVA member to create code that converts a VI to a text representation and back? Call it a compiler, call it what you want. Sure, it isn't something for the faint of heart, sure, it can't be done over lunch. Sure, it's not your typical challenge. Let's call it the LAVA Super Grand Challenge.

I just fixed it. The URL to the video was not complete so the player was not working. Probably a copy paste mistake...

Admin Note: For the next release, perhaps you can include the older labview versions in the zip file. Another option is to develop in LV7.0 or 7.1 and release it in that version only. People can then upconvert. Just some suggestions to streamline the process.

I was using .NET once to do a tray icon. For some reason it was crashing. I discovered that it was an issue with an ActiveX call I was making while the app was minimized. It turns out that the issue was related to the front panel not having the focus. This only applies if you are using .NET to do the system tray icon.

What do you mean by by "ordinary"? These need to be API calls. Simulating keyboard strokes using a windows API should do it.