Re: Multiple backgrounds

edit file

vi ~/GNUstep/Defaults/WindowMaker


Vagner Machado wrote:

>Remove:
>----- cut -----
> WorkspaceBack = (
>    cpixmap,
>
>"/home/<user>/GNUstep/Library/WindowMaker/Themes/Edoras.themed/edoras.jpg",
>    gray20
>  );
>----- end -----
>
>Execuet
>wmsetbg -e -w 0
>~/GNUstep/Library/WindowMaker/Themes/Edoras.themed/edoras.jpg
>
>wmsetbg -e -w 1
>~/GNUstep/Library/WindowMaker/Themes/Imladris.themed/imladris.jpg
>
>wmsetbg -e -w 2 ~/GNUstep/Library/WindowMaker/Backgrounds/lotr1024.jpg
>
>wmsetbg -e -w 3
>~/GNUstep/Library/WindowMaker/Themes/tolkien.themed/tolkien.png
>
>
>By MPrates
>
>
>
>cga wrote:
>
>  
>
>>[email protected] wrote:
>>
>>[..]
>>
>>    
>>
>>>>OK, now I think we're getting somewhere. What I was thinking about
>>>>was getting the "WorkspaceSpecificBack" directive to disappear, but
>>>>perhaps it would be easier to use "wmsetbg -w n" in a loop, or
>>>>something like that.
>>>>  
>>>>        
>>>>
>>>i would investigate how to use wdread and wdwrite those are very
>>>usefull tools
>>>for editing proplist files, while windowmaker is running
>>> 
>>>
>>>      
>>>
>>And possibly document them..? ;-)
>>
>>Well wdwrite has a man page of  sorts but not much in the way of a
>>user's guide..
>>
>>    
>>
>>>>The type of thing I am talking about about is this:
>>>>
>>>>Assume that you have selected a common theme with only one
>>>>background. This will be set according to the global "WorkspaceBack"
>>>>directive. Then, suppose you set up multiple backgrounds. Fine.
>>>>Then, if you try to reinstate a single global background with a
>>>>theme, for example, only the previously unassigned backgrounds
>>>>change to the theme background. It seems that once
>>>>"WorkspaceSpecificBack" is in your defaults file, it sticks there
>>>>until it gets manually removed,
>>>>or am I missing something obvious?
>>>>
>>>>cheers
>>>>Duncan
>>>>  
>>>>        
>>>>
>>This behavior hasn't changed in ages. When I was playing w/ themes I
>>would dread the ones w/ multiple bg's because I didn't know how to get
>>rid of the "specific"  bg's.. Because once this gets into
>>~/GNUstep/Defaults/WindowMaker there's no amounts of cycling wmaker or
>>rebooting that will get rid of it.
>>
>>So what I did was to create a
>>~/GNUstep/Library/WindowMaker/reset.themed/style file that contains
>>the following:
>>
>>{
>>WorkspaceSpecificBack = (());
>>}
>>
>>and then I would run a setstyle against it to get rid of the
>>troublemakers. IIRC.. You may need to  follow that by a wmaker
>>"Restart" (not shutdown/restart.. use the "Restart" option in the Exit
>>submenu..) .. to refresh the in-core copy of the plist I guess..
>>
>>If you change themes frequently and/or you have many of those
>>"workspacespecific" themes you could probably front-end the setstyle
>>command with a two-line script that does the reset prior to invoking
>>the new theme (?)
>>
>>_______________________________________________
>>INFO: https://windowmaker.org/lists/listinfo/wm-user
>>ARCHIVE: https://windowmaker.org/lists/archive/wm-user/
>>FAQ: http://windowmaker.org/faq.html
>>    
>>
>
>
>  
>

-- 
Vagner Machado
Analista de TI - Seguranca Tecnica
SICREDI SERVICOS -  Porto Alegre
(51) 3358.9911 ramal 9911
http://www.sicredi.com.br


As informações contidas neste e-mail e nos arquivos anexados podem ser informações confidenciais ou privilegiadas. Caso você não seja o destinatário correto, apague o conteúdo desta mensagem e notifique o remetente imediatamente.
_______________________________________________
INFO: https://windowmaker.org/lists/listinfo/wm-user
ARCHIVE: https://windowmaker.org/lists/archive/wm-user/
FAQ: http://windowmaker.org/faq.html