xfrun4 problems

[Jannis Pohlmann]

Am Fri, 19 Sep 2008 00:27:43 -0700
schrieb "Brian J. Tarricone" <bjt23 at cornell.edu>:

> On Thu, 18 Sep 2008 21:37:20 +0100 Olivier Fourdan wrote:
> 
> > On Thu, Sep 18, 2008 at 7:18 PM, Brian J. Tarricone
> > <bjt23 at cornell.edu> wrote:
> > > There aren't any defaults, so you probably ran into an issue with
> > > the settings migration script (which should have migrated your old
> > > active keytheme).
> > 
> > As a corollary, does xfconf has some sort of schema like gconf that
> > we can use to set defaults?
> 
> No, it doesn't use schemas -- I wanted to keep complexity down and
> didn't think they'd be worth the effort (I'm still pretty against
> them, but I'm not quite so opposed as I used to be).
> 
> In theory, though, there's a defaults mechanism -- you can put a
> normal .xml file (like one that stores the settings in ~/.config) in
> one of the $XDG_CONFIG_DIRS dirs, but I didn't really think that
> through, and there's a problem with *removing* xfconf properties when
> there's a system property (i.e., it won't work).
> 
> So for now we're just going to use hardcoded defaults in the app until
> I can figure out what the best thing to do with xfconf to make setting
> defaults a bit easier.  (Hopefully by beta2!)

As for the keyboard shortcuts: Defaults just won't work here with the
current way shortcuts are stored. Right now the shortcut is the
property name which makes it easy to detect conflicts between command
shortcuts and xfwm4 shortcuts, but if a user e.g. wants to clear the
shortcurt for a xfwm4 feature, the property will be removed. In this
situation there's no way for xfconf to figure out whether it should use
the global default value or not.

I am planning change the keyboard shortcuts internals again next week
since this is really bothering me. If we use the command names and xfwm4
feature names as property names and keep shortcuts for commands and
xfwm4 in different base properties then overriding the global default
value of xfwm4 shortcuts will be easy: Just set the shortcut value to
an empty string but keep the property. Same for the command shortcuts
but in their case, commands without shortcut would just not be visible
to the user. This is a bit of a workaround but I can't really think
about anything better.

  - Jannis