Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 11:18
    Jonn3y opened #919
  • 10:32
    mkniewallner commented #765
  • Dec 11 15:00
    marco-silva0000 commented #911
  • Dec 09 02:12
    alextenczar opened #918
  • Dec 07 03:50

    ianyh on duplicate-floating

    (compare)

  • Dec 07 03:49

    ianyh on development

    Reset floating when displaying … (compare)

  • Dec 07 03:49
    ianyh closed #917
  • Dec 07 03:49
    ianyh closed #912
  • Dec 07 03:38
    ianyh opened #917
  • Dec 07 03:38

    ianyh on duplicate-floating

    Reset floating when displaying … (compare)

  • Dec 07 03:36

    ianyh on duplicate-floating

    Reset floating when displaying … (compare)

  • Dec 07 03:34

    ianyh on duplicate-floating

    Reset floating when displaying … (compare)

  • Dec 07 03:14

    ianyh on xcode-update-in-setup-script

    (compare)

  • Dec 07 03:14

    ianyh on development

    Set `OUR_XCODE` correctly for X… (compare)

  • Dec 07 03:14
    ianyh closed #916
  • Dec 07 03:04
    ianyh opened #916
  • Dec 07 03:03

    ianyh on xcode-update-in-setup-script

    Set `OUR_XCODE` correctly for X… (compare)

  • Dec 04 11:04
    egel commented #765
  • Dec 04 11:03
    egel commented #765
  • Dec 04 11:03
    egel commented #765
Ian
@ianfixes
@ianyh what do you think about using #127 to help with this? It might be cool to have a feature (even just for debugging) that draws a border around each window Amethyst "sees". They could be color-coded to indicate which windows are un-managed due to user settings (vs being framed). This would help e.g. to see whether a floating window was being affected by settings vs not being presented as a "window" by the OS.
Ian
@ianfixes
@NathanRightnour it looks like the windows in question are some form of "tool window" (note the shorter-than-usual title bar), so it's possible that the OS doesn't have control over them in the way that you'd expect. In some ways, that's a good thing: some types of tool windows simply disappear when their "parent" window loses focus, and that would make for some very jarring rearrangements of windows as you switch back and forth between apps. That doesn't mean we can't improve things (see my previous comment), but it might not be possible to directly address the problem you have.
NathanRightnour
@NathanRightnour
Okay, thanks for checking! If I can do any kind of testing I'm happy to help.
Slus
@Slus
Hey! Is it possible to have a "Quarter" layout?
Ian
@ianfixes
what would that look like?
Slus
@Slus
4 evenly split windows
2 on top
2 at the bottom
Ian
@ianfixes
try the tall layout, and increase the main pane count by 1
Slus
@Slus
omg I love you
What exactly does main pane count do
Btw. Insane work on this app
Ian
@ianfixes
As you noticed, there are a variety of different layouts. Most (but not all) involve some concept of a "main" window. Floating layout and BSP don't really have main windows, for example.
But for the rest of the layouts, the windows are all scaled relative to one "main" pane. For the Tall layout, that pane is vertical and resizes horizontally. For Wide, it's horizontal and resizes vertically.
Minimum "main" pane count is one. But if you increase the count, you subdivide that space.
You can make some interesting spaces adjusting that single parameter
Slus
@Slus
That's awesome. Thank you so much
Ian Ynda-Hummel
@ianyh
@NathanRightnour it looks like those might be panels rather than windows. Amethyst is explicitly narrowed to windows. It's not impossible to handle panels, but it causes a lot of unexpected behaviors if you do tile them.
@ianfixes #127 could be interesting for debugging, but it's possible what you actually want is a separate debugging mode that layers debug information over all windows.
Ian
@ianfixes
For #127 I wasn't thinking so much of debugging as for helping folks see whether things are windows or panels. (Case in point, NathanRightnour's issue). Like, maybe the popup for "identify" would also point out which window is which. I dunno, should I open an issue to track that idea?
Arnold
@arnoldsandoval
Howdy! I sit possible to have gaps in Amethyst?
Ian
@ianfixes
Yes, under settings there are both "window margins" and "screen padding". or do you mean just empty positions in the layout itself?
Jeff Windsor
@jeffwindsor
Just to properly communicate it, I put up some PRs for documentation updates around hotkeys.
ianyh/Amethyst#796
ianyh/ianyh.github.io#8
Are there any rules on picking up tickets on the twillo board?
Michael Drogalis
@MichaelDrogalis
Hey there. I just downloaded Amethyst for OS X 10.13.6. I enabled it through the Accessibility settings, but whenever I run the hot keys to change layouts, I see it echo the layout its switching to in the middle of my screen, but no windows are moved. Can anyone think of something dumb that I'm doing?
Michael Drogalis
@MichaelDrogalis
Huh, looks like I just had to restart it. Thanks for this cool project!
Zach Dwiel
@zach-nervana
amethyst has recently stopped reliably working for me. It seems as if amethyst starts moving a window in the right direction and adjusting the dimensions of the window, but then gives up partway through, leaving the window in a weird state
this happens for all kinds of events, moving windows between screens, resizing for new windows, rearranging windows on the same screen, etc
any ideas?
i can usually get the window to settle in the right spot by switching focus back and forth between windows, each time amethyst moves the window a little closer to where it should be
High Sierra 10.13.6
4 monitors: 1x retina display, 2x 2560x1440 and 1x 4k display
Zach Dwiel
@zach-nervana
this used to happen less often, but now it happens almost every time
Zach Dwiel
@zach-nervana
i've reproduce the problem in another window manager
Ian Ynda-Hummel
@ianyh
That's a fair bit of strain on graphics. Maybe it's delaying the accessibility calls enough that they encounter errors. I've seen that happen on occasion.
But it's been fairly rare.
I rarely have that many monitors.
Zach Dwiel
@zach-nervana
that appears to be the problem in the other application as well
he would timeout after 100 milliseconds, which wasn't enough
Ian Ynda-Hummel
@ianyh
It's an interesting problem.
Not sure how to approach it.
Ian
@ianfixes
If Amethyst puts up its own window, we could probably measure that delay (at least for resizing) right?
Ian Ynda-Hummel
@ianyh
I don't think so. I would expect the effect to be wildly varied.
It's also possible that the total number of windows impacts it. If you have 20 windows visible and they all receive accessibility calls at the same time would some of them be more likely to time out than if you had 10 windows?
Zach Dwiel
@zach-nervana
one thing talon is doing is checking on where the window is after a timeout and retrying if it isn't where it should be
still not perfect though
Ian Ynda-Hummel
@ianyh
We do something similar for registering observers on applications, but we do an exponential backoff.
It’s a lot of delay for an already slow operation, though.
Could you link me to the code you’re talking about?
Zach Dwiel
@zach-nervana
gotcha, that makes sense