hi, i need a set of fresh eyes with setstyle. most of what follows is so far guesswork.
so, it takes a theme pack or a style file, updates the defaults database with it, thus giving you a new style. when this is all done, it (tries to) signal wm that re-reading the defaults db is in order, so it picks up changes. which it does automatically, unless it is running in static mode. however, even if it is running in static mode, the handler for this message sent by setstyle is run anyway (src/event.c around 927), so you get your new style. the same seems to hold true for wprefs (WPrefs.c:save()). so, the question is, if wm is running static, should these reconfigure events be honored or not? (i don't yet see if there's a way currently to not even let other clients modify the def db in that case, but that doesn't quite make sense anyway, since you can just do it with vi). it somehow seems strange stat `static' in these cases actually means `static, except...'. if wm is not running static, is there a way for it _not_ to re-read the defaults db if it changes (via inotify, polling it, or whatever)? - also, what are the hackpath* stuff in getstyle really for? to be honest, i have lost the flow of events in getstyle.c:416. there's some magic to determine if the argument is a theme pack or a style file, get the style file if it's a pack, and then the original path to the theme pack directory gets passed down to hackPaths then hackPathInTexture where i have completely lost what the fsck is going on. from what i can gather, it fixes up pixmap paths so that if you have an image that is not given with an absolute path, it will be converted to one. i'm guessing this is because theme packs with their self-contained images are outside of standard pixmap search paths. right..? but why is it not applied if you load a single style file, not a pack? this also means that if you have a theme unpacked somewhere, and do setstyle .../style, it will not be good, whereas only specifying the containing directory makes it ok. i am confused even by writing this. further, how does a plain style file look like and what it is good for anyway? my guess would be it would be like ~/G/D/WindowMaker, but what's the use? old-style theme perhaps? -- [-] mkdir /nonexistent -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
