I’m trying to use “Show Window Switcher for All Open Apps”, and I’m noticing unexpected behaviors such as the following: Hitting right arrow key on highlighted window when the window switcher menu is launched, will actually move the window to a different space.
I don’t see any description of how this workflow is supposed to work from within the app, and I cannot find any documentation about it from the Documentation section of this section. There’s also no formal documentation of how this workflow is supposed to behave on this forum (except to see that it was proposed and bugs were fixed). If I’m missing an obvious “help” resource, please let me know.
The set of instructions shown in Popover seems incomplete, because “Left Arrow” seems to send the selected window to another space, and that’s not shown in the Popover Shortcuts list. The shortcut list does show a “Left Arrow” next to Command-D, but I don’t think that means “send to left space”.
Furthermore, I don’t see any documentation which says that the Window Switcher will NOT auto hide when there’s another BetterTouch window. This bit of detail is found only in a forum comment by Andreas, and it’s not in any documentation, even though it’s a pretty important UI behavior to note.
BetterTouchTool docs always try to cover the basic concepts, they will/can never be complete or cover all edge cases. Lots of actions don’t have documentation at all
In this case, I think we have a different view on what’s “edge case”. Maybe you’re interpreting these “edge cases” as “minor unexpected behaviors that are inconvenient”, but I interpret them as “unexpected behaviors that prevent user from adopting useful feature”.
I think it’s great that BetterTouch is developing SO fast, and it’s continuously getting updated with new features. The downside is that I sometimes have a hard time trying out the new features, because it’s not clear how I should use them. In this example with the “Show Window Switcher” feature, I couldn’t figure out how to make the switcher window auto-hide when not in focus, and I thought there’s no way to do so, which would be a deal breaker, and it would have stopped me from using the feature. Furthermore, I didn’t expect highlighted windows to move across spaces when I hit the arrow keys. These unexpected behaviors are confusing when users are trying understand how a new feature could be useful for them.
I take the point that documentation is HARD and can feel like a waste of time (because we’re not shipping new features or fixing bugs), but I do think this particular feature is valuable enough that more of its behaviors should be documented (some of it is already documented in the popup menu as Volker showed).
Much thanks for ALL the continuous development and new feature updates. I’m always amazed with all the progress.
Good news is that I have a general improvement incoming for the „hide on deactivate option“ requiring non-BTT windows (this was to improve performance but I think I now have a better way of achieving the same).
This affects many things in BTT, which is why I need to test carefully, but ai think it will come in 1-2 weeks
