Yes.
The only way is to obtain both rectangles aligned is to resize each rectangle separately.
I don’t.
Ok. So the value in all that detail is, the Backing Object, which may come in handy as your grouped Objects progress and mature.
Understanding
If I may say so …
The issue you have in intellective, and typical of people with an OO mindset. The larger problem is the suppression of the hierarchy. The specific problem is, they want both the total independence of each Component, and also the total integrity of the Group [grouped Object]. This is the Inheritance problem that they have never resolved. It is not an exclusive choice at the Object level. It is to be understood that in any given Object, due to multiple inheritance, several channels of access exist and that when using one channel of access, the others will be negatively affected.
In this example, there are only two such channels, but that is enough to expose the issue. The resolution is to apply the Grouping last: easy in a compiler, but impossible in a tool that works from the finished product (an OO Object or a OG grouped Object) backwards. One must be clear in the intent, when approaching a grouped Object on one channel, and not expect the behaviour of the other channel:
- either change the grouped Object
- xor change one or more Components of a grouped Object
As demonstrated here, the correction was at the intellective level, the expectation.
Cheers
