You are not logged in.
-1 here. I use root-tail to pipe logs from /var, & an empty desktop is very much needed...
or you can use the showhide branch and hide all windows/show the root window with a shortcut. i use it because of conky, which uses all space it can get (on a rather small netbook). i don't know why people bother with those small panels anymore...
Offline
alright, pushed a fix for this
transient windows are always on top
unless obscured by a floating window
Popups are ok now, but floating windows still go to background.
Offline
c00kiemon5ter wrote:alright, pushed a fix for this
transient windows are always on top
unless obscured by a floating windowPopups are ok now, but floating windows still go to background.
shouldn't they?
I can fix it once I'm back home, in a couple of hours
not sure what the behaviour should be.
I'll push the new behaviour and you (the users) tell me if you prefer it that way
.:[ git me! ] :.
Offline
It doesn't really matter to me, since I rarely use floating mode, but I think he's right? At least, that's the way dwm does it and it is useful in some situations.
edit:but then again, I guess there are times when you would want it to go to the background? I guess you can't have it both ways, or can you? Anyway, whatever you decide c00kie is good for me personally.
Last edited by stlarch (2012-02-08 16:31:00)
Offline
It doesn't really matter to me, since I rarely use floating mode, but I think he's right? At least, that's the way dwm does it and it is useful in some situations.
Like stlarch said, it's default on dwm. With current behaviour, floating, at least for me, is unusable.
It's impossible to have floating window visible while doing work in another tiled window.
eg. I open gcolor2 (color picker, defined as floating), select a color, but soon as mouse leaves its window
so I can paste color code somewhere else, gcolor2 vanishes to background.
edit:but then again, I guess there are times when you would want it to go to the background? I guess you can't have it both ways, or can you? Anyway, whatever you decide c00kie is good for me personally.
I didn't look at this that way, but if I you don't want to see certain window, it makes more sense to just send it to another workspace.
Offline
It doesn't really matter to me, since I rarely use floating mode,
me too, so I don't mind either
I didn't look at this that way, but if I you don't want to see certain window, it makes more sense to just send it to another workspace.
yeah, that makes sense
with the parsing output to panel you can even have a
hidden desktop - no name , no window count nothing shown
and send windows there
edit: forgot to say I pushed it
Last edited by c00kiemon5ter (2012-02-08 17:40:03)
.:[ git me! ] :.
Offline
It works perfectly now!
Float like dwm, sting like a monster
Offline
How to configure shortcuts to start app with defined parameter? This is the relevant code:
/** my apps **/
static const char *web_browser[] = { "app_launcher.sh", "--web-browser", NULL };
static const char *text_editor[] = { "app_launcher.sh", "--ide", NULL };
...
I just created that script to enable me to dynamically change GUI apps which can be launched in monsterwm. The problem in compiler is this:
...
In file included from monsterwm.c:160:0:
config.h:62:79: error: called object ‘"--file-manager"’ is not a function
...
Any help? I just need to use "app_launcher.sh --parameter" to launch everything i need
[Edit]
It sems that i lost one comma when i defined those commands :-/
It is working now.
Last edited by kuraku (2012-02-09 02:26:18)
Offline
Using monsterwm and loving it But I have a few questions:
-Would it be a lot different from dwm to make a patch to increase the amount of master clients? - Also, is there any reason why some fancy panels, like pypanel or bmpanel, doesn't work with monsterwm? nevermind, bmpanel2 works fine, pypanel print an error.
Thanks for the good work
Last edited by Poplus (2012-02-10 18:59:15)
Offline
or you can use the showhide branch and hide all windows/show the root window with a shortcut. i use it because of conky, which uses all space it can get (on a rather small netbook). i don't know why people bother with those small panels anymore...
Hi rich, nice to meet you. Thanks, appreciate it, I'll give it a spin.
Offline
Would it be a lot different from dwm to make a patch to increase the amount of master clients?
this can be done, if anyone is willing to make a patch.
I may try this, but I've been a bit busy lately with exams.
btw, grid layout with 5 clients will give you 2 "master" windows and 3 in "stack"
which kinda emulates what you want.
I guess having more that 3 stack windows or two master ones isn't much usable,
so until someone or I makes a patch, you can try that
thanks for trying it out
Last edited by c00kiemon5ter (2012-02-12 01:04:07)
.:[ git me! ] :.
Offline
hum... what about making resize stack function to work with grid layout too? I've been looking at some dminiwm screens and just noticed that using grid layout with + resizing, there would be no need to add more masters and it would still be possible to create some usefull custom layouts, like this http://ompldr.org/vYzlpdg
Of course that would be only good if it doesn't take a lot of sloc and work
Offline
Oh thanks no need to rush tho
Offline
Hi,
I've found a new bug: when a program spawns a floating window on top of another floating window, monsterwm flickers and becomes unresponsive during a few seconds. (noticed this using gparted and exfalso).
I'm using the core branch
*edit: The quit function it's not working also.
Last edited by whooper (2012-02-20 01:20:18)
Offline
I've found a new bug: when a program spawns a floating window on top of another floating window, monsterwm flickers
monsterwm raises every floating window it finds. If you have two or more on top of each other they could be ordered in such a way that the one on the back is raised, and then the one that was on top is raised after, which would cause a flicker there.
I don't think I want to "fix" that. It's just a minor flicker, and choosing a floating wm but having many floating windows sound like not a good choice (not directed to whooper, I'm talking in general).
and becomes unresponsive during a few seconds. (noticed this using gparted and exfalso).
I do not think that is related to monsterwm. If you can tell what you were doing when that happened, I might be able to reproduce it, but there no reason for something like that to happen. Most usual reason for such effects, is great IO work (ie lots of compiling, or use of converters (ie for images, pdfs etc), or compressing etc)
*edit: The quit function it's not working also.
The quit in core was binded to "Mod1-Ctrl-r" by default (dah, got there by mistake)
I changed it to "Mod1-Ctrl-q" as one would expect. I tested and works as expected.
Also note that core doesn't return a value on exit, as master does. So anything like:
while true; do monsterwm || break; done
will _not_ work for the core branch (as it never exits with !=0, except on error).
thanks
Last edited by c00kiemon5ter (2012-02-20 12:34:06)
.:[ git me! ] :.
Offline
Offline
Monsterwm becomes unresponsive when I open gparted, go to help -> about -> credits and after a while goes back to normal. This happens with exfalso too.
http://i.imgur.com/ulrwVs.png
I'm not able to reproduce this on either monsterwm_xcb or monsterwm.
Offline
hmmm, I cannot reproduce this. Both gparted(help/credits and other menus) and exfalso work as expected.
I tried different combinations (many/non windows) with all the layouts, but all seem fine.
Can anyone else reproduce/try this ?
edit: ah, thanks for the quick reply cloudef
see if you get any error from gtk, by running gparted from a terminal, although I think gparted hides all output..
Last edited by c00kiemon5ter (2012-02-22 13:33:42)
.:[ git me! ] :.
Offline
@c00kiemon5ter
Monocleborders branch: working fine with exfalso on debian system (sid here).
Offline
Ran gparted from a terminal but it doesnt output any error. As other people cant reproduce this bug I would just forget about this minor issue, it doesn't affect the usability for me.
Thank you for your attention.
Offline
If I were you, I'd try changing the gtk-theme, or play with the gtk settings in general.
Probably just mv every .gtk* dir under home to a backup place and try with default settings.
If that works you'll know it's gtk causing that.
If not, uhm, I cant thing of something now, but will say if somethings comes to mind.
.:[ git me! ] :.
Offline
I set follow_mouse false and the bug doesn't happen anymore. Don't know if it has to do with my mouse or with monsterwm itself.
Last edited by whooper (2012-02-23 23:36:31)
Offline
ah, yes, I see what you mean now. It's not that contents are not drawn, it's just that the windows keep raising one on top of the other. I've encountered that too with FOLLOW_MOUSE and the warp_cursor patch.
I pushed quick fix for now. It should be working. Test with exfalso and tell me.
Last edited by c00kiemon5ter (2012-02-24 02:39:28)
.:[ git me! ] :.
Offline