Processing undefined values on a Menu Ring indicator

[Kaspar]

Hello,

   I am using a Menu Ring as a indicator to perform a "captain midnite decoder ring" for 1 byte hex values that come from the hardware I am working with. Since the 1 byte hex value can have 256 possibilites I do not want to have a menu ring with every possible value. Currently when a undefined value is received by the Menu Ring Indicator the Menu Ring display the value it received with open and close carrots, which is not always obvious to a "non programmer" person that a undefined value is present.

  I was thinking of putting a case structure infront of the Menu Ring indicator that would "screen" the input values to the currently defined values.

Regards,

Kaspar

[smercurio_fc]

Carets, not carrots. Let's keep Bugs Bunny out of this.

You don't need to do anything all that complicated for this. You can create an "UNDEFINED" value that has a value of -1, and then just use the "Values" property to search for the input value in the list of values you have. See attached.

Message Edited by smercurio_fc on 07-09-2007 09:47 AM

[Kaspar]

Thank you! I will try it out!

[Ben]

That's not fair!

Blue property nodes are "right out" (operating instructions for the Holy handgrenade, MP's Quest for the Holy Grail) 

Ben

[smercurio_fc]

Hah! You know I wrote that example so fast I hadn't even noticed!

[smercurio_fc]

A more "technically" correct version based on not using blue property nodes:

Message Edited by smercurio_fc on 07-09-2007 10:45 AM