![]() ![]() I'm using it myself now and it's just one click and you get a link to share, no need to upload anywhere. A user sent me a video recording with that app a few weeks back, and it's such a delight to see a problem with a nice video and audio. That way you can activate AltTab, wait, and snap.Īnother alternative is to install Loom. With "Show standard tabs as windows" unchecked in v3.19.2, now I see some strange layout issues, assuming below is the list of windows and an x stands of a window:Ĭould you please attach a screenshot? A way to do it is to launch the Screenshot app and put a 5s timer. ![]() I suspect they do option Thank you for the kind words □ We could verify at the last second if the windows are still valid. I also noticed similar issues working on Stops working when Octave-app runs #182 "Steam" windows do not show up #236, however I fixed a deeper cause that prevented these symptoms from showing up, for those 2 tickets. This seems to still be an issue, even though it's hard to pin-point what's at play: Mail.app has an extra window showing in AltTab #292 Phantom windows created by app Optimus Player #200. With any option, it may be an opportunity to also fix issues where windows go invalid without us getting noticed, and then we display incorrect windows. I think it would be a great feature for people who have lots of tabs, but since no-one asked for it yet, I guess not many people have this workflow. Given that cmd-tab + down arrow or Mission Control don't let users navigate tabs, and given that nobody has asked for that extra feature so far, I think this will go to the back-burner. They will never be known to AltTab as the app reports 1 window, and we never know that it has children windows itself.Ĭhecking for AXTabGroup like in option 2 is the only way that would allow to implement a preference to display tabs as individual windows. Option 2 and 3 don't handle one use-case: AltTab starts but they are already tabbed windows. If it's not an application, then remove it from our list. ![]() However, I don't know how robust it is to check for this AXTabGroup.Īsk every window we observe for their parent. I like that this approach only checks for the existing windows, which is a way smaller list than the apps, so less work. Then look for a child with role AXTabGroup which indicates that the window has children windows. On summon, we:Īsk every app their windows again, and when it doesn't match our current understanding (because some windows have been tabbed/split), we sync it up.Īsk every window we observe for their children. This sucks because it means more computation and more latency. Since we can't observe changes of children/parent, it means we have to detect this last minute: when the user summons the UI. Merging them into tabs won't affect that, which is a bug from the user perspective.Ĭonversely, tabbed windows made before AltTab was open will be seen as only 1 window by AltTab as they are already created, and asking the app for its children won't reveal the windows children of the main window. Current state in AltTabīecause we are not aware of these changes, windows or tabs created after AltTab is running will appear as individual windows. ![]() Splitting means they become children of the app again. Basically merging into tabs means that windows become children of other windows, instead of the application. Same for splitting into individual windows. I checked all AX notifications, and none of them detect windows merging into tabs. Indeed the OS treats windows in a strange way when they implement standard NSWindow tabs (i.e. I have been investigating this further and it's a snake pit. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |