# TS3 and Sequoia

**URL:** <https://discuss.binaryage.com/t/ts3-and-sequoia/8753>\
**Category:** TotalSpaces\
**Tags:** question\
**Created:** [September 16, 2024, 8:21pm UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753 "2024-09-16T20:21:37Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![tarkine](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/t/ccd318/32.png) [@tarkine](https://discuss.binaryage.com/u/tarkine)\
**Post date:** [September 16, 2024, 8:21pm UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/1 "2024-09-16T20:21:37Z")

</div>

Using my M1 2020 Macbook to install Sequoia 15.0, TS3 works fine so far. The only difference I can see from using it on Sonoma is that it has an alert window that appears asking to permit TS3 to access audio and video directly and not go through the “Private Window Picker.” No idea what the PWP is, but another app I have called Mosiac asks for the same permission. Granted the permission for both for one month. Would like to know from the developer, if you are scraping audio and video data from your TS3 users, why are you doing that if you are not developing the app?

---

<div class="post-metadata">

**Author:** ![funk](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/f/d07c76/32.png) [@funk](https://discuss.binaryage.com/u/funk)\
**Post date:** [September 19, 2024, 8:12pm UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/2 "2024-09-19T20:12:49Z")

</div>

It may be a change in the framework or how it’s presented in the OS, but you’re not going to get a response from the dev as they no longer seem to support the software.

Otherwise though, does TS3 seem to be working fine without any new issues compared to Sonoma? I was thinking of upgrading soon and that’s god info to have.

---

<div class="post-metadata">

**Author:** ![StegosaurusFriend](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/s/6f9a4e/32.png) [@StegosaurusFriend](https://discuss.binaryage.com/u/StegosaurusFriend)\
**Post date:** [September 20, 2024, 5:18am UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/3 "2024-09-20T05:18:53Z")

</div>

TotalSpaces3 seems to be working about as well on Sequoia as it did on Sonoma and Monterey (I didn’t try Ventura) – that is, not as well as TotalSpaces2 on earlier versions of MacOS but still much better than Stage Manager or Mission Control have ever been. I don’t see a difference between its performance in Sonoma and Sequoia.

---

<div class="post-metadata">

**Author:** ![chobitz](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/c/90db22/32.png) [@chobitz](https://discuss.binaryage.com/u/chobitz)\
**Post date:** [September 21, 2024, 3:31am UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/4 "2024-09-21T03:31:53Z")

</div>

Thanks for the useful info.  
I have a question for those who have updated to Sequoia.  
Is it possible to move a window (instance of an application) from space to space in Sequoia’s grid view?  
It does not work in Sonoma.

---

<div class="post-metadata">

**Author:** ![tarkine](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/t/ccd318/32.png) [@tarkine](https://discuss.binaryage.com/u/tarkine)\
**Post date:** [September 21, 2024, 7:27pm UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/5 "2024-09-21T19:27:11Z")

</div>

@chobitz - I can move apps between spaces in TS3’s grid within a single window/screen. For two screens, only when the app is displayed on a single screen and not in the grid view.

---

<div class="post-metadata">

**Author:** ![chobitz](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/c/90db22/32.png) [@chobitz](https://discuss.binaryage.com/u/chobitz)\
**Post date:** [September 23, 2024, 2:35am UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/6 "2024-09-23T02:35:42Z")

</div>

@tarkine  
Thanks for your reply!  
So even in Sequoia you couldn’t move windows or apps from space to space in grid view?

---

<div class="post-metadata">

**Author:** ![tarkine](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/t/ccd318/32.png) [@tarkine](https://discuss.binaryage.com/u/tarkine)\
**Post date:** [September 24, 2024, 12:09am UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/7 "2024-09-24T00:09:02Z")

</div>

On a single screen I can move apps between grid spaces, i.e., I can move an app between left screen grid space 1 to left screen grid space 12. But on two screens, the apps need to be in an app window, not a grid space, to move to another app window, i.e., on the left screen an app is open in the window (that compresses to left window grid space 1 when the grid is invoked.) On the right screen, there is no app in the window (that compresses to right screen grid space 9,) so I can move the app in the left screen window to the right screen window. TS3 isn’t like Mission Control where you can move apps across screens to MC’s spaces on MC’s lattice at the top of the window.

---

<div class="post-metadata">

**Author:** ![K\_D](https://discuss.binaryage.com/user_avatar/discuss.binaryage.com/k_d/32/3828_2.png) [@K\_D](https://discuss.binaryage.com/u/K_D)\
**Post date:** [September 29, 2024, 4:52am UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/8 "2024-09-29T04:52:39Z")

</div>

It doesn’t work basically based on my experience with TS3 and Sequoia. App windows cant be moved from one space to the other in TS3. It shows an animation but the window doesn’t really get moved.

---

<div class="post-metadata">

**Author:** ![K\_D](https://discuss.binaryage.com/user_avatar/discuss.binaryage.com/k_d/32/3828_2.png) [@K\_D](https://discuss.binaryage.com/u/K_D)\
**Post date:** [October 1, 2024, 3:11pm UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/9 "2024-10-01T15:11:09Z")

</div>

Actually, this feature of moving window between spaces in the grid preview is no longer working since some recent updates of sonoma. I spent some time trying to figure out whether this can still be savaged somehow. Some other apps have reported success, and I can confirm move window across spaces is indeed possible in yabai and amethyst at least in latest sonoma.

> <https://github.com/koekeishiya/yabai/issues/2380>
>
> I recently upgraded to MacOS 15.0 and reinstalled yabai so all other commands li…ke switching spaces and window focusing works.
> 
> However, moving windows to different spaces no longer works:
> 
> \`\`\`
> \# send window to a space
> rcmd - 1 : yabai -m window --space 1
> \`\`\`
> When I run this, the focused window still remains in the current space. This code worked before the MacOS 15.0 upgrade.

---

<div class="post-metadata">

**Author:** ![K\_D](https://discuss.binaryage.com/user_avatar/discuss.binaryage.com/k_d/32/3828_2.png) [@K\_D](https://discuss.binaryage.com/u/K_D)\
**Post date:** [October 3, 2024, 8:25pm UTC](https://discuss.binaryage.com/t/ts3-and-sequoia/8753/10 "2024-10-03T20:25:35Z")

</div>

Well, seems still broken even in other software:

> <https://github.com/ianyh/Amethyst/issues/1676>
>
> \*\*Describe the bug\*\*
> I'm able to move windows to different displays just fine.
> …
> I'm unable to throw a window to an absolute or relative desktop/space. The default key bindings are ctrl+alt+shift+\<left/right\> to throw the focused window to the prev/next space and ctrl+alt+shift+\<num\> to throw the focused window to the \`num\`-th space
> 
> \*\*Applications:\*\*
> All applications
> 
> \*\*To Reproduce\*\*
> Steps to reproduce the behavior: 
> 1. Launch Amethyst
> 2. Launch any application and open a window
> 3. Create a new space/desktop
> 4. Use ctrl+alt+shift+arrows to attempt to throw the window to the next/previous space
> 5. Use ctrl+alt+shift+num to attempt to throw the window to the \`num\`-th space
> 
> \*\*Expected behavior\*\*
> The selected window should move to the next/previous space, or the \`num\`-th space.
> 
> \*\*Screenshots\*\*
> None
> 
> \*\*Versions:\*\*
> - macOS: 14.6 (23G80)
> - Amethyst: 0.21.0 (110)
>  
> \*\*Debug Info\*\*
> \`\`\`
> $ /Applications/Amethyst.app/Contents/MacOS/Amethyst --debug-info \[--include-apps\]
> \`\`\`
> Note: \`--include-apps\` will list your manageable applications, but is optional if you don't want to list that.
> 
> \`\`\`
> Version: 0.21.0 (110)
> 
> OS version: Version 14.6 (Build 23G80)
> 
> Screens:
> (0.0, 0.0, 2560.0, 1440.0) \[(0.0, 0.0, 2560.0, 1440.0)\]
> (-1792.0, 169.0, 1792.0, 1120.0) \[(-1792.0, 151.0, 1792.0, 1120.0)\]
> (2560.0, 0.0, 1920.0, 1080.0) \[(2560.0, 360.0, 1920.0, 1080.0)\]
> 
> Configuration:
> screen-padding-left: 0
> floating: (
> {
> id = "com.jetbrains.pycharm";
> "window-titles" = (
> );
> },
> {
> id = "com.apple.Terminal";
> "window-titles" = (
> );
> },
> {
> id = "com.googlecode.iterm2";
> "window-titles" = (
> );
> },
> {
> id = "com.agilebits.onepassword7";
> "window-titles" = (
> );
> }
> )
> enables-layout-hud-on-space-change: 0
> focus-follows-mouse: 0
> window-minimum-width: 0
> new-windows-to-main: 0
> window-resize-step: 5
> window-max-count: 0
> float-small-windows: 1
> restore-layouts-on-launch: 1
> ignore-menu-bar: 0
> enables-layout-hud: 1
> layouts: (
> tall,
> wide,
> fullscreen,
> column,
> bsp
> )
> debug-layout-info: 1
> screen-padding-right: 0
> floating-is-blacklist: 1
> window-margin-size: 1
> use-canary-build: 0
> mouse-follows-focus: 0
> screen-padding-bottom: 0
> window-margins: 0
> follow-space-thrown-windows: 1
> mod2: (
> option,
> shift,
> control
> )
> window-minimum-height: 0
> mod1: (
> option,
> shift
> )
> screen-padding-top: 0
> \`\`\`
> 
> \*\*Additional context\*\*
> N/A
