[dwm] feature freeze, please test
Hi there,
I consider the current states of dwm hg tip and dmenu hg tip as
finished for the next release.
I contrast to my previous decision to postpone several patches
which have been supplied during the last weeks for after
dwm-5.0, I decided to integrate them now, just before dwm-5.0,
in order to minimize changes to config.h after the 5.0 release.
Thus, the current hg tip contains the following major changes:
1. The argument type for key- and button-handlers is a union
called Arg, which looks as follows:
typedef union {
int i;
uint ui;
float f;
void *v;
} Arg;
This enforces type-safety at compile time, but also provides the
flexibility to supply auxilliary arguments using the v-field.
2. The previous color/font definitions are const char[]
declarations now. Note, that in dmenu's config.h they are const
char * however, because there the pointer might change if
colors/fonts are overridden by program arguments.
3. The syntax to spawn has changed, if you prefer the old
behavior, config.def.h contains a SHCMD macro to supply the old
behavior.
4. A new Button type has been introduced which encapsulates the
mouse handling in dwm in a very similiar fashing as the Key type
does. See config.def.h for details. Thanks to yiyus for his
contribution!
5. dwm-5.0 support Xinerama in a very basic way, it basically
uses the Xinerama screen indexed by xidx only, however the
floating layout allows to use the whole real estate provided by
the X display -- so in multihead setups dwm can be used in a
floating fashion, whereas the biggest screen should be used for
the tiled layout.
6. The tags are addressed using bit-fields now, which has been
discussed earlier already. See the mailinglist archives for
details.
7. The bar is toggleable again.
8. There is a new maximize meta-layout which can be
enabled/disabled using Mod1-m.
In contrast to previous releases of dwm and dmenu, the 5.0 and
3.7 series will be major simplifications. I got rid of the
DEFGEOM and pseudo-multihead-layout overengineering from dwm-4.8
and dwm-4.9, so 5.0 feels more like 4.7, but provides
considerably major improvements.
Please report any bugs. If there aren't any major bugs, I will
release both, dmenu and dwm around mid of next week.
Kind regards,
--
Anselm R. Garbe http://www.suckless.org/ GPG key: 0D73F361
Re: [dwm] feature freeze, please test
About the mouse warping issue we have discussed in #dwm, forget it, I
can get the desired behavior with a little config.h modifications.
I add:
void
warptosel(const Arg *arg) {
if(sel)
XWarpPointer(dpy, None, sel-win, 0, 0, 0, 0, 0, 0);
}
and then, in buttons definitions:
{ ClkWinTitle, 0, Button1,warptosel,
{0} },
{ ClkWinTitle, 0, Button1,movemouse,
{0} },
{ ClkWinTitle, 0, Button3,resizemouse,
{0} },
{ ClkWinTitle, 0, Button4,focusstack,
{.i = -1 } },
{ ClkWinTitle, 0, Button5,focusstack,
{.i = +1 } },
and that's all. So I'd suggest to not touch dwm.c any more, and this
message will stay here as a reference for other people if they are
interested.
greets,
--
- yiyus || JGL .
Re: [dwm] feature freeze, please test
On Sat, Jun 14, 2008 at 03:12:38PM +0200, yy wrote:
2008/6/14 yy [EMAIL PROTECTED]:
About the mouse warping issue we have discussed in #dwm, forget it, I
can get the desired behavior with a little config.h modifications.
I add:
void
warptosel(const Arg *arg) {
if(sel)
XWarpPointer(dpy, None, sel-win, 0, 0, 0, 0, 0, 0);
}
and then, in buttons definitions:
{ ClkWinTitle, 0, Button1,warptosel,
{0} },
{ ClkWinTitle, 0, Button1,movemouse,
{0} },
{ ClkWinTitle, 0, Button3,resizemouse,
{0} },
{ ClkWinTitle, 0, Button4,focusstack,
{.i = -1 } },
{ ClkWinTitle, 0, Button5,focusstack,
{.i = +1 } },
and that's all. So I'd suggest to not touch dwm.c any more, and this
message will stay here as a reference for other people if they are
interested.
I have reverted the ButtonPressMask in the root win and added
else
click = ClkWinTitle;
after the last else if in buttonpress, if you add this to the config.h
modifications in my previous message managing windows in the floating
layout is really comfortable, just click in the root window. I think
further thinking is needed before getting rid of root click events
(though this solution is not definitive, it still has the problem of
window borders treated like the root win...). What do other people
think about this?
The only thing I dislike is the reuse of ClkWinTitle for the
root window -- if we want to do that, we need to re-introduce
ClkRootWin.
Also, is the warp really necessary or shouldn't the handling be
the same as in resizemouse?
Kind regards,
--
Anselm R. Garbe http://www.suckless.org/ GPG key: 0D73F361
Re: [dwm] feature freeze, please test
Anselm, I just tried out the dwm current hg tip, with the recently posted kbmvresize.patch and prevnexttag.diff patches applied. I had to apply the kbmvresize patch by hand but that was simple enough. All appears to be working well on my box. The more I get to know dwm, the better I like it. Since the early 1.xx kernel days I've been primarily a Linux console user. I usually only switch to X windows for internet browsing, graphic/movie file viewing, etc. Since discovering dwm I've been using X more and the console less. I'm typing this e-mail via Alpine running in an urxvt terminal window. Many thanks for such a wonderful window manager Kevin http://www.RawFedDogs.net http://www.WacoAgilityGroup.org Bruceville, TX Si hoc legere scis nimium eruditionis habes. Longum iter est per praecepta, breve et efficax per exempla!!!
