Formula Node output display bug

[X.]

Here it is:

If I try to move the output sideways:

You can fix this problem by retyping the output variable names, for whatever reason.

Oh well...

[RavensFan]

How did you get these outputs to appear this way to begin with?

[X.]

Don't know,  opened up the FP and here they were.

[Darin.K]

---

@X. wrote:

Don't know,  opened up the FP and here they were.

---

Now that is what I would call a bug!

[X.]

OK, BD... Blame this on the ridiculous "no Edit after 15 min" policy (and please don't bother explaining it again).

I have provided a copy of the damn thing, so I cannot be accused of making things up or getting all excited, etc.

NI might no bother to look into it because it is not provided as a step-by-step bug report, I really don't care.

It's here, and to me it says something is fishy in the underlying code somewhere.

It is doesn't appear as a show-killer though, so nobody should lose sleep over it (yet).

[RavensFan]

It was certainly there.  I believe you.  I just couldn't figure out how to make it happen to begin.  Wondering if you had a method to reproduce it.

It is weird.

[altenbach]

Still wondering what could cause this. Did you make this VI from scratch in the current version? Did it possibly originate from a very old version or different platform? Dit it originate in a foreign language version with a different alphabet (e.g. Japanese).

Just trying to narrow down things...

I am sure NI can inspect the VI to see where the corruption is. Might give some archeological clues. 🙂

[X.]

Recent FN.

The VI itself is not recent (but there is not much if any "archaisms" in it).

[0utlaw]

I was able to reproduce this behavior in 2013 by following these steps:

1) Create a new VI.

2) Drop a formula node.

3) Add inputs or outputs to the top or bottom border.

4) Name variable input/output node just created.

5) Save

6) Close VI.

7) Repeat 5+6)

The variable name appears to shift one pixel each time it is saved and loaded.  This only appears to happen when variables on the top or bottom of the node are renamed and the position is reset when the variable is renamed.  From what I've seen, the visual glitch that arises when the variables in/outputs are moved fixes itself after any other operations that would cause a screen redraw are performed.

Regards,

[X.]

I am not sure what you mean by your last statement.

But if you move the output themselves (which should force a redraw), the output is moved but the display glitch is still there. And in fact on my machine, moving the output "drops" copies of the variable name along the path:

THAT is fixed by a "force redraw":

but as you can see, the variable names still won't fit into their designated frames.

The only fix I found was to retype the name (which oddly enough requires you to type this wherever the string happens to be - outside the frame):