Duplicated custom NME node loses port order

Bugs
1

Hello!

image

After copy/paste:
image

I’ve tried to duplicate @piratejc’s OOB with the same result:
https://nme.babylonjs.com/#VDL4EQ#1

image

Can you check it please guys?

Thank you!

2

@Evgeni_Popov might have a clue ?

3

Not at all but @msDestiny14 might because she added this functionality.

1 Like
4

cc @PirateJC to track that bug

5

Heh! Yep. That’s a bug. I’ll get on that.

3 Likes
6

Issue submitted:

7

And here’s the PR for the fix! :crossed_fingers: :wink:

4 Likes
8

Hello @msDestiny14, hi guys!
Is this already deployed? Because today it happened again :frowning: And there is something else bad with the custom nodes handling. The custom nodes are sometimes throwing all it’s children outside the frame on save, sometimes it just erases a whole custom node and have to wire it again. :cry: I will try to reproduce it and let you know. Thank you!

9

The change was merged after nightly and we don’t do it over the weekend but it will be in the Monday. :slight_smile:

As for the other issue if you can get a repro on it feel free to post it in another thread and I’ll take a look.

1 Like
10

Sure, thanks!