Re: [Stellarium-pubdevel] Back with another plugin question :-)

[Steve I. <st...@in...>]

Hi again,
 
> > Thanks for remembering! Our maps on the ships are not that much 
> > different, although they change more slowly :-)
> >
> > I was waiting for 0.10.0 as I wanted to use the latest "release" 
> > rather than put too many changes in. I'm glad I did as the 
> method for 
> > setting the position has changed rather dramatically (My first 
> > thoughts were "where the hell is "observer->setLatitude"????)
> >
> > We expect to be installing it on the ship (MSC Fantasia, currently 
> > being built in St. Nazaire) next month.
> 
> That's cool, congrats!
> 
> 
> > I'm glad the auto-hide status can be configured - (is it in the 
> > config.ini file, and is there new documentation on that? For some 
> > reason Stellarium can't save my configuration changes. I'm on XP 
> > SP3...)
> 
> I only just added it to the svn version - it's not in the 
> release.  If that's the version you're using, it's 
> mysterious.  I didn't do a windows release recently, so it's 
> possible some win32 specific bug has crept in.

I have been using the 0.10.0 release, so there was no config option. I have
just updated to the latest svn version so I will have a look around. It
still appears to work OK, and my plugin still talks to it!


> The first thing to check is that the config file which is 
> being used is writable and owned by the same user which is 
> running the program. 

Yes, it is, as far as I can tell. Will dig deeper, though!

> > Also, as I mentioned, the current revision build doesn't output any
> > qDebug() stuff. I don't think it's a Qt setup issue as my 
> plugin will 
> > output qDebug() if built with the current Qt (4.4.3) as long as I'm 
> > using the 0.10.0 release.
> 
> I changed the win32 build flags shortly after the release to 
> suppress the cmd window.  You can still see all that stuff by 
> running the program from a pre-existing cmd window - just do 
> "start -> run -> cmd" and then change the installation 
> directory and type "stellarium".

Unfortunately, that's the way I am running it. Whereas before, Stellarium
would start up, output to the command window from which it was run and only
return to the command prompt when closed, now it returns to the command
prompt immediately, so there's no console for the program to write to :-(
Seems like the build flag change has affected that as well.


> > Finally (for now!) I have a problem getting config.ini info 
> from the 
> > main config.ini file to the plugin. QSettings* settings =
> > StelApp::getInstance().getSettings() works OK, and 
> Q_ASSERT(settings) 
> > will not send an error, but when I try to get a value out 
> of settings 
> > (either my own addition or a known good item) it will crash the 
> > application. Any thoughts?
> 
> I don't know why that's crashing.  However, I think it's 
> better to put plugin-specific settings in the plugins 
> module.ini file.  There's an example of how to do that in the 
> latest revision of the AngleMeasure plugin.  Th drawback is 
> that the config window save settings button won't presently 
> save settings.  Like I mentioned before I think we want to 
> make the save action call each module to save it's own 
> settings.  This would make it possible for modules to save 
> settings using the same mechanism.  
> It's not done yet though.

OK, thanks, I'll have a look in the example plugin. I'm not too worried
about saving from the main program as these configs are set up at
installation and should never be changed again.

Thanks for the help!

Best,
Steve