[mythtv] patch: setsetting -> db

[Andy Davidoff]

Where do you want the code, then, if not SetSetting()?

In the future, I would expect the settings to be cached and only flush
out to the database during FlushSettings() or maybe ~MythContext().

I have a lot of difficulty with authoring larger patches which implement
these sorts of features all at once, especially when it usually takes me
a day or two to massage the feature into a form that will be accepted.

Please provide some direction on exactly what you want, since saying
"that doesn't exist, feel free to submit a patch" is obviously a waste
of everyone's time.


#if Drew Whittle /* Feb 25, 09:50 */
> On Tue, 2003-02-25 at 05:18, Isaac Richards wrote:
> > I had kind of meant for SetSetting() to only be temporary storage, and not 
> > write to the database.  The only users of it are the setup program, when it 
> > ensures that there's a Theme and a ThemeQt setting present, and mythvideo, 
> > where the stuff it stores there is only temp storage, and shouldn't be 
> > written to the DB.
> 
> This sounds exactly like what I wanted.
> 
> I am now sooooo confused it's not funny.
> 
> First I get told that the "right" way to save a changed setting is to
> use:
> 
> 	ThemeSelector theme;
> 	theme.setValue(themename);
> 	theme.save(db);
> 
> Then I find that this isn't available in mythfrontend and I'll have to
> make it available, which then leads to a can of worms because of
> everything else that needs to be included.
> 
> Along the way I discover SetSettings and AppearanceSettings.save and
> this seems that is should do what I want, I'm advised that it should
> work but it doesn't.
> 
> Then I'm told that it doesn't do what I want, ok fair enough.
#endif /* drew at lug.net.nz */