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

Highlighting instance rectangle of deleted object does not disappear #6067

Open
1 task done
f0nar opened this issue Dec 12, 2023 · 3 comments
Open
1 task done

Highlighting instance rectangle of deleted object does not disappear #6067

f0nar opened this issue Dec 12, 2023 · 3 comments
Labels
😤Non optimal UI A bug/issue where the UI is usable but not optimal

Comments

@f0nar
Copy link
Contributor

f0nar commented Dec 12, 2023

Is there an existing issue for this?

Describe the bug

If instance of object that you are going to delete is under the mouse cursor after deleting dialogs the highlighting instance rectangle is present until you hover smth else

record

Steps to reproduce

  1. Create object (was tested on tilemap, text, spine)
  2. Create its instance on scene
  3. Scale and place instance to make mouse hover it after deleting dialogs
  4. Right click on appropriate object in object list
  5. Select delete
  6. Yes to everything

GDevelop platform

Desktop

GDevelop version

5.3.183

Platform info

OS macOS Venture 13.5.2

Additional context

No response

@ClementPasteau
Copy link
Collaborator

Thanks for the issue and for the video 👍

I can indeed reproduce the problem.
Have you seen any crashes following this situation?
It feels to me as if it's only a temporary rendering issue but I may be wrong.

@ClementPasteau ClementPasteau added the 😤Non optimal UI A bug/issue where the UI is usable but not optimal label Dec 13, 2023
@f0nar
Copy link
Contributor Author

f0nar commented Dec 13, 2023

HighlightedInstance caches instance and continue to call render with it. Nothing is crashed with objects I tested it on due to simple implementation of getWidth/Height/Depth but if one of these methods try to work with _associatedObjectConfiguration then it will throw error (It was my case with spine but I fixed that).

@ClementPasteau
Copy link
Collaborator

Definitely deserves taking a look then, thanks for the details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
😤Non optimal UI A bug/issue where the UI is usable but not optimal
Projects
None yet
Development

No branches or pull requests

2 participants