Entered label resets when immediately ctrl-selecting an earlier hierarchy unit on the same level

[m-k94]

This is a little workflow irritation that has existed for a while. I often encountered this bug when trying to very quickly create two basic ideas and group them together. Now I seem to be able to reproduce it consistently, and can give some insights into how it behaves. I did this testing on 0.6.4 on Windows, but have seen this on the Linux version as well:

Steps to reproduce:

1. have two hierarchy components on the same level (adjacent for the sake of simplicity)
2. Enter a label into the left unit
3. Now click on the right child and enter a label into it from the inspector
4. While still having that inspector open, ctrl+click on the left element, as you would do to group them
5. now click anywhere on the screen to end the selection

Expected behavior: Both labels stay as they currently are displayed

Actual behavior: The label you entered into the right component should disappear:

=>

Some interesting properties of this bug:

• The order matters. I wasn't able to make the left component's label disappear
• You can select arbitrarily many components, however, the bug only appears if they are all on the same level as the right one, and if it the one with the changed label remains the rightmost selected component
• If another label was present in the right component's label field, the bug will reset it to that state
• Calling group (g) on the selection or changing their level does not stop the bug from reseting the right label as soon as the selection is no longer active.
• The bug does not appear if the previous state of the right component's label field matches the present one of the selected component. This is why we first entered something in the left unit in step 2.
• This also applies to Marker Timeline Labels, but is not as relevant there because there is less reason to co-select several immediately after entering a label. For hierarchy components on the other hand, it's a very natural workflow.