Hi, In GTK, the current sound theme name is stored AFAICT in gconf. This in itself makes sense I guess, in that context.
However, if I ever implement libcanberra support (or any alternative Sound Theme implementation (which is very much NOT my intention, but just making a point)) in KDE, then the logical step would be to store the sound theme in some kconfig file. But therein lies the problem. If KDE and GTK sound theme preferences are separate, then running GTK apps under KDE or KDE/Qt apps under GNOME would result in potentially different sound themes which is not ideal. Would there be some scope to instead store the current sound theme in the .config tree? Perhaps expose an API in libcarberra itself which allows the current theme to be set? It could internally use this config as a fallback if the client does not set the theme in the context or play proplists. Perhaps this is too "heavy weight" than is intended for libcanberra, which just wants to be controlled from something externally? What are peoples' thoughts on this? Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] _______________________________________________ libcanberra-discuss mailing list [email protected] https://tango.0pointer.de/mailman/listinfo/libcanberra-discuss
