On Wed, 1 Feb 2012 at 21:31:41 +0100, Paul Seelig wrote:
> On 02/01/2012 09:16 PM, Carlos R. Mafra wrote:
> >> - the currently not working "Save Theme" function of the Appearance
> >
> > I think I fixed this one a few weeks ago. I've just tested here and
> > it works.
> >
> For me, only "Save IconSet" works, but "Save Theme" still has no effect.
> This is for the 0.95.1 release tar ball source.
How does your WMRootMenu look like? Mine looks like this:
(
"Save Theme",
SHEXEC,
"getstyle -p \"%a(Theme name, Name to save theme as)\""
),
IIRC, I had to change -t to -p and remove the path specification.
Try it with exactly the above lines in your WMRootMenu (or generate
a new one with wmgenmenu). Your theme will (probably) appear in
~/GNUstep/Library/WindowMaker/Themes.
> > Some changes in the WMRootMenu generated by wmgenmenu together with
> > some fixes in getstyle make it work for me.
> >
> I didn't look any further into this theme stuff, as i don't really use
> it anyway.
I didn't use it too but I spent some time trying to fix this, so if you
report back with the above instructions that will be appreciated.
> >> - any global definition in /etc/GNUstep/Defaults/WMWindowAttributes
> >> can't be overridden by a users' own private
> >> $HOME/GNUstep/Defaults/WMWindowAttributes entries.
> >
> > Really?
> >
> Yes, and it is a bit annoying. I have built up a rather complete
> WMWindowAttributes over time, and for new installations usually use this
> as a global default. A few weeks ago i noted that it is not possible to
> change any private parameters if this very parameter has already been
> defined globally. I would need to look further into this to provide more
> suitable details.
I wasn't aware of this. If you can provide more details that will be
good.
--
To unsubscribe, send mail to [email protected].