Musca (Tiling Window Manager)

Procyon · 2009-04-20 00:29:52

try window_layer normal, if you use pad 0 0 0 x it will be visible.

Inxsible · 2009-04-20 00:39:28

Procyon wrote:

try window_layer normal, if you use pad 0 0 0 x it will be visible.

Thanks procyon, but it doesn't change the bahavior. it shows correctly initially, but when I manually enter a pad 0 0 0 0, it is still visible. I even tried restarting the tray and musca both.
Beats me !

Inxsible · 2009-04-20 00:42:13

Also in version 18, I see that when I hit Mod4+g, it lists all my groups. But the highlighting is always on 0-default. Sean, can you change this so that it highlights the group that is currently in focus?

AFAIK, that's how it was in earlier versions. I am not sure why you changed it

aerosuidae · 2009-04-20 01:14:46

@Inxsible: try in .stalonetrayrc:

window_layer normal

When you use window_layer top, stalonetray sets EWMH _NET_WM_STATE_ABOVE to force the window to stay on top of everything else. The only reason this worked on older versions of Musca was because older versions did not know about _NET_WM_STATE_ABOVE

Edit: ah, got beat to it

Try setting this, *and* cycling the frame or switching the group.

Last edited by aerosuidae (2009-04-20 01:16:42)

aerosuidae · 2009-04-20 01:23:24

Inxsible wrote:

Also in version 18, I see that when I hit Mod4+g, it lists all my groups. But the highlighting is always on 0-default. Sean, can you change this so that it highlights the group that is currently in focus? AFAIK, that's how it was in earlier versions. I am not sure why you changed it

Now here we have a conundrum. Some folks were saying they disliked the groups getting out of order in that list, and unfortunately dmenu automatically highlights the first entry. The current behavior is also to allow the group number to be used for switching, where previously we have no group numbers at all. So two options:

1. We have some mode to toggle dmenu lists displaying in number order or in focus order, or

2. You could bind "show groups" to some key when you want to see the active group (marked with an asterisk).

Any opinions...

Inxsible · 2009-04-20 02:45:06

aerosuidae wrote:

Inxsible wrote:
Also in version 18, I see that when I hit Mod4+g, it lists all my groups. But the highlighting is always on 0-default. Sean, can you change this so that it highlights the group that is currently in focus? AFAIK, that's how it was in earlier versions. I am not sure why you changed it
Now here we have a conundrum. Some folks were saying they disliked the groups getting out of order in that list, and unfortunately dmenu automatically highlights the first entry. The current behavior is also to allow the group number to be used for switching, where previously we have no group numbers at all. So two options:
1. We have some mode to toggle dmenu lists displaying in number order or in focus order, or
2. You could bind "show groups" to some key when you want to see the active group (marked with an asterisk).
Any opinions...

In option 2, once it shows the groups -- can we move around with arrow keys and switch groups as well? If so, that would be great since I use a similar layout for my screen apps

Inxsible · 2009-04-20 02:47:35

aerosuidae wrote:

@Inxsible: try in .stalonetrayrc:
window_layer normal
When you use window_layer top, stalonetray sets EWMH _NET_WM_STATE_ABOVE to force the window to stay on top of everything else. The only reason this worked on older versions of Musca was because older versions did not know about _NET_WM_STATE_ABOVE
Edit: ah, got beat to it
Try setting this, *and* cycling the frame or switching the group.

Alright, having window_layer at normal and then cycling groups does help. Although, I am positive that it doesn't work unless I cycle frames/groups.

aerosuidae · 2009-04-20 06:31:32

@Inxsible: revision 177 of the dev tree https://code.launchpad.net/musca adds a Musca command called refresh, to force the current window to redraw and re-raise itself. Ie, to have your full screen movie hide stalonetray without needing to cycle windows or switch groups:

pad 0 0 0 0
refresh

(with window_layer normal).

The frame cycle or group switch you tired earlier was just to force a redraw. The reason this step is required in .18 is a result of reducing the screen flicker with needless window redrawing. Soon we will support _NET_WM_STATE_BELOW at which point running stalonetray with window_layer bottom will fix this.

EnvoyRising · 2009-04-20 12:38:29

Inxsible wrote:

Procyon wrote:
@ Inxsible: Can't you change the WM Hints of Stalonetray? I think the old way was worse because if you had dmenu open and click on firefox, dmenu disappears even though it is still grabbing keys. Some apps just need to be on top always and the current version respects that.
@ Envoy Rising: That is certainly more informative than config.h, but with the website documentation, musca -c 'show settings|etc|etc', and that the startfile is better built bottom up than top down, I don't know if it is really a good thing to put in the official package.
Hmmm. I never had the issue of dmenu locking up in musca....although I had had that happen to me a lot in wmii. I will try and change the WM Hints of stalonetray and see if it helps. The thing is, I want the tray to disappear only when I am watching a movie...At all other times, I want it staying at the bottom right corner, which is why I pad all my groups by 0 0 0 16.
I agree that building a musca_start file from bottom up is much better, because you can only add stuff that you want different from default. But a good thing would be to be able to change the location of the start file. I like all my config files to go under ~/.config/appName, rather than clutter the /home/$USER. I know we can change the location in config.h and re-compile...but I am just lazy to do it for every update

@ Procyon: I didn't know about the "-c settings" option. Thanks for the hint. Also, people are notorious for not looking at documentation, so I figured this might be useful for those who hadn't fully embraced the "Arch Way".
@ Inxsible: Isn't that what the "set startup" option is for? Just change that in your musca_start and you can avoid changing the config location in your config.h and recompiling.

Perhaps then as a simpler alternative it would be helpful to remind users via the post install script that they have to create their musca_start from scratch and to reference the online documentation or "musca -c settings" for available options?

Last edited by EnvoyRising (2009-04-20 12:43:15)

greenmanwitch · 2009-04-20 12:47:24

I got sick of Awesome today after using it for 2 months. It was good, but I hated the constant breaking with minor version bumps. This has to be the best wm I've tried so far, and it's so young! Incredible! Thanks to devs and the arch community.
The documentation is somewhat lacking, though. Everything's there but some examples and walkthroughs might be handy. It took me all day to get it set up right. I might lend a hand with that, actually.

Inxsible · 2009-04-20 15:05:43

greenmanwitch wrote:

I got sick of Awesome today after using it for 2 months. It was good, but I hated the constant breaking with minor version bumps. This has to be the best wm I've tried so far, and it's so young! Incredible! Thanks to devs and the arch community.
The documentation is somewhat lacking, though. Everything's there but some examples and walkthroughs might be handy. It took me all day to get it set up right. I might lend a hand with that, actually.

We have a wiki page just for that purpose. Sean's website has pretty much all the information. I too, had some trouble with the syntax of the musca_start file (if you read the entire 12 page thread )

So, in short, please update the wiki page as and when you find something that is not obvious. Thanks

Inxsible · 2009-04-20 15:06:41

aerosuidae wrote:

@Inxsible: revision 177 of the dev tree https://code.launchpad.net/musca adds a Musca command called refresh, to force the current window to redraw and re-raise itself. Ie, to have your full screen movie hide stalonetray without needing to cycle windows or switch groups:
pad 0 0 0 0
refresh
(with window_layer normal).
The frame cycle or group switch you tired earlier was just to force a redraw. The reason this step is required in .18 is a result of reducing the screen flicker with needless window redrawing. Soon we will support _NET_WM_STATE_BELOW at which point running stalonetray with window_layer bottom will fix this.

Thanks for the quick reply Sean. I will hook refresh to pad and I think that would do

Inxsible · 2009-04-20 15:08:20

EnvoyRising wrote:

@ Inxsible: Isn't that what the "set startup" option is for? Just change that in your musca_start and you can avoid changing the config location in your config.h and recompiling.
Perhaps then as a simpler alternative it would be helpful to remind users via the post install script that they have to create their musca_start from scratch and to reference the online documentation or "musca -c settings" for available options?

hmmm. Honestly, I haven't read up on the set startup option -- but if it doesn't find the musca_start file under /home/$USER -- then how is it going to read the "set startup" option in the file?

* need to read up on this*

greenmanwitch · 2009-04-20 15:09:56

Basically, my only problem with musca is watching movies. It's ridiculous that I have to:

turn off borders
set padding to 0 0 0 0
open gmplayer
set to stack mode
select fullscreen in gmplayer
set to tiling mode

I've got no idea how, but for usability's sake this needs to be fixed.

Inxsible · 2009-04-20 15:26:19

greenmanwitch wrote:

Basically, my only problem with musca is watching movies. It's ridiculous that I have to:
turn off borders
set padding to 0 0 0 0
open gmplayer
set to stack mode
select fullscreen in gmplayer
set to tiling mode
I've got no idea how, but for usability's sake this needs to be fixed.

The only thing that I do is turn off the borders and pad 0 0 0 0. I use vlc and it opens it in full screen since I am always in stack mode on a new group where I start a movie. Look into hook. you can hook certain commands with others so that you don't have to go about entering them all.

Procyon · 2009-04-20 15:32:34

About movie playing, what I do is that I already have one main catchall frame with no borders and I don't use padding, then when I open mplayer it already tries to fit the entire frame, and I just have to press `mod4+(o)nly`.

So there's no need for stack mode or fullscreen mode. I don't know about gmplayer though.

And don't forget to combine everything you need in a single keybinding. Also look at the example script I posted. You could use the same key to toggle going to single window mode and to multiple frame mode by just checking the dump file.

Inxsible · 2009-04-21 02:37:09

Procyon wrote:

About movie playing, what I do is that I already have one main catchall frame with no borders and I don't use padding, then when I open mplayer it already tries to fit the entire frame, and I just have to press `mod4+(o)nly`.
So there's no need for stack mode or fullscreen mode. I don't know about gmplayer though.
And don't forget to combine everything you need in a single keybinding. Also look at the example script I posted. You could use the same key to toggle going to single window mode and to multiple frame mode by just checking the dump file.

So Procyon, do you start this group(without borders) in musca_start? or do you create it manually? Can you show us your musca_start?

Procyon · 2009-04-21 10:29:15

It's the same, main group, with one frame that has no borders and is catchall.

I do use another group for unimportant applications like wine, but I hardly ever look at it. .musca_start:

set dmenu dmenu -i -l 7 -rs -ni -xs
set window_open_frame empty
set window_open_focus 1
set frame_display_hidden 1
set border_width 2
set border_focus red
set border_unfocus #285577

bind on Print screen (next)
bind on KP_Subtract command
bind off Mod4+x

screen 1
load .musca_dump_screen1

screen 0
border off
catchall on
exec musca_bpager bottomcycle
add wine
use default

I use the script I posted earlier that has bottomcycle, topcycle, toponly and bottomonly (with xbindkeys). I feel comfortable with it without using a window list or pager, which had been a problem in the past.

The bottom window will have a border, that's why bottomonly removes them and makes it catchall.

So when I start the movie and I'm in two frame mode, it will start in the top frame, and I press toponly. When I have to check firefox I press bottomcycle and the movie is still visible in the top (return with toponly). When it is in the OP/ED or something I press topcycle and the movie is in the smaller frame (return with bottomonly).

EDIT: and I have those in xbindkeys:
"musca_bpager uponly"
KP_Up
"musca_bpager cyclebottom"
KP_End
"musca_bpager cycletop"
KP_Home
"musca_bpager downonly"
KP_Down

Last edited by Procyon (2009-04-21 10:31:55)

EnvoyRising · 2009-04-21 13:44:53

Inxsible wrote:

EnvoyRising wrote:
@ Inxsible: Isn't that what the "set startup" option is for? Just change that in your musca_start and you can avoid changing the config location in your config.h and recompiling.
Perhaps then as a simpler alternative it would be helpful to remind users via the post install script that they have to create their musca_start from scratch and to reference the online documentation or "musca -c settings" for available options?
hmmm. Honestly, I haven't read up on the set startup option -- but if it doesn't find the musca_start file under /home/$USER -- then how is it going to read the "set startup" option in the file?
* need to read up on this*

Valid question, but as per the main page "startup" is in fact an option.

Last edited by EnvoyRising (2009-04-21 13:45:08)

Procyon · 2009-04-21 15:43:54

I noticed Firefox sometimes wants to be raised and then the focused border isn't updated.

hatten · 2009-04-21 15:59:37

Wow, I'm surprised there is so much to fiddle with, and that people actually does that! I haven't touched any musca start file or anything, the default stuff is amazing! Tremulous goes fullscreen automatically and i haven't encountered any problems at all! (that the manuals didn't cover)

Berticus · 2009-04-21 17:02:28

http://bbs.archlinux.org/viewtopic.php?id=69272

Just tried the latest version. Good news is I no longer have the issue with gtk2 apps. Bad news is I still have that focusing issue.

Procyon · 2009-04-21 17:08:35

@Berticus: How do you compile musca?

Berticus · 2009-04-21 17:38:02

I just use:

yaourt -S musca

I don't edit the PKGBUILD or anything.

greenmanwitch · 2009-04-22 02:09:47

How do I make a keybinding that toggles?

Like, if I press Mod4+p once, it will pad 0 0 18 0, 2nd time it will pad 0 0 0 0

Arch Linux

#276 2009-04-20 00:29:52

Re: Musca (Tiling Window Manager)

#277 2009-04-20 00:39:28

Re: Musca (Tiling Window Manager)

#278 2009-04-20 00:42:13

Re: Musca (Tiling Window Manager)

#279 2009-04-20 01:14:46

Re: Musca (Tiling Window Manager)

#280 2009-04-20 01:23:24

Re: Musca (Tiling Window Manager)

#281 2009-04-20 02:45:06

Re: Musca (Tiling Window Manager)

#282 2009-04-20 02:47:35

Re: Musca (Tiling Window Manager)

#283 2009-04-20 06:31:32

Re: Musca (Tiling Window Manager)

#284 2009-04-20 12:38:29

Re: Musca (Tiling Window Manager)

#285 2009-04-20 12:47:24

Re: Musca (Tiling Window Manager)

#286 2009-04-20 15:05:43

Re: Musca (Tiling Window Manager)

#287 2009-04-20 15:06:41

Re: Musca (Tiling Window Manager)

#288 2009-04-20 15:08:20

Re: Musca (Tiling Window Manager)

#289 2009-04-20 15:09:56

Re: Musca (Tiling Window Manager)

#290 2009-04-20 15:26:19

Re: Musca (Tiling Window Manager)

#291 2009-04-20 15:32:34

Re: Musca (Tiling Window Manager)

#292 2009-04-21 02:37:09

Re: Musca (Tiling Window Manager)

#293 2009-04-21 10:29:15

Re: Musca (Tiling Window Manager)

#294 2009-04-21 13:44:53

Re: Musca (Tiling Window Manager)

#295 2009-04-21 15:43:54

Re: Musca (Tiling Window Manager)

#296 2009-04-21 15:59:37

Re: Musca (Tiling Window Manager)

#297 2009-04-21 17:02:28

Re: Musca (Tiling Window Manager)

#298 2009-04-21 17:08:35

Re: Musca (Tiling Window Manager)

#299 2009-04-21 17:38:02

Re: Musca (Tiling Window Manager)

#300 2009-04-22 02:09:47

Re: Musca (Tiling Window Manager)

Board footer