Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PR to Fix 396 wrong border node creation location #455

Open
wants to merge 5 commits into
base: lre/enh/426-GMFHelper
Choose a base branch
from

Conversation

lredor
Copy link
Contributor

@lredor lredor commented Sep 12, 2024

No description provided.

lredor and others added 5 commits September 27, 2024 15:36
Remove parameter in private method that is always true.
Code has leftovers after some refactoring.
- Constructors of CreationUtil have been improved to directly have
LayoutData as parameter instead of location and size. Indeed, the
location is relative to the parent edit part and for border nodes, the
parent edit part is not systematically the "host" of the called policy.
- In NodeCreationEditPolicy, in case of border nodes, the "host edit
part" is not systematically considered (to compute the RootLayoutData
for example). The correct edit part, a parent of the host, is computed
according to the mapping defined in the used tool.

Bug: #396
@lredor lredor force-pushed the lre/bug/396-wrongBorderNodeCreationLocation branch from 00dc7d3 to ec2c328 Compare September 27, 2024 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Creation tool uses the wrong location when creating a border node from inner container in a Stack
2 participants