Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

patch: Vertical stacking #19

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

antonholscher
Copy link

@antonholscher antonholscher commented Nov 13, 2020

Makes notifications vertically stack (downwards/upwards depending on corner config being top/bottom).
Uses System V shared memory to keep track of y-offset between processes.
Here's a demo

Download

https://patch-diff.githubusercontent.com/raw/dudik/herbe/pull/19.diff

@antonholscher antonholscher changed the title patch: vertical stacking patch: Vertical stacking Nov 13, 2020
@dudik dudik added the patch This pull request is a patch label Nov 14, 2020
TAAPArthur added a commit to TAAPArthur/herbe that referenced this pull request Jan 3, 2021
Makes notifications vertically stack (downwards/upwards depending on
corner config being top/bottom).
Uses System V shared memory to keep track of y-offset between processes.

Vertical stacking taken from patch dudik#19
TAAPArthur added a commit to TAAPArthur/herbe that referenced this pull request Jan 16, 2021
Makes notifications vertically stack (downwards/upwards depending on
corner config being top/bottom).
Uses System V shared memory to keep track of y-offset between processes.

Vertical stacking taken from patch dudik#19
ttr3dp added a commit to ttr3dp/herbe that referenced this pull request Feb 4, 2021
TAAPArthur added a commit to TAAPArthur/herbe that referenced this pull request Apr 11, 2021
Makes notifications vertically stack (downwards/upwards depending on
corner config being top/bottom).
Uses System V shared memory to keep track of y-offset between processes.

Vertical stacking taken from patch dudik#19
@leahneukirchen
Copy link

This approach works badly on a multi-user system of course... perhaps X resources could be used to figure out position?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch This pull request is a patch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants