add commands for window tiling#281
Conversation
There was a problem hiding this comment.
What if rather than hard coding left / right we used:
f32 as a "percentage" of the display and make it configurable in the config?
This way theres a few default arrangements, and its customisable
There was a problem hiding this comment.
I'm not sure that a single f32 can get you there (or maybe I'm misunderstanding) but I do think a 4-tuple of (x_start, x_end, y_start, y_end) could. I'm not interested in implementing the configurable part of this but have a draft of changing to the 4-tuple implementation I can push if you're interested.
|
|
||
| // TileWindow is intercepted in the RunFunction handler which has | ||
| // access to the frontmost PID; nothing to do here. | ||
| Function::TileWindow(_) => {} |
There was a problem hiding this comment.
Mark it with unreachable!() please.
|
I think for now we can add this becuase tiling is something many people have requested. But in the future it is worth switching to using a more programatic method. |
2 participants
Another raycast feature I use a lot. This doesn't technically implement every single tiling option from raycast but handles my commonly used ones and the ones I expect get the most use in general. Regardless, it should be easy to add additional tiling options in a future change if desired.