Copy/paste components loses position data!?!?

i have a bunch of buttons i need to copy from one component to another. i just noticed that when i do, NONE of the copied components retained their position data. they are all smashed up in the top corner with microscopic values for x, y, width, height. (and what ARE those units anyway? pixie-nipples-per-smashed-frog??) is there a modifier key to keep those properties? i tried the context menu as well, same result.

You need to be more specific rather than rant.

  • What "component" are you copying the buttons from and pasting them into?
  • What is the root container?
  • If it's a coordinate view, what is its mode?

doesn't matter what. i copy a button from tab and paste to coordinate: zeroed out. copy ANYTHING from ANYWHERE to ANYWHERE and the position data is zeroed. table? zero width, height, x, y. label? same. copy a series of labels to a split-view. zeroed. all crammed into the top left corner. the only thing that doesn't is a flex container, but that just spreads them out to fill based on flexbox parameters.

what are you talking about? what rant? if you're referring to my parenthetical question, i literally have no idea what those units are!! 0.0207 what? it isn't pixels, it isn't inches or cm.

Results in version 8.1.25.

ComponentPaste

Regarding ruler units, see Perspective Designer Interface - Ignition User Manual 8.1 - Ignition Documentation.

1 Like

Copying between container types doesn't work, because mapping position props from one coordinate type to another is a non-trivial problem (plus, container types are extensible, so every container type would have to somehow 'know' how to convert every type to any other?).

That said, the current UX is not ideal and I'm pretty sure a ticket already exists to at least preserve the props that are already in place, or make some other attempt at improving it.

EDIT: There's at least one bug in coordinate -> coordinate pasting that's going to be fixed in 8.1.31.

2 Likes

Is this why pasting (using cut) components from i.e. flex to coordinate, and then back to flex as I quickly understand that did not work end with messing up the component?

Yes, the paste to coordinate 'lost' the flex positions, so there was nothing useful present when you went back to flex. Undo should hopefully be useful in that scenario, at least...