You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I really want to use Tabby in quake mode but it becomes extremely frustrating when I work on multiple desktops on MacOS (I believe it behaves the same with workspaces on Windows). That's because whenever I launch it on a particular desktop and then switch and start working on another desktop, if I use the shortcut to get drop Tabby down (ala quake), instead of it appearing in the current desktop, it first changes desktop to the one that Tabby was on earlier. That really makes it pointless to use in a multi-desktop setup.
This happens regardless of whether tabby was previously visible on the desktop that it was initially launched on or hidden (via the shortcut for example).
Describe the solution you'd like
Whenever a user "calls" Tabby to the foreground via the shortcut for example, regardless of which desktop Tabby was previously on, it should appear in the currently active desktop and follow the rest of the user's preferences (for example in regards to docking).
Describe alternatives you've considered
Not sure if this should be the default behavior or not, I don't see any reason why would anyone in quake mode would want the current behavior.
Additional context
In case anyone is confused as to what I mean by Desktops:
Here is an example video:
I "summon" Tabby by pressing ctrl+space, then I do something in it and finally hide it by using the same shortcut again.
Then I switch to another desktop and do something else. When I finally summon Tabby again, instead of it appearing on top of Safari in the same desktop, it instead takes me back to the previous desktop that Tabby was on and it becomes visible again.
Screen.Recording.2021-12-15.at.16.16.30.mov
The text was updated successfully, but these errors were encountered:
I've just spent an evening wrenching at this without no sight of success unfortunately - there's some underlying Electron issue that prevents the window from being shown on top of other fullscreen windows unless it's been interacted with (e.g. dragged) first :(
Is your feature request related to a problem? Please describe.
I really want to use Tabby in quake mode but it becomes extremely frustrating when I work on multiple desktops on MacOS (I believe it behaves the same with workspaces on Windows). That's because whenever I launch it on a particular desktop and then switch and start working on another desktop, if I use the shortcut to get drop Tabby down (ala quake), instead of it appearing in the current desktop, it first changes desktop to the one that Tabby was on earlier. That really makes it pointless to use in a multi-desktop setup.
This happens regardless of whether tabby was previously visible on the desktop that it was initially launched on or hidden (via the shortcut for example).
Describe the solution you'd like
Whenever a user "calls" Tabby to the foreground via the shortcut for example, regardless of which desktop Tabby was previously on, it should appear in the currently active desktop and follow the rest of the user's preferences (for example in regards to docking).
Describe alternatives you've considered
Not sure if this should be the default behavior or not, I don't see any reason why would anyone in quake mode would want the current behavior.
Additional context
In case anyone is confused as to what I mean by Desktops:
Here is an example video:
I "summon" Tabby by pressing ctrl+space, then I do something in it and finally hide it by using the same shortcut again.
Then I switch to another desktop and do something else. When I finally summon Tabby again, instead of it appearing on top of Safari in the same desktop, it instead takes me back to the previous desktop that Tabby was on and it becomes visible again.
Screen.Recording.2021-12-15.at.16.16.30.mov
The text was updated successfully, but these errors were encountered: