Re: [dev] [wmii] Mouse problems
Hi again, unfortunately, my solution worked only a couple of days. Meanwhile I have the same problems again and the search for solutions continues. So if someone has Ideas about the source of my mouse issues I would be glad to hear about them. But, I still think wmii and rumai are not the cause. Cheers, Tom
Re: [dev] [wmii] Mouse problems
On Fri, Jul 16, 2010 at 11:03:38AM +0200, Tom Kazimiers wrote: unfortunately, my solution worked only a couple of days. Meanwhile I have the same problems again and the search for solutions continues. So if someone has Ideas about the source of my mouse issues I would be glad to hear about them. But, I still think wmii and rumai are not the cause. There's a good possibility you're using a version of Xorg that uses HAL for driver configuration. This is, to say the least, inideal. Unless you have some relish for editing dozens of inscrutable XML files. Arch has finally updated to 1.8 where things are moderately sane (by X11 standards, anyway) again. -- Kris Maglione When a religion is good, I conceive it will support itself; and when it does not support itself, and God does not take care to support it so that its professors are obliged to call for help of the civil power, 'tis a sign, I apprehend, of its being a bad one. --Benjamin Franklin
[dev] [wmii] floating clients in default and stack mode
I have a question about wmii, floating clients and the "default" and "stack" modes in this situation. Let's suppose I create a new tag, then switch to the floating layer with Mod-shift-space and start 4 new clients. By default the "default" mode is applied, so I can see all the clients. If I press Mod-s, I only see the focused client and the other 3 clients remain are collapsed. If I switch to the default mode again with Mod-d nothing changes visibly. That is, I can still see 1 client and 3 collapsed clients. So I have to un-collapse them manually using the mouse. I remember that some months ago switching from the "stack" to the "default" mode in the floating layer used to collapse/uncollapse all the clients (except for the focused one). So I was wondering if this new behavior is intentional or not. Thanks, Juan Pablo
Re: [dev] [wmii] floating clients in default and stack mode
On Fri, Jul 16, 2010 at 12:34:50PM +0200, Juan Pablo Aroztegi wrote: I have a question about wmii, floating clients and the "default" and "stack" modes in this situation. Let's suppose I create a new tag, then switch to the floating layer with Mod-shift-space and start 4 new clients. By default the "default" mode is applied, so I can see all the clients. If I press Mod-s, I only see the focused client and the other 3 clients remain are collapsed. If I switch to the default mode again with Mod-d nothing changes visibly. That is, I can still see 1 client and 3 collapsed clients. So I have to un-collapse them manually using the mouse. I remember that some months ago switching from the "stack" to the "default" mode in the floating layer used to collapse/uncollapse all the clients (except for the focused one). So I was wondering if this new behavior is intentional or not. Yes, in the hg tree this is the expected behavior, but not the correct one. The code that deals with collapsed clients is currently incomplete. I have a WIP on my patch queue, but it's about a day's work from completion and requires more concentration than I've been able to invest recently. -- Kris Maglione Increasingly, people seem to misinterpret complexity as sophistication, which is baffling---the incomprehensible should cause suspicion rather than admiration. Possibly this trend results from a mistaken belief that using a somewhat mysterious device confers an aura of power on the user. --Niklaus Wirth
Re: [dev] [wmii] floating clients in default and stack mode
> Yes, in the hg tree this is the expected behavior, but not the correct one. > The code that deals with collapsed clients is currently incomplete. I have a > WIP on my patch queue, but it's about a day's work from completion and > requires more concentration than I've been able to invest recently. OK clear, it's great to know it's planned. Thank you for the information. Juan Pablo
[dev] [ii] patch - simplify add_channel() a bit
Hello,
Another small ii patch. Originally add_channel does
if(!channels) channels = c;
else {
c->next = channels;
channels = c;
}
but the check to see if channels is NULL is not needed. This patch
changes it to just
c->next = channels;
channels = c;
If channels is NULL, c will be the last element and c->next will be NULL anyway.
-emg
diff -r d93eaacde742 ii.c
--- a/ii.c Fri Jun 25 10:55:05 2010 +0200
+++ b/ii.c Fri Jul 16 14:35:51 2010 -0700
@@ -123,13 +123,10 @@
perror("ii: cannot allocate memory");
exit(EXIT_FAILURE);
}
- if(!channels) channels = c;
- else {
- c->next = channels;
- channels = c;
- }
c->fd = fd;
c->name = strdup(name);
+ c->next = channels;
+ channels = c;
}
static void rm_channel(Channel *c) {
