-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
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? |
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. |
ok so the borders, no the controls. |
this should be ok. If it turns out it isn't i ll have to revert. |
Hi @asturur |
hi @niketaOptimumnbrew you should open a PR on the 5.x branch that looks like this one, do you think you can? |
hi @asturur |
i opened one few hours ago with many fixes |
from where can i check opened issue? |
https://github.com/fabricjs/fabric.js/pulls the first one: |
Fixed controls render order for ActiveSelection
Before
![image](https://private-user-images.githubusercontent.com/11871242/337251897-ec9cdcbf-972e-4a8b-95a8-1e62fbb05a8b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MDg0OTYsIm5iZiI6MTczODkwODE5NiwicGF0aCI6Ii8xMTg3MTI0Mi8zMzcyNTE4OTctZWM5Y2RjYmYtOTcyZS00YThiLTk1YTgtMWU2MmZiYjA1YThiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDA2MDMxNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBmNzk0NGVjYjk4OGUxY2JmMzYxNzk3OTA1M2Y3NWZhZGZjNjFmZTYyNWViNTg3NDhlOGU3NzYyYTU0ZWRkOTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.XJBnio24K0YIpersP_Ebfl7keUwWUvsJHA_EdSgrhCI)
Child controls renders over ActiveSelection
After
![image](https://private-user-images.githubusercontent.com/11871242/337252189-ac54f824-22b9-4090-a1a3-c54c118ef9ac.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MDg0OTYsIm5iZiI6MTczODkwODE5NiwicGF0aCI6Ii8xMTg3MTI0Mi8zMzcyNTIxODktYWM1NGY4MjQtMjJiOS00MDkwLWExYTMtYzU0YzExOGVmOWFjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDA2MDMxNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTdhZjc1MzgyYmU4ZWUzODNjZDU3YWMzZmFiMzE3YzdmZWYzODVkYjMyYTI0YWNkMzkyMjI4NmVkZWZmNjk4MTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.vg5PB7ucjjEurmGCRZQtbE-F1wnFMGjDCE6t5MRa_g0)
ActiveSelection controls renders over child's
This is my first contribution to this project, please let me know if I have missed out anything.