Hi i'm on a Macbook Pro 2016 (Big Sur) and amethyst is working well except for google chrome which seems to ignore the tiling. I tried toggling the floating on chrome but this doesn't seem to change anything. Is this a known issue or something encountered by anyone before or is there a way to debug what is happening ? Google Chrome is up to date, and it works well with firefox.
Thanks :):)
Thanks :):)
You're a genius
ok i tested it and that is it. well, sorry for the spam
Glad you got it working.
Is anyone else having issues on Big Sur? Small window auto float seems to be broken for me. e.g. Evernote's top bar dropdown window (for entering quick notes) never used to be detected, but now is. Additionally, I can't seem to find it's window title to exclude it. Also finder file copy dialogs are now being detected and arranged :(
Big fan of the binary space partitioning. Three requests: option to remove rounded corners and if possible fullscreen within the partition. Second, auto float for dialogue boxes (currently opens blank partition with dialogue hovering over application) and partitions that match the size of non-resizable windows.
I’m on Big Sur and see a lot of crashing, yes. I haven’t had the time to dig into it, but it’s probably this: ianyh/Silica#10
Is there a repository of what all the listed actions actually do in Amethyst? For instance throw focused window to space 4? What does that mean? Also, I am wondering about Focus screen 1 Focus screen 2? I am using an external widescreen in addition to my iMac for data analysis. Does the focus mean I am shift focus between these two screens?
Hi folks, I was wondering if its possible to move windows to new workspace automatically without having to create it first?
For instance, moving a window to a new workspace would actually first create the workspace and then move the window to that workspace.
Finally, if the only window on specific workspace is closed then the workspace is automatically destroyed.
For instance, moving a window to a new workspace would actually first create the workspace and then move the window to that workspace.
Finally, if the only window on specific workspace is closed then the workspace is automatically destroyed.
I’m not sure I totally understand the issue.
You can look at floating configurations if so.
Let me give a concrete example, I'm using thunderbird as my email client, whenever I sent an email a small dialog box opens in email client showing the progress. Now if I'm on a workspace with Tall/Column layout opening thunderbird will occupy the full screen real-estate, that's nice, so far so good. Now upon sending an email the popup progress bar of the email client will show up which then will immediately be scaled to occupy the half real estate of the screen while the other half will be occupied by the email client which will be resized due to the Tall/Column layout.
The problem is that amethyst perceives the progress bar dialog box which is part of the email client as being a separate app with its own window which tries to scale accordingly due the Tall/Column layout. This happens for other apps as well, e.g. calendar.
I don't know the exact details behind the scene of amethyst but there must be something informing amethyst what app/window/ or part of app must be scaled and how. I think this should not apply for popups or dialog boxes which are part of the actual app occupying currently the workspace, like my previous example with the email client.
Window managers on macOS are hacked together using a set of APIs that are not intended for this use and a set of APIs that are private and undocumented.
It is sometimes difficult to distinguish between a dialog and a “real” window because from the perspective of the operating system they are both “real” windows. L
There is a way to distinguish things that are dialogs, but only if the given application uses the relevant distinguishing objects, which they are (a) not required to do and (b) not motivated to do for a variety of reasons that are somewhat technical and specific to implementing applications on macOS.
5 replies
@nbren12 I think you can do that at the OS level.
But it’s not something Amethyst knows how to do.
Hello all, I'm interested in working on contributing to Amethyst and saw there was a setup script
/bin/setup.sh can you install app in via brew but still test the app build from source? Or as a contributor you should only use the one build from source? wondering how the process works...
The only issue is that the accessibility permissions can be quite finicky.
If you give the production Amethyst accessibility permissions then the development Amethyst run from Xcode will not have permissions, and vice versa.
And switching them over can be a pain.
So I would say stick with the dev version if you can, but otherwise the way I usually switch them is by removing Amethyst from the Accessibility access list entirely and then letting Amethyst prompt for permissions again.
Hi There! I'm new to Amethyst and to Mac... First I want to thank for the awesome work! It's great to have an option for a Tiling Window Manager... I've been using Linux for the past 12 years and over the last 6 I've been an i3 user. So when I switched to MacOS I really felt the loss of my productivity. Now with Amethyst I saw a light at the end of the tunnel.
I don't really getting the whole "space" concept here on Amethyst...
I'm using a MacBookPro with an external monitor. My external monitor is my main screen and the laptop display is my secondary screen. I know I can throw windows to space 1, or 2, or 3... but I don't know how to switch to that space... I'm probably misunderstanding the concept.
Spaces are a macOS concept. https://support.apple.com/guide/mac-help/work-in-multiple-spaces-mh14112/mac