Copy & Filter Editor

I don't know if this is a bug or a setting.
Anyway it is something that in my opinion should be solved.

When we copy some component and we paste them in another filter, Filter Forge should copy that component or those components as they are, without messing or changing them. Instead it seems that it doesn't happen.

The cases are two :

1. The components that we copy receive an input from other components not copied in our selection.
This case I understand that, because some input was not included in what we copied, our copy will have some differences from what we copied, being some connections missing. This is not a problem and it is just up to our choice.

2. The components that we copy receive no input from other components not copied.
This means that we copied a whole branch of the filter or the whole filter.
This case it should not happen that, when we copy something, the copy is different from the copied components.

The problem doesn't happen when we copy and paste something without closing the filter editor.
But, because we can't edit two filters at the same time, we can't copy something from a filter to another without closing the filter editor, it would be useful that this thing was solved.

Sometimes copying something even gives curious errors that appear or disappear without any clear reason ( at least not clear for me. But I'm not a programmer, so I can't say more ). Here is what I mean : ???? Group copy ????

Anyway small errors appearing in some situations aren't a particular trouble and I report them only in case FF wants to know them.
Instead having a "Copy" working well also when we close the filter editor ( Attention. I don't mean "when we close FF", but simply the editor. It is clear that, if we close the program, FF should not keep record of our last copy ) would be very useful to copy part of filters, snippets, etc. from a filter to another.
Otherwise, for example, what's the meaning of having snippets if, when we copy them in a filter, they lose their original characteristics?

Ramlyn, could you please provide a refined example filter that only shows the issue and doesn't have anything else. Our testers won't be happy to debug the entire component tree of Extreme Pixels.

( P.S. "behavior" with that strange "*" is not my ironic comment. Ha! Ha!
It is again the forum doing something wrong )

Yes, the tester is right. The problem was in the "Pixel, size" value in the Result component.
Thank you very much for your help. It was very useful.