Bug in virtual sensors command line?

[Hathor27]

If I hit a command line for virtual sensors, such as

Code: Select all

awk '{if ($3<150) {printf "%d", 200-$3} else print "0"}'

and press save, Meteohub takes this command string and works fine with it.

But if I want to edit this command line, I just can reach the first 26 characters of it

Code: Select all

awk '{if ($3<150) {printf 

Boris, could please enlarge that input field?

[admin]

Hard to believe that you cant reach the other letters. Did you try moving the cursor with the arrow keys. The field does scroll then, when I do remember right.

[Hathor27]

Hard to believe that you cant reach the other letters. Did you try moving the cursor with the arrow keys. The field does scroll then, when I do remember right.

I'm sorry to say that, Boris: I tried it several times, scrolled left and right - no chance at all

[skyewright]

Boris, could please enlarge that input field?

If I look at the html source of the form it shows maxlength="458" for that field!

By curious coincidence my virtual command lines are exactly 26 characters long, so I can't test for the behaviour you have seen without making a change that would invoke a (very long) recompute.

Could it be a browser issue? Which browser are you using? Have you tried looking at the form in a different browser.

[Hathor27]

Could it be a browser issue? Which browser are you using? Have you tried looking at the form in a different browser.

I'm using the good old standard: Internet Explorer 8

Uses anybody virtual command lines exceeding 26 characters?

[d_l]

I've a command line of 158 characters that I can scroll to the end. This is on 4.6t. I doubt that Boris reduced that field for newer versions. Scrolling using FF 4.0.1. I don't update that frequently unless there is a good reason.

[Hathor27]

I've a command line of 158 characters that I can scroll to the end. This is on 4.6t. I doubt that Boris reduced that field for newer versions. Scrolling using FF 4.0.1. I don't update that frequently unless there is a good reason.

I recognized the problem in v4.8i, and it persists in v4.9 - good idea not to update that frequently...

[admin]

I cannot confirm the error. Is it just an IE8 issue? Did you try other browsers?

[Hathor27]

I cannot confirm the error. Is it just an IE8 issue? Did you try other browsers?

No I didn't another browser - I only run on IE8 (standard?).

Is there an other way to test it? Are you able to test it on IE8?