Variable Names with umlauts?

Does Indigo support variable names with umlauts?

I assume it does because a user has reported a problem in the Alexa-Hue Bridge plugin which was due to having an umlaut in a variable name.

However, I have tried to create one and Indigo won't let me do this via the UI. I tried a copy and paste (or tried to ) of a name with an umlaut. The paste was ignored. Pasting a non-umlauted name works OK.

So I used a script to set a name:

Code: Select all

>>> newVar = indigo.variable.create("OütputT", "true")

I then displayed it:

Code: Select all

>>> newVar
<indigo.Variable object at 0x113427b18>
>>> newVar.value
u'true'
>>> newVar.name
u'O\xfctputT'


However, now when I go into the Indigo main Variable List window, and select the variable, the New..., Duplicate and Delete... buttons are greyed out and non-clickable.

Umlaut Problem

Screenshot 2019-06-15 at 17.41.51.png (48.89 KiB) Viewed 1727 times

If I select a standard named variable I get the Duplicate and Delete... buttons.
If no variable is selected the New... button won't display.

Is this a bug or have I done something wrong?

who needs umlauts ?

Germans

Always the Germans
Mit freundlichen Grüßen
Karl

Sent from my iPhone using Tapatalk

Does Indigo support variable names with umlauts?

I followed all your steps and the Indigo UI buttons for New, Duplicate, and Delete were all working as expected.

Not sure what's going on.

... Not sure what's going on.

Me neither.

Just restarted my Indigo server and now it is working.

As soon as I click New... variable and past in a name with an umlaut, which doesn't work, the New... disappears.

If I click New and delete the default name 'variable' the New button disappears, too. That may be expected behavior.

I, too, can't paste the name with an umlaut.

... I, too, can't paste the name with an umlaut.

That's good to know - it's not just me then!

[matt (support)]

It is intentional that Indigo filters non-alpha/numerical characters in variables name as you type them. Pasting them appears to fail in a not very friendly manner it looks like – we'll look into that. We might lift some of the restrictions on variable naming – we intentionally had them locked down because years ago we were not sure how we would expose Indigo's variables in various scripting languages so keeping them very restricted seemed like the safest approach.

Also, as you all have noticed, our variable filtering/enforcing code on the API/plugin side don't match what the UI enforces. We'll look into that as well.

OK - Thanks for the update.