Perhaps it�s just me, but I find �Scan from String� to be quite quirky. It seems to work for some configurations and then does not on others. I am �casting� Enum rings into strings using the �Format into String� adding a comma then adding the numeric value of the Enum.
So the string looks this: �240W, 5� (The 240 �W� is actually the ohms symbol � but it appears as a W in system font) I have several other snippets of code successfully scanning similar strings with enumns back using the �%s,%d� then using a constant of the enum as the prototype for the first output node. But this particular message � won�t parse (ERR 85 in Arg 1). The Enum is not Strict type Def. nor are the others. If you read the help carefully, you can define the string handling by using the top �format String� node OR by connecting the correct default data type into the �Default Value� nodes. Even doing by defaulting the nodes � it can� t decode the string � it seems to fumble over the �W� I guess I�ll use the old tried and true �Match Pattern� which is more reliable. Jack Hamilton Hamilton Design [EMAIL PROTECTED] www.Labuseful.com 714-839-6375 Office
