-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
Issue with palette selection tools not staying selected persists in Archi 5.4.0/5.4.1 #1076
Comments
Can you explain in more detail what this means:
Or perhaps a screen capture to show this? |
It's because the tooltip is grabbing the focus. This is a regression from here - eclipse/gef-classic@843e56c I'll fix it. In the meantime either disable tooltips in preferences or create the connection before the tooltip shows. |
I have a fix for the next version. I'll wait until next week to release the fix in case something else shows up. |
… Tooltip - The fix in 42f4319 caused a regression on Linux Wayland - See #1076 - See eclipse/gef-classic#469
… Tooltip - The fix in 42f4319 caused a regression on Linux Wayland - See #1076 - See eclipse/gef-classic#469
Unfortunately I wasn't fast enough to record a screen video. But in the meantime the problem could be understood without it. :-) Disabling the tooltip is a much more pleasant option than frantically selecting the target object before the tooltip appears... . I also confirm the behavior that the tooltips are not displayed in the correct position, but for me this is only a small blemish and does not particularly disrupt work. Thanks for the quick response!! |
… Tooltip - The fix in 42f4319 caused a regression on Linux Wayland - See #1076 - See eclipse/gef-classic#469
Fixed in Archi 5.4.2. |
Fix in Archi 5.4.2 confirmed, THANX! |
Archi Version
5.4.0/5.4.1
Operating System
Debian 12
Archi Plug-ins
None
Description
Still have the issue with palette selection tools not staying selected in Archi 5.4.0/5.4.1 when selecting relations.
Switched back to Archi 5.3 without this issue.
Steps to reproduce
The text was updated successfully, but these errors were encountered: