-
Notifications
You must be signed in to change notification settings - Fork 11
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
🐛Fix context menu and components panel spawn coordinates #169
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it's fixed on my end, great work! The context menu and component list spawn correctly near the click point.
If I had to nitpick, maybe the spawn coordinates for the most bottom location might be shifted upwards for a few pixels so users can see the, Add Comment Component
option, but otherwise this is good enough already.
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. The bottom spawn went the other direction than expected.
I've tried some changes myself, it was pretty manual for my tastes but it does fix it.
https://gist.github.com/MFA-X-AI/0f4570dae5e8dccf777189a87c5670d0#file-gistfile1-txt-L1601-L1622
Let me know if there's a smarter way of doing it. 😄
Thanks for noticing this bug. Don't know why I've to add some additional offset when it height changed. Currently, it's not possible yet to get a dynamic height(Though, the width is fine idk why). The way things works is everytime adding/removing an options, the offset need changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okayy..Was not expecting that. Good job for finding that bug. Anyway, will work on fixing that. |
Figured out what causing it but not sure why... I guess it's probably because the canvas bottom area goes outside of the screen. Thus, getting its exact bottom position is a bit difficult. Right now, I just only use the top position for the y-axis. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description
This will fix context menu and component panel from rendering at the wrong position.
Pull Request Type
Type of Change
Tests
.xircuits
fileTested on?