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

fixed renderControls order #9914

Merged
merged 3 commits into from
Jun 10, 2024
Merged

Conversation

DaxGama
Copy link
Contributor

@DaxGama DaxGama commented Jun 6, 2024

Fixed controls render order for ActiveSelection

Before
Child controls renders over ActiveSelection
image

After
ActiveSelection controls renders over child's
image

This is my first contribution to this project, please let me know if I have missed out anything.

Copy link

codesandbox bot commented Jun 6, 2024

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@asturur
Copy link
Member

asturur commented Jun 6, 2024

This is a bit of really a preference issue. In which case do we have both group and child selected? that is the first thing to understand. It shouldn't happen in theory.

The screenshot doesn't really give out many informations, could you make a small example with a code snippet of what are you running and how you ended up in a situation that didn't make sense to you?

@DaxGama
Copy link
Contributor Author

DaxGama commented Jun 6, 2024

HI @asturur I realised I did't descirbe it well. This is the logic for ActiveSelection not group.

The scenario is simple, when ever you select multiple objects, the borders of _objects is drawn over the border of selection.

The _objects are explicitly set by code to not render controls, so there won't ever be a scenario where conrols of _objects are render under the active selection.

@asturur
Copy link
Member

asturur commented Jun 6, 2024

ok so the borders, no the controls.
In that case this could make sense. I need to think carefully with nested selections, but with active selection that is never the case.

@asturur
Copy link
Member

asturur commented Jun 10, 2024

this should be ok. If it turns out it isn't i ll have to revert.

@asturur asturur merged commit c820dd6 into fabricjs:master Jun 10, 2024
19 of 22 checks passed
@niketaOptimumnbrew
Copy link

this should be ok. If it turns out it isn't i ll have to revert.

Hi @asturur
I have the same issue with active selection , can you please tell me that how did you resolve that issue?

@asturur
Copy link
Member

asturur commented Jul 3, 2024

hi @niketaOptimumnbrew you should open a PR on the 5.x branch that looks like this one, do you think you can?

@niketaOptimumnbrew
Copy link

niketaOptimumnbrew commented Jul 3, 2024

hi @niketaOptimumnbrew you should open a PR on the 5.x branch that looks like this one, do you think you can?

hi @asturur
Thank you :)
I got the answer.

@asturur
Copy link
Member

asturur commented Jul 3, 2024

i opened one few hours ago with many fixes

@niketaOptimumnbrew
Copy link

i opened one few hours ago with many fixes

from where can i check opened issue?

@asturur
Copy link
Member

asturur commented Jul 5, 2024

https://github.com/fabricjs/fabric.js/pulls the first one:
#9965

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.

3 participants