From: Damien M. <dam...@gm...> - 2012-05-10 19:42:53
|
Thanks for the responses Ivan and Bogdan. I should have clarified that I do have most things working. My questions were just trying to confirm that I used the most efficient approach. I did read the documentation, wiki, and studied the API and other plugins to get a handle on things. They were all helpful, but perhaps a more detailed wiki entry would be a useful addition. :) > The title bar can be easily copied from an existing window (at least > in Qt Designer) and the code for hooking up the close button is > minimal. I used the designer in QtCreator but didn't figure out how to copy bits of one form into another. I kept getting an error message about needing to break the layout when I tried to paste, but breaking the layout resulted in a mess. User error on my part, I suppose... > I think that you don't need to handle styles manually, unless your > plug-in is using a custom style sheet for some reason. It appears the I need to set the style so that the window title and close box are styled appropriately. > The language code needs to be handled separately because sometimes > there are things like lists in the window that need to be repopulated > when the language is changed. I see. That makes sense. >Stars in the primary catalogs use their Hipparcos number, DSOs use NGC >numbers, SSO names are supposed to be unique, ditto for >constellations. So is the "name" member of StelObject supposed to include the Hipparcos #, NGC #, or SSO name? Or do I need to retrieve this info somehow from the derived class? Thanks, dm |