Mark Balla

QUOTE(Mikkel @ Mar 15 2007, 04:01 PM) I would say you are over optimizing. In my world saving a programmer's time is a much higher priority than worrying about a few computer clock cycles. Most of the time with a modern PC you will have plenty of cpu time to spare. I doubt you can say the same about a programmer's time. Writing the same code over and over to do the same thing. Now That is just WRONG.

QUOTE(Mikkel @ Mar 6 2007, 02:31 AM) I use a simple Stop loop utility that I keep in my user lib it allows for several stop loop contitions and also has an output that tells why the loop stoped. http://forums.lavag.org/index.php?s=&showtopic=2710&view=findpost&p=9584' target="_blank">see here

Check out this post. It shows screen shots of how to make a compact icon

I am now taking nomination for the application that is to be modified by participants in Lava

It's time to start working on the next coding challenge. For this challenge I'm going to steer more towards open discussion instead of the behind the scenes committee idea. Personally I would like to see more participation and discussion as opposed to a technically and objective selection process. Using Aristos' Idea as a starting point Here are my Ideas so far. Take a week or 2 to publicly discuss the format and rules. Next we have a period where we will nominate the application to use in the challenge. After the nomination time we will vote on the application to use for the challenge. Like before the submissions will be sent to me and I will give them an anonymous name and place them in the challenge list. When the challenge is completed we will have a silent vote for the best modification/feature. If there is a lot of submission We may take the top vote getters and have a revote. Ideas I would like to discuss: Does the base application have to come from the CR or should we let people submit non CR applications. Should the author of the selected application be excluded from the challenge? How much time should we give for the challenge? Any other ideas that would make the coding challenge more interesting.

I think this is a great Idea. Thanks Aristos your my hero (again). I've been looking for a way to reduce the complexity while increasing participation and I'm willing to give this Idea a shot. I'll start a new thread to discuss.

There are some built in ones if you have loaded the NI Scope drivers.

I remember having this same problem a while back. My solution was to modify the Trigger Detection Vi so it used controls that were hidden. hope this works for you. Download File:post-584-1166593894.vi Download File:post-584-1166593914.vi Here is the 7.1 version Download File:post-584-1166594563.vi Download File:post-584-1166594577.vi

Your kidding right? My Icon editor gets the Icon form a vi via the reference. And if I recall you were the one whom approved it for the CR.

Congradulation Jeff! :thumbup: They offer the CLD at NI week you know. I'm sure you would be much more likley to pass if you are able to hang out with so many LabVIEW Gurus. Let me know when you are ready to try for the CLA. I will need a study partner. And Thanks again for your help with the Icon editor.

File Name: Mark Balla's Icon Editor Ver 2.1File Submitter: mballa File Submitted: 17 Nov 2006 File Category: LabVIEW Development Environment File: Mark Balla Icon editor V2.1 Author: Mark Balla mballa@sbcglobal.net Description: This is the second version of my vi icon editor and was created in LV8.2. The purpose is to help quickly create text base icons. The editor can be used in place of the standard NI icon editor or as a stand alone vi. see instructions. My original posting of the icon editor Ver. 1 can be found here LabVIEW 7.0,7.1 http://forums.lavag.org/index.php?s=&s...ost&p=19022 LabVIEW 8.0 http://forums.lavag.org/index.php?s=&s...ost&p=12920 Instructions: 1: The icon editor was designed to be used as a replacement for the standard NI editor LV8.x only. To get LabVIEW 8.x to use the editor place the three files (lv_icon.vi, color templates.bin and the folder lv_icon_Subvis) in the LabVIEW 8.2\resource\plugins directory. The next time the icon editor is called LabVIEW will use the lv_icon.vi instead of the standard one. There is a button on the editor that will allow you to use NI

Neat way to call the do function. It still bugs me that when I open the Parent Do cmd vi it shows me a vi that does nothing and LabVIEW gives me no option to see the child vi's block diagrams. Unless I have the project open and know to look for vis of the same name, I have no clue what is going on. This will be confusing For users who are not familiar with OOP. It breaks idea that what you see in the block diagram at edit time is the same code used at run time. I know the argument has been raised about dynamic vis doing the same thing but a dynamic vi doesn't allow me to see any code. Where an override vi shows me one of many possible diagrams. I am going to avoid override vis in my OOP projects until LabVIEW can somehow indicate and show me all of the override vis that can be called. Maybe a selector similar to the one used for a polymorphic vi would work. :2cents:

