Re: [simon-development] Acoustic Model Switching

[Peter G. <gr...@si...>]

On Monday 19 December 2011 13:59:37 Adam Nash wrote:
> > Does that help?
> 
> Yeah, thanks, it was pretty easy to diagnose with that error message.  I
> wasn't creating the acoustic model cache skeleton (the prompts files
> with specific sample groups) if there was a static model, but I was
> still using those prompts files when the language model changed.  I just
> made it so that it always sets up the cache skeleton whenever it gets a
> new prompts file.  I deleted everything in the cache and started it up
> with a static model and everything worked.
Great.

> >> Also, make sure that the Cancel button works ->   don't work on the
> >> real
> >> configuration but a copy!
> 
> I'm working on making the sample group context config work with the kcm
> format (I didn't know anything about it before, and I just sort of
> hacked a widget together and threw it into the SoundSettings thing).  I
> assume that it will fall into place a little cleaner when I actually
> know what's going on.  The .tag and non-cpp or standard .ui files throw
> me off.
Okay. As always, the documentation on techbase.kde.org is quite good and 
you'll find plenty of examples in the simon code. But I'm sure you'll figure it 
out..


> As far as the singleton stuff goes, I agree that one singleton that
> manages the rest would make sense.  I noticed that the simonview
> destructor (which deletes simoncontrol) never gets called, and there is
> something in main.cpp about it being deleted automatically.  I deleted
> it after the program exits just to see what would happen and it crashes,
> apparently because of something in scenariomanager that depended on
> simonview or part of it.  Should I be doing anything about this
> singleton problem?  It seems like a big project (although, a quick fix
> seems like it would be as simple as finding dependencies between
> singletons and deleting them in the right order).
Yes, but you can leave that to me. I'm hoping I can take a look at that (among 
a couple of other long standing issues) over the holidays.

Best regards,
Peter