4db0cd6443
An idea to remember to add keymodes patch files
2020-06-02 10:18:17 +02:00
af96d4c358
Adding keymodes patch
2020-05-31 15:14:29 +02:00
e7ea06a0c2
status2d: Minor protection against crashes due to invalid x and y values
2020-05-31 15:14:07 +02:00
7b2c30b371
Adding color emoji patch
2020-05-29 20:43:55 +02:00
643ea4d84f
Awesomebar: patch to prevent visual glitches from uneven tabs count
2020-05-28 10:50:33 +02:00
2c9ff7453a
dwmblocks and status2d compatibility fix for barpadding patch
2020-05-28 10:31:10 +02:00
66a32a0e48
fancybar: renaming tw variable to ftw due to clash with upstream sw --> tw variable rename
2020-05-28 10:26:01 +02:00
8236f1940b
dwmblocks and status2d buttonpress adjustments for awesomebar and statuspadding
2020-05-28 10:15:15 +02:00
2e30bddc16
Fixing status2d and statuscmd / dwmblocks compatibility issues.
...
Text width calculations when using status2d strings resulted in
statuscmd button placement calculations to be way off. Fixed by
introducing a separate function status2dtextlength to get an
approximate correct text width.
2020-05-27 21:04:22 +02:00
1bf50728a7
Awesomebar: dwm crashes on bar click with 0 clients
...
Clicking on the bar before any clients have been started results
in dwm crashing. This fix addresses that.
2020-05-27 14:10:51 +02:00
e79aec52c2
Adding status2d patch
2020-05-26 20:53:53 +02:00
fc8434abd1
Adding moveplace patch
2020-05-21 19:58:11 +02:00
2cb3e697e4
Adding moveresize patch as per #25
2020-05-21 18:55:47 +02:00
df118dc046
Switchtag patch, lose switchtag feature for client if the client is moved to another tag
2020-05-20 16:43:09 +02:00
5e281dcd44
Adding (temporary?) EWMH_WINDOWS_FLOAT_PATCH
2020-05-20 15:25:07 +02:00
57ef22eaba
[dwm][patch] setborderpx reset floating windows to previous size
2020-05-20 15:11:33 +02:00
29a06f83a0
[dwm][patch] setborderpx minor code style changes
2020-05-13 13:25:06 +02:00
ae5c96c217
Adding link to fix transparent borders diff
2020-05-13 13:24:45 +02:00
5cfaf8357b
[dwm][setborderpx] allow borderpixel changes in floating layout and for floating clients
2020-05-13 13:17:12 +02:00
1c6412802e
Getting rid of practically unused nbottom variable
2020-05-13 09:41:44 +02:00
0b429b4994
Fibonacci updates
2020-05-10 17:11:05 +02:00
ac4c5081c5
Horizgrid pixel perfect updates
2020-05-10 17:09:41 +02:00
443795e3c9
Gridmode pixel perfect updates
2020-05-10 10:42:47 +02:00
174e3260d2
Gappless grid pixel perfect updates
2020-05-10 10:40:47 +02:00
1508d9f274
Fibonacci pixel perfect updates
2020-05-10 10:31:11 +02:00
c65315d52f
Improved fibonacci layout (pixel perfect)
2020-05-08 18:54:39 +02:00
f1bc4e8858
Moving vanitygaps patches to https://github.com/bakkeby/patches/ repository
2020-05-08 18:53:52 +02:00
511fda0088
Removing unnecessary variable when both statuscmd and dwmblocks is used
2020-05-07 21:44:17 +02:00
1a4b3632d1
Removing redundant lastbutton variable when both statuscmd and dwmblocks patches are enabled
2020-05-05 19:59:21 +02:00
a6c2fe5668
Adding shiftviewclients files
2020-05-05 19:54:02 +02:00
91291ceb9f
Removing redundant statuscmds logic when both statuscmd and dwmblocks patches are applied
2020-05-05 19:50:28 +02:00
75d5f1e0c5
Adding shiftview patch
2020-05-03 16:09:05 +02:00
657988fbbf
Added the no transparent borders patch
2020-05-03 10:09:26 +02:00
f028377c98
Adding dwmblocks patch
2020-05-02 14:58:23 +02:00
5c1e09688f
Adding reference to fakefullscreenclient patch
2020-05-01 17:06:28 +02:00
b837899f7a
Adding option to be able to reverse cycle through flextile-deluxe layouts
2020-05-01 16:45:25 +02:00
0a0222d929
Pertag flextile-deluxe needlessly tied to monitor rules patch
2020-05-01 14:14:38 +02:00
c56773c0a0
Missing variable for dragmfact without vanitygaps patch
2020-04-30 18:09:47 +02:00
69a9fe607a
Changes to make fibonacci layout arrangement pixel perfect
2020-04-28 16:56:51 +02:00
8aa7a8dafb
Changes to make gapplessgrid layout arrangement pixel perfect
2020-04-28 16:34:44 +02:00
f7bb7f4403
Updating patch links
2020-04-27 20:54:16 +02:00
5911a9b7d7
Upgrade of the tagmonfixfs patch, allows e.g. fullscreen YouTube videos to be moved to an adjacent screen
2020-04-27 20:45:24 +02:00
904cc5962f
No real reason for using Bool here, we use ints everywhere else
2020-04-26 16:46:10 +02:00
14b7edd911
Expanded monitor rules patch to include nmaster, showbar and topbar options.
2020-04-26 16:29:44 +02:00
5848460fff
Improved swallow and switchtag compatibility
2020-04-23 17:19:17 +02:00
7c4a0c347f
Adding if conditions before freeing res_class and res_name in applyrules
2020-04-23 13:16:13 +02:00
1bed3b0093
drawbar: Don't shadow sw global
...
This jarred me a bit while reading the code, since "sw" usually refers
to the global screen geometry, but in drawbar() only it refers to
text-related geometry. Renaming it makes it more obvious that these are
not related.
2020-04-23 08:07:29 +02:00
2d8d5a0931
getatomprop: Add forward declaration
...
No functional changes, but for every other function we have a forward
declaration here. getatomprop should be no exception.
2020-04-23 08:00:22 +02:00
a84f1b01d2
Adding fix for attachbottom patch
2020-04-22 20:04:09 +02:00
11b47dda99
setmfact: Unify bounds for compile-time and runtime mfact
...
There are two places that mfact can be set:
- In the mfact global, which is defined at compile time and passed
into m->mfact during monitor setup. No bounds checks are performed,
but the comment alongside it says that valid values are [0.05..0.95]:
static const float mfact = 0.55; /* factor of master area size [0.05..0.95] */
- By setmfact, which adjusts m->mfact at runtime. It also does some
minimum and maximum bounds checks, allowing [0.1..0.9]. Values outside
of that range are ignored, and mfact is not adjusted.
These different thresholds mean that one cannot setmfact 0.95 or 0.05,
despite the comment above that lists the legal range for mfact.
Clarify this by enforcing the same bounds in setmfact at runtime as
those listed for mfact at compile time.
2020-04-20 18:40:25 +02:00