Sorry here is the 7.0 version Download File:post-584-1162306015.zip Download File:post-584-1162306071.zip No good reason realy, I guess I wanted to make it a little more universal and include more template options before I submit it to the CR.

Here is an easlier version of my icon editor. It should be easily adaptable to the your icon version. Download File:post-584-1162306015.zip Download File:post-584-1162306071.zip

Thanks

When I create a new numeric control it is created as a DBL and I would like to change it to an I32. I don't see Representation property in the control or terminal properties. What am I missing?

With the coding challenge still fresh in everyone

Congratulation zen The winner of the MG coding challenge. Here is the final vote tally Morrie aka ALPHA: 8 jsz aka BRAVO: 1 yen aka CHARLIE: 7 zen aka DELTA: 10 Thank you to all the Members That Voted: Morrie, i2dx, mballa, Khalid Ansari, kennoncotton, Mads, bsvingen, jaegen, dstudwell, Dan Press, bwgames, jhoskins, alukindo SULLutions, didierj, PJM_labview, peteski, Urs Lauterburg, JoeLabview, jsz, yen, zen, jpdrolet, Mike Ashe, tcplomp, Michael_Aivaliotis, crelf Special thanks to the Challenge Committee, Morre, jsz, yen, and zen for all their work.

I've also created vis that figure this numbering system out in the Subvi Fixer Base on the position the index is placed in a cluster that represents the pattern.

The whole toolkit installation process is kind of a pain if you want to have them installed in multiple versions on the same computer. The CD install only lets you install one version at a time. So What is the easiest way to install all the developer suite toolkits in versions 6.1 to 8.2 on the same computer?

Voting Ended 10-15-06 It's time to vote for the best Mouse Gestures submission. There were 4 submissions to the coding challenge that pass the minimum criteria. To eliminate any biased opinions we made the submission anonymous. Here are the submissions. The code is in LabVIEW version 7.1.x and 8.0.x. Download File:post-584-1157153745.zip Programmed by Morrie Download File:post-584-1157153772.zip Programmed by jsz Download File:post-584-1157153840.zip programmend by yen Download File:post-584-1157153882.zip programmed by zen (edit names updated 10-16-06) In the interest of fairness we have placed vote codes in the block diagrams of each submission. They look like this: This will help insure that everyone whom voted has viewed all the submissions. In order for a vote to count it must contain all 4 vote codes in the following format. I Vote for __________ Alpha: "Alpha vote code" Bravo: "Bravo vote code" Charlie: "Charlie vote code" Delta: "Delta vote code" EXAMPLE: Note these are not the correct codes. I Vote for ECHO Alpha: 1111 Bravo: BBBB Charlie: 2222 Delta: CCCC To vote please send a LAVA PM to -> me mballa with the voting information. Any comments on the submissions should be posted to this thread. Please make sure your comments are constructive. All of the finalist will be emailed stating if they made it to the voting process. If your are one of the four submitters we ask that you DO NOT comment about the submissions here. Voting Ended 10-15-06

Here is a ring control that I created a while back for my subvi fixer Download File:post-584-1157028237.ctl

I like the Idea that the class is the way to select the function. A little more complicated and obscure than I would like but I get it. The override SubVI implementation in LVOOP is starting to scare me though My assumptions were that static wires were only about that class and you could only operate on it's data members. It seems like the override vis are kind of breaking encapsulation. The override SubVI is able to operate on child data even though every thing on the block diagram shows a parent wire and parent SubVI. I am seeing this as possibly a huge debugging problem. If there is a problem where a bad value gets written in a child class member do to an override vi how do find it since it happened in a vi I can't see or track down. There could be potentially hundreds of overide "Do it" SubVIs that I can't see or access on the block diagram. Unless I have the project open there is no way to know if the "Do it" SubVI is being overridden and no way to fix it if I did know. For classes it seems like can

Man! do I Love this stuff. Ok here is something I've been working on since the Beta version but never got there until NI WEEK gave me an Idea. What if we create a class That uses both the by ref model and the by Value model and then inherit the class so any class can be run as a by reference. What I came up with was a class called Flip-Flop. Its purpose is to move the data to either a Variant stored in a Que (By Ref) or the Child class wire itself (By Value). In the Main Vis the class wire data is stored in the Que and when a public function receives the wire it transfers the data to the wire so it can process it. The power of this Idea is it takes full advantage of the new inheritance. Please check this new Idea Out. I'm calling it FLOOP for Flip-Flop OOP. Download File:post-584-1156262742.zip

The MG coding challenge is officially complete. Thank you to all the participants. The challenge committee is reviewing the submission and will post the top ones for a LAVA member vote soon.