Yair

I thought of mentioning combo boxes with rings and enums, but it seems that changing an element in the typedef does not update the list in the BD constant, losing the point of using the typedef. Does it work for you? Never mind, I just saw the other thread now.

To elaborate on JP's answer, I believe the port has to be different from the default one (although I'm not sure).

QUOTE(dthomson @ May 15 2007, 08:53 PM) I would do that in one of two ways - either create a subVI which will have the enum as an input and the text as an output (with an internal case structure) and make a merge VI for it so that it will be easy to drop on the BD during development or I would have the string as the enum item and wire the enum into the Format Into String primitive. That would convert the enum value to its text.

QUOTE(Jim Kring @ May 15 2007, 07:07 AM) And now the trick would be using the picture control to generate a nice diagram of them so it could be printed.

Maybe this is caused by enabling various Xnode related settings? :ninja:

I would say that of the two you would be better off with the cluster because it's named and so would be clearer. Other options - Globals. A seperate subVI for each. Rings or enums.

QUOTE(crelf @ May 14 2007, 07:39 PM) Or Sciware GOOP or Endevo\NI GOOP for the inheritance they provide. Dataact also had a version which was supposed to include inheritance (I think it was called FOOP), but I don't know if that's still around. It may have just been an experiment.

Michael, I have a email subscription to this thread, when I know for sure I did not subscribe to it, nor do I have any reply there. Did I have a reply which was removed and the system remembers the subscription or is this some fluke? P.S. The subscription date is May 10.

You're probably right.

Don't worry, you didn't mislead anyone and there's a good reason Mike did not want to elaborate in a public forum. I'll PM you, just to appease your mind.

For these to be useful, they would need to be uploaded as seperate files (and preferably incorporated into the post, so they are easy to select from). Here are Jim's icons: http://forums.lavag.org/index.php?act=attach&type=post&id=5839 http://forums.lavag.org/index.php?act=attach&type=post&id=5840 http://forums.lavag.org/index.php?act=attach&type=post&id=5841 http://forums.lavag.org/index.php?act=attach&type=post&id=5842 http://forums.lavag.org/index.php?act=attach&type=post&id=5843 http://forums.lavag.org/index.php?act=attach&type=post&id=5844 http://forums.lavag.org/index.php?act=attach&type=post&id=5845 http://forums.lavag.org/index.php?act=attach&type=post&id=5846 http://forums.lavag.org/index.php?act=attach&type=post&id=5847 http://forums.lavag.org/index.php?act=attach&type=post&id=5848 http://forums.lavag.org/index.php?act=attach&type=post&id=5849 http://forums.lavag.org/index.php?act=attach&type=post&id=5850 http://forums.lavag.org/index.php?act=attach&type=post&id=5851 http://forums.lavag.org/index.php?act=attach&type=post&id=5852 I don't feel like doing the others at the moment.

QUOTE(Mike Ashe @ May 11 2007, 05:59 PM) That wasn't quite how I would put it (although I do understand which two out of the three you are talking about), but I was thinking the exact same thing. :ninja:

QUOTE(LV Punk @ May 11 2007, 01:33 PM) I don't know SVG, so I would say PNG. It's lossless and supported by all modern browsers.

Now I think I understand. Is what you want basically an enum where you can control the numeric values (a sparse enum)? This doesn't exist in LV, but as suggested you can use a typedef ring. Just note that the strings and values are not part of the data type of the ring, so updating the typedef does not update typedef constants. To update the BD constants, you need to change the type of the ring after you change its values. You can do this by changing its representation (e.g. I32 to U32) and then changing back and applying. This will cause the constants to reload the ring from the typedef. If you want these as inputs to case structures, you can create a subVI which will translate your ring values to enum values.

Did you read the other thread?

Actually, if my understanding of C is correct, the #define directive only does a text substitution on your defined text. Since LV is strictly typed, what you're thinking of is "Const" which is typed. In any case, as mentioned in the other thread I linked to (and here), you can't actually have consts today. You can either use the method described in the other thread (which has its advantages and disadvantages) or you can use a subVI, which is safer, but takes more work to create.

QUOTE(Aristos Queue @ May 11 2007, 05:35 AM) OK, I'm amending my statement: It's not by-value, but most people seem to think that's a good thing, because they're used to by-ref OOP in LV (file functions, TCP functions, QUEUE functions) and find it very easy to understand and work with. I include myself with that group, since I still don't really understand by-value OOP (I'm still trying, though. I just have a limited amount of time for it since I don't work with 8.x) and my experience with GOOP has been with hardware, which requires concurrent access to the same instance from different places in the code. When I split a numeric wire, I don't mind what LV does with the "object". It can duplicate it or schedule it so that it can reuse the buffer, since all the data is in the wire. When I split a reference pointing to a file, however, I definitely do not want LV to create another copy, because I only have a single file. In any case, we shouldn't turn this into another "explain LVOOP" thread. I guess I will just need to learn by learning.

QUOTE(crelf @ May 11 2007, 02:38 AM) Wouldn't that be a deviant? :laugh:

You might wish to read this thread. For some things, if you're using a subVI, you won't even need a typedef.

QUOTE(TiT @ May 10 2007, 02:57 PM) What??? You do know it's allowed in the license agreement, right?

I know everyone's thinking it - alfa just isn't as funny anymore.

Sciware GOOP already handles inheritance (including overriding methods) in this fashion and works as far back as 6.1, so the wheel was already invented. :laugh: It's not by-value, but that seems to be a good thing for most people. BTW, typedef's weren't always around. I believe they've only been around since about version 5 or so.

I can't say I fully understand what you want to do, but you might wish to check out the OpenG Data Tools. Specifically, the Variant Configuration VIs which use the data tools to save and load clusters.

The one in the right is the default one, which accepts a single double. The other two seem to accept the waveform datatype, which I have no experience with, so I can't comment on those. As I said, my personal preference is the XY Graph.

QUOTE(Thang Nguyen @ May 7 2007, 06:21 PM) Why? Using the method shown by Ben or linked to in my example is usually much better than using the reference and the value property. I suggest you try it first. If you still can't get it, you should post your code so that we can see what you are actually doing.