Are firestorm edit axes broken?

[Quistess Alpha]

When 'edit linked' is on, and the whole object is highlighted, firestorm seems to choose the wrong prim as the root? This seems like a bug, but half of the bugs I see in firestorm are just "extra features" so, maybe I'm missing something?

You can clearly see the root is the box, not this prim:

So, why does it put the axes there and use its rotation rather than the root prim's rotation?

[Frionil Fang]

That's because edit linked is on: edit axis at root means when you're not in linked mode.

I don't think it's broken, it just arbitrarily puts the cursor to the last prim of the linket (as far as I can tell) when you go from non-linked to linked mode, as if it selected each piece in link order and left the cursor on the last one. If you shift-click select linked pieces, the cursor will stay where it is when deselecting, and moves to the last selected piece when selecting.

[Quistess Alpha]

On 7/17/2024 at 11:21 AM, Frionil Fang said:

That's because edit linked is on: edit axis at root means when you're not in linked mode.

Other viewers behave identically in 'edit linked' mode and 'normal' mode when the entire linkset is selected. Firestorm choosing what is essentially a random prim in the linkset if you forget to uncheck a tickbox, seems rather abnormal to me. 'edit axis at root' is also the default in other viewers, and I've never seen the axes randomly choose a non-root prim before. *sigh*.

[Frionil Fang]

1 hour ago, Quistess Alpha said:

Other viewers behave identically in 'edit linked' mode and 'normal' mode when the entire linkset is selected. Firestorm choosing what is essentially a random prim in the linkset if you forget to uncheck a tickbox, seems rather abnormal to me. 'edit axis at root' is also the default in other viewers, and I've never seen the axes randomly choose a non-root prim before. *sigh*.

That makes sense, I've given up trying to build on other viewers* so I'm very used to how Firestorm works and have never really paid attention to that particular peculiarity. Not that I have any defense for making it function differently to other viewers, it just doesn't seem broken to me since (I think) it behaves the same way every time. 

*) edit to say that I'm not saying other viewers are any worse at it, but oh boy if I don't have a lot of small widget positions and hotkeys etc. hardwired to muscle memory and I spend way too much time fighting that if I go to some other viewer.

Edited July 20 by Frionil Fang