ejbills/DockDoor

Bug: Calculator and Photos aren’t recognized

Closed this issue · 15 comments

Screenrecording.mov

Demonstration between Font Book and Calculator shows Calculator is not recognized by app.

Hoping this isnt due to localization... @ShlomoCode have you been having any other issues with localized bundle identifiers beyond our patch to fix that?

I have some questions:
And does calculator just never work? Try relaunching it? What if you make the calculator window bigger? Does it show up in the window switcher?

@ejbills Tried several times, Calculator isn’t detected. Trying to make the calculator window bigger implies activating the scientific mode and it still does not work.
When checking with the window switcher, Calculator preview does not show up.

Changing the locale back to English does not fix it.

@ejbills Are you able to reproduce the issue?

This happens for me even though the language of the system and the calculator app is English. So it seems to be unrelated to localization

Calculator works for me, not able to reproduce... could one of you dump the window info logs?

I think I found it, but I don't have time right now to work on a fix
CleanShot 2024-07-11 at 18 57 40@2x

Some more screenshots
CleanShot 2024-07-11 at 18 50 34@2x
CleanShot 2024-07-11 at 18 52 23@2x

Hmm.. that filtering is needed for other applications. Perhaps we can maintain a list of bundle IDs which are allowed to have empty window names (like calculator)?

What applications is it for?

#36

It was a fix for this issue, I didn't track the associated commit properly - but I just added the empty title check.

Maybe we could instead check by minimum window size to show up in DockDoor?

I see that alt tab uses a bunch of private CG APIs to get more information

I have the same problem with the built in Photos app from Apple.

When the Photos app is open and you hover over the app icon in the dock, there is no preview pop up.

Since the fix for #36 seems to be causing cascading effects with other apps, it might be worth reverting the changes and reopening that initial issue.

I agree

This will be addressed in the next release.