Child Dialog Becomes Non-Interactive Once Parent Dialog Is Clicked If Child Overlaps Parent

Open
#154 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
desktop

Research direction

Start by reproducing the issue with overlapping parent and child dialogs, clicking the parent, and then interacting with the overlapping child area. Trace the dialog parenting and input-routing behavior, including the timer-based repositioning described in the report. Done means the child remains interactive after the parent is clicked without closing and reopening it.

Written by the indexing model from the issue text.

Description

Aseprite v1.3.16.1

When trying to use a sub dialog via parenting the sub dialog becomes non-interactive if the parent dialog is clicked, this will now no longer take input on any part of the child dialog that is overlapping the parent.

Input seems to be passed to the parent instead of still taking input on the child when trying to interact with it.

This can be updated by closing and reopening the sub dialog but as far as I know there is not a way to trigger this when interacting with the parent dialog.

Could maybe use a canvas to detect but also happens if any button or widget is interacted with on parent dialog which I don't believe a canvas can go over top of.

Extra context here, I am using a timer to check if the main dialog has moved and if so close the child dialog and reopen so it moves to its relative position to the parent.

https://github.com/user-attachments/assets/e668502e-a8de-40e8-b7eb-17c4682dd415

Dominant language
No language data
Stars
310
Forks
68
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aseprite/api

All issues in aseprite/api

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.