From: Bogdan M. <dag...@gm...> - 2009-09-24 08:36:31
|
Hello to all. Yesterday I committed TelescopeControl version 0.1.3 (rev. 5049). I would like to hear feedback about the new interface and the way telescopes are set up - by choosing a "device model" instead of a telescope server. The Dummy server (the "Stellarium Virtual Telescope" inside the plug-in) can be used to test the plug-ins behaviour if you don't have a GoTo telescope. I would also like to hear suggestions for things to be added before the release of Stellarium 0.10.3. I will have very little time for programming from the beginning of the next week. - Should I add a GUI feature for adding new device models? - "Colour picker" dialogs for labels' and reticle colours? - A log area in the Telescopes windows, showing info and error messages? - A button to export/back up telescope settings? There also seem to be a problem with telescope servers on Windows, but I'm going to start a separate thread about that. Note that my plug-in is not compatible with the new RTS2 driver wrappers, as they use non-standard arguments. Regards, Bogdan Marinov |
From: Fabien C. <fab...@go...> - 2009-09-24 09:09:03
|
Compile works fine, but at startup I get this: Loaded plugin "TelescopeControl" . TelescopeControl: Loading device model descriptions... TelescopeControl: The default device models file has been restored to "/home/fab1/.stellarium/modules/TelescopeControl/device_models.json" TelescopeControl::init() error: file not found: servers Segmentation fault Fabien On Thu, Sep 24, 2009 at 10:36, Bogdan Marinov <dag...@gm...> wrote: > Hello to all. > > Yesterday I committed TelescopeControl version 0.1.3 (rev. 5049). I > would like to hear feedback about the new interface and the way > telescopes are set up - by choosing a "device model" instead of a > telescope server. The Dummy server (the "Stellarium Virtual Telescope" > inside the plug-in) can be used to test the plug-ins behaviour if you > don't have a GoTo telescope. > > I would also like to hear suggestions for things to be added before > the release of Stellarium 0.10.3. I will have very little time for > programming from the beginning of the next week. > > - Should I add a GUI feature for adding new device models? > - "Colour picker" dialogs for labels' and reticle colours? > - A log area in the Telescopes windows, showing info and error messages? > - A button to export/back up telescope settings? > > There also seem to be a problem with telescope servers on Windows, but > I'm going to start a separate thread about that. Note that my plug-in > is not compatible with the new RTS2 driver wrappers, as they use > non-standard arguments. > > Regards, > Bogdan Marinov > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > |
From: Bogdan M. <dag...@gm...> - 2009-09-24 09:12:29
|
On Thu, Sep 24, 2009 at 12:08 PM, Fabien Chéreau <fab...@go...> wrote: > Compile works fine, but at startup I get this: > Loaded plugin "TelescopeControl" . > TelescopeControl: Loading device model descriptions... > TelescopeControl: The default device models file has been restored to > "/home/fab1/.stellarium/modules/TelescopeControl/device_models.json" > TelescopeControl::init() error: file not found: servers > Segmentation fault Yes, you still need to install the telescope servers by hand. I need to make it fail less spectacularly when they are not found. I thought I had fixed all such cases. Bogdan |
From: Barry G. <bar...@ho...> - 2009-09-24 09:14:39
|
Hi Bogdan I have compiled your latest version of the telescopecontrol in Windows. It now goes quite nicely. The only problem I have is the name of the server. All the servers have seem to have an embedded name that appears behind any name you give it in the configuration panel. I have tested it on the LX200 classic and it works well. I did have a problem with the dummy telescope. I tried four computer but only one would display the dummy. When I eventually found the problem it worked on all computers. I have a number of Windows compiled servers and the only ones that work are the TelescopeServerLX200.exe from Johannes original and a dummytelescope.exe server that I compiled from the source none of the others will display the dummy telescope so far. Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes > Date: Thu, 24 Sep 2009 11:36:16 +0300 > From: dag...@gm... > To: ste...@li... > Subject: [Stellarium-pubdevel] TelescopeControl 0.1.3: Feedback, please > > Hello to all. > > Yesterday I committed TelescopeControl version 0.1.3 (rev. 5049). I > would like to hear feedback about the new interface and the way > telescopes are set up - by choosing a "device model" instead of a > telescope server. The Dummy server (the "Stellarium Virtual Telescope" > inside the plug-in) can be used to test the plug-ins behaviour if you > don't have a GoTo telescope. > > I would also like to hear suggestions for things to be added before > the release of Stellarium 0.10.3. I will have very little time for > programming from the beginning of the next week. > > - Should I add a GUI feature for adding new device models? > - "Colour picker" dialogs for labels' and reticle colours? > - A log area in the Telescopes windows, showing info and error messages? > - A button to export/back up telescope settings? > > There also seem to be a problem with telescope servers on Windows, but > I'm going to start a separate thread about that. Note that my plug-in > is not compatible with the new RTS2 driver wrappers, as they use > non-standard arguments. > > Regards, > Bogdan Marinov > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ Looking for a place to rent, share or buy this winter? Find your next place with Ninemsn property http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Edomain%2Ecom%2Eau%2F%3Fs%5Fcid%3DFDMedia%3ANineMSN%5FHotmail%5FTagline&_t=774152450&_r=Domain_tagline&_m=EXT |
From: Bogdan M. <dag...@gm...> - 2009-09-24 09:29:59
|
On Thu, Sep 24, 2009 at 12:14 PM, Barry Gerdes <bar...@ho...> wrote: > Hi Bogdan > > I have compiled your latest version of the telescopecontrol in Windows. It > now goes quite nicely. The only problem I have is the name of the server. > All the servers have seem to have an embedded name that appears behind any > name you give it in the configuration panel. Could you please explain this further? The only thing that you can type in is the telescope name. In 0.1.2 there was a bug where if the Configure button was pressed for an existing telescope, the device model selected in the configuration window would be the first one using the same telescope server as the originally selected one, but this has been fixed now. Please make sure you have updated your source to the latest version and clean your /modules/TelescopeControl folder. > [snip] I have a number of Windows compiled servers and the only ones > that work are the TelescopeServerLX200.exe from Johannes original and a > dummytelescope.exe server that I compiled from the source none of the others > will display the dummy telescope so far. Yes, Johannes' Dummy binary (and probably Matthew's from the Wiki) won't work, as they use slightly different parameters. (Added in revision 4870). Bogdan |
From: Fabien C. <fab...@go...> - 2009-09-24 10:02:54
|
Hi, I just tried it further. It's really becoming a great part of Stellarium :) I have few comments: - In my case I had no servers/ directory at all and it crashed. Once this is fixed, somehow, the fact that the binary servers should come in the stellarium/servers/ directory should be mentioned somewhere within the GUI because it took me some time to get that. - I could start a dummy server and point to an object. Maybe it would be nice to remind users that to point they should do CTRL+1 when they select a telescope in the list. - The program crashed when trying to select the telescope pointer: QSharedPointerData: internal self-check failed: pointer 0xa433480 was already tracked by another QSharedPointerData object Aborted This happens only in debug mode, when you create more than 1 QSharedPointer from the same pointer. To avoid that, never use pointers but only shared pointer when dealing with StelObject. Thanks! Fabien On Thu, Sep 24, 2009 at 11:12, Bogdan Marinov <dag...@gm...> wrote: > On Thu, Sep 24, 2009 at 12:08 PM, Fabien Chéreau > <fab...@go...> wrote: >> Compile works fine, but at startup I get this: >> Loaded plugin "TelescopeControl" . >> TelescopeControl: Loading device model descriptions... >> TelescopeControl: The default device models file has been restored to >> "/home/fab1/.stellarium/modules/TelescopeControl/device_models.json" >> TelescopeControl::init() error: file not found: servers >> Segmentation fault > > Yes, you still need to install the telescope servers by hand. > > I need to make it fail less spectacularly when they are not found. I > thought I had fixed all such cases. > > Bogdan > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > |
From: Barry G. <bar...@ho...> - 2009-09-24 10:14:20
|
Hi Bogdan I will try to be a little more specific. I loaded the LX200 server and deleteted the name except for an underscore (this panel must have an entry). I connect the telescope and select a star. Ctrl 1 is pressed and the LX200 slews to that star and the name "My_second_telescope" is shown on the screen. If I remove the server then shut down stellarium then re-start This time I load the LX200 server and write the name LX200_Telescope in the panel. I connect the telescope and select a star. Press Ctrl 1 and the telescope slews to that star However the original "My_second_telescope" appears behind the new name "LX200_Telescope" Looks dreadful The same thing happens with the dummy server. The default name "My_second_telescope" appears if I use an underscore for the name. If it is the second telescope loaded the default name is "Dummy_Telescope" If I reverse the order of loading the servers I still get "My_second_telescope" for the first slot and "Dummy_Telescope" for the second slot as the default name. The server for the Autostar is a modified version of the LX200 to give more delay in the sending of commands and was built to drive the 494 Autostar controller which has a makeshift control port rather than a true RS232 port. It also requires the delay to be set to 1.5secs for smooth operation. However it will also drive the LX200, AutostarII and 497 controller. Johannes and I worked on this a couple of years ago to get a server that would drive an ETX70 I have a test bed on the bench in front of me with all the works of an LX200 mounted which I use for repairing boads and motors. I also have the works of the ETX70 and 494 controller but it will take me a little time to set it up Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes > Date: Thu, 24 Sep 2009 12:29:47 +0300 > From: dag...@gm... > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] TelescopeControl 0.1.3: Feedback, please > > On Thu, Sep 24, 2009 at 12:14 PM, Barry Gerdes <bar...@ho...> wrote: > > Hi Bogdan > > > > I have compiled your latest version of the telescopecontrol in Windows. It > > now goes quite nicely. The only problem I have is the name of the server. > > All the servers have seem to have an embedded name that appears behind any > > name you give it in the configuration panel. > > Could you please explain this further? The only thing that you can > type in is the telescope name. In 0.1.2 there was a bug where if the > Configure button was pressed for an existing telescope, the device > model selected in the configuration window would be the first one > using the same telescope server as the originally selected one, but > this has been fixed now. Please make sure you have updated your source > to the latest version and clean your /modules/TelescopeControl folder. > > > [snip] I have a number of Windows compiled servers and the only ones > > that work are the TelescopeServerLX200.exe from Johannes original and a > > dummytelescope.exe server that I compiled from the source none of the others > > will display the dummy telescope so far. > > Yes, Johannes' Dummy binary (and probably Matthew's from the Wiki) > won't work, as they use slightly different parameters. (Added in > revision 4870). > > Bogdan > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ POP access for Hotmail is here! Click here to find out more http://windowslive.ninemsn.com.au/article.aspx?id=802246 |
From: Bogdan M. <dag...@gm...> - 2009-09-24 15:58:58
|
On Thu, Sep 24, 2009 at 1:02 PM, Fabien Chéreau <fab...@go...> wrote: > Hi, > I just tried it further. It's really becoming a great part of Stellarium :) > I have few comments: > - In my case I had no servers/ directory at all and it crashed. Once > this is fixed, somehow, the fact that the binary servers should come > in the stellarium/servers/ directory should be mentioned somewhere > within the GUI because it took me some time to get that. The reason for the crash is that I had expected StelFileMgr::findFile to behave in a different way. I've committed a quick fix, but I don't like it - I would like to be able to find the /servers directory if it's in the main directory too, not only in the user's directory. I guess I'll have to use a try/catch. Otherwise, at the moment there are installation instructions in the README file. If the plug-in is going to be distributed separately, I will probably have to include the servers in the package (they are GPL, aren't they?). If is going to be statically linked in Stellarium, the makefile can install the executables in a more central location. > - I could start a dummy server and point to an object. Maybe it would > be nice to remind users that to point they should do CTRL+1 when they > select a telescope in the list. There are already lines about this in the Help window. :) The numbers in the leftmost column are the telescope numbers, they don't just count the number of lines (it is possible to have "1", "5" and "7" without "2", "3", etc.). If you think that this is not enough, I can change the column header to "Ctrl+#" . If this is not enough, I can add a QLabel with a reminder somewhere. > - The program crashed when trying to select the telescope pointer: > QSharedPointerData: internal self-check failed: pointer 0xa433480 was > already tracked by another QSharedPointerData object > Aborted > This happens only in debug mode, when you create more than 1 > QSharedPointer from the same pointer. To avoid that, never use > pointers but only shared pointer when dealing with StelObject. So that's why the bug mysteriously went away when I tested the plug-in on Windows. I decided that I had fixed it somehow. :) I've committed a fix to that. I would also like receive some comments on the suggestions in the initial email (log area, colour pickers, etc.) Regards, Bogdan Marinov |
From: Fabien C. <fab...@go...> - 2009-09-25 09:45:55
|
On Thu, Sep 24, 2009 at 17:58, Bogdan Marinov <dag...@gm...> wrote: > On Thu, Sep 24, 2009 at 1:02 PM, Fabien Chéreau > <fab...@go...> wrote: >> Hi, >> I just tried it further. It's really becoming a great part of Stellarium :) >> I have few comments: >> - In my case I had no servers/ directory at all and it crashed. Once >> this is fixed, somehow, the fact that the binary servers should come >> in the stellarium/servers/ directory should be mentioned somewhere >> within the GUI because it took me some time to get that. > > The reason for the crash is that I had expected StelFileMgr::findFile > to behave in a different way. I've committed a quick fix, but I don't > like it - I would like to be able to find the /servers directory if > it's in the main directory too, not only in the user's directory. I > guess I'll have to use a try/catch. You should always use try catch for the findFile method otherwise you'll get crashes. > Otherwise, at the moment there are installation instructions in the > README file. If the plug-in is going to be distributed separately, I > will probably have to include the servers in the package (they are > GPL, aren't they?). If is going to be statically linked in Stellarium, > the makefile can install the executables in a more central location. I guess the default installation for your plugin will be to link it statically with Stellarium. What could maybe be done, is that you include the servers into your plugin binary, either by creating a new API and link them with your plugin, or by putting them as resources, and install them in the user directory the first time the plugin is started. >> - I could start a dummy server and point to an object. Maybe it would >> be nice to remind users that to point they should do CTRL+1 when they >> select a telescope in the list. > > There are already lines about this in the Help window. :) The numbers > in the leftmost column are the telescope numbers, they don't just > count the number of lines (it is possible to have "1", "5" and "7" > without "2", "3", etc.). If you think that this is not enough, I can > change the column header to "Ctrl+#" . If this is not enough, I can > add a QLabel with a reminder somewhere. It would maybe be useful to have a small info line under the list of telescope, or maybe also to put the info in the tool tip when hovering above the line inthe list. >> - The program crashed when trying to select the telescope pointer: >> QSharedPointerData: internal self-check failed: pointer 0xa433480 was >> already tracked by another QSharedPointerData object >> Aborted >> This happens only in debug mode, when you create more than 1 >> QSharedPointer from the same pointer. To avoid that, never use >> pointers but only shared pointer when dealing with StelObject. > > So that's why the bug mysteriously went away when I tested the plug-in > on Windows. I decided that I had fixed it somehow. :) I've committed a > fix to that. It seems more stable now. Well done. > I would also like receive some comments on the suggestions in the > initial email (log area, colour pickers, etc.) It comes soon! Thanks for your great contribution! Fabien |
From: Bogdan M. <dag...@gm...> - 2009-09-24 16:09:27
|
On Thu, Sep 24, 2009 at 1:14 PM, Barry Gerdes <bar...@ho...> wrote: > Hi Bogdan > > I will try to be a little more specific. > I loaded the LX200 server and deleteted the name except for an underscore > (this panel must have an entry). I connect the telescope and select a star. > Ctrl 1 is pressed and the LX200 slews to that star and the name > "My_second_telescope" is shown on the screen. > If I remove the server then shut down stellarium then re-start > This time I load the LX200 server and write the name LX200_Telescope in the > panel. I connect the telescope and select a star. Press Ctrl 1 and the > telescope slews to that star However the original "My_second_telescope" > appears behind the new name "LX200_Telescope" Looks dreadful > > The same thing happens with the dummy server. The default name > "My_second_telescope" > appears if I use an underscore for the name. If it is the second telescope > loaded the default name is "Dummy_Telescope" > > If I reverse the order of loading the servers I still get > "My_second_telescope" for the first slot and "Dummy_Telescope" for the > second slot as the default name. Thank you. I think I know where is the problem. Do you have any telescopes defined in the traditional way in Stellarium's config.ini? They are not affected by my plug-in and if there are any servers at the ports they expect them to be, they will connect and will react to the same commands, displaying their names on top of the telescopes managed by my plug-in. If this is not the case, please attach Stellarium's log file so I can have a look at the situation. I have tried to avoid such problems by making my plug-in unload Stellarium's TelescopeMgr using StelModuleMgr::unloadModule(), but this causes Stellarium to crash, as the name of TelescopeMgr is used in LandscapeMgr::getCallOrder(). I don't have any other ideas, perhaps Fabien can help here. Regards, Bogdan Marinov |
From: Barry G. <bar...@ho...> - 2009-09-24 21:00:29
|
Hi Bogdan That was the problem. That was in fact the first thing I looked at. I thought I had removed the lines in the config.ini refering to the old method. I must have neglected to save it correctly because when I looked at the config.ini the reference was still there. I have removed it again and now the double print has disappeared. No other problem with the windows dynamic or static version as long as I don't try to compile with Qt 4.5.2 . I followed the instruction as to where to put the servers before I started so I never saw any problems with their location only the problem that some server versions worked and others did not. Today I will assemble another test bed for the ETX70 version so I can try controlling it as well. I won't include the log.txt at this stage as the only reference to the plugins is that they load at start and unload at close. Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes > Date: Thu, 24 Sep 2009 19:09:09 +0300 > From: dag...@gm... > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] TelescopeControl 0.1.3: Feedback, please > > On Thu, Sep 24, 2009 at 1:14 PM, Barry Gerdes <bar...@ho...> wrote: > > Hi Bogdan > > > > I will try to be a little more specific. > > I loaded the LX200 server and deleteted the name except for an underscore > > (this panel must have an entry). I connect the telescope and select a star. > > Ctrl 1 is pressed and the LX200 slews to that star and the name > > "My_second_telescope" is shown on the screen. > > If I remove the server then shut down stellarium then re-start > > This time I load the LX200 server and write the name LX200_Telescope in the > > panel. I connect the telescope and select a star. Press Ctrl 1 and the > > telescope slews to that star However the original "My_second_telescope" > > appears behind the new name "LX200_Telescope" Looks dreadful > > > > The same thing happens with the dummy server. The default name > > "My_second_telescope" > > appears if I use an underscore for the name. If it is the second telescope > > loaded the default name is "Dummy_Telescope" > > > > If I reverse the order of loading the servers I still get > > "My_second_telescope" for the first slot and "Dummy_Telescope" for the > > second slot as the default name. > > Thank you. I think I know where is the problem. Do you have any > telescopes defined in the traditional way in Stellarium's config.ini? > They are not affected by my plug-in and if there are any servers at > the ports they expect them to be, they will connect and will react to > the same commands, displaying their names on top of the telescopes > managed by my plug-in. > > If this is not the case, please attach Stellarium's log file so I can > have a look at the situation. > > I have tried to avoid such problems by making my plug-in unload > Stellarium's TelescopeMgr using StelModuleMgr::unloadModule(), but > this causes Stellarium to crash, as the name of TelescopeMgr is used > in LandscapeMgr::getCallOrder(). I don't have any other ideas, perhaps > Fabien can help here. > > Regards, > Bogdan Marinov > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ POP access for Hotmail is here! Click here to find out more http://windowslive.ninemsn.com.au/article.aspx?id=802246 |
From: Fabien C. <fab...@go...> - 2009-09-25 09:34:49
|
On Thu, Sep 24, 2009 at 18:09, Bogdan Marinov <dag...@gm...> wrote: > On Thu, Sep 24, 2009 at 1:14 PM, Barry Gerdes <bar...@ho...> wrote: >> Hi Bogdan >> >> I will try to be a little more specific. >> I loaded the LX200 server and deleteted the name except for an underscore >> (this panel must have an entry). I connect the telescope and select a star. >> Ctrl 1 is pressed and the LX200 slews to that star and the name >> "My_second_telescope" is shown on the screen. >> If I remove the server then shut down stellarium then re-start >> This time I load the LX200 server and write the name LX200_Telescope in the >> panel. I connect the telescope and select a star. Press Ctrl 1 and the >> telescope slews to that star However the original "My_second_telescope" >> appears behind the new name "LX200_Telescope" Looks dreadful >> >> The same thing happens with the dummy server. The default name >> "My_second_telescope" >> appears if I use an underscore for the name. If it is the second telescope >> loaded the default name is "Dummy_Telescope" >> >> If I reverse the order of loading the servers I still get >> "My_second_telescope" for the first slot and "Dummy_Telescope" for the >> second slot as the default name. > > Thank you. I think I know where is the problem. Do you have any > telescopes defined in the traditional way in Stellarium's config.ini? > They are not affected by my plug-in and if there are any servers at > the ports they expect them to be, they will connect and will react to > the same commands, displaying their names on top of the telescopes > managed by my plug-in. > > If this is not the case, please attach Stellarium's log file so I can > have a look at the situation. > > I have tried to avoid such problems by making my plug-in unload > Stellarium's TelescopeMgr using StelModuleMgr::unloadModule(), but > this causes Stellarium to crash, as the name of TelescopeMgr is used > in LandscapeMgr::getCallOrder(). I don't have any other ideas, perhaps > Fabien can help here. I changed the code from LandscapeMgr. You should now be able to unload TelescopeMgr. Actually, if you plugin completely replaces it, we could as well suppress the module completely. Fabien > Regards, > Bogdan Marinov > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > |
From: Fabien C. <fab...@go...> - 2009-09-25 10:10:47
|
On Thu, Sep 24, 2009 at 10:36, Bogdan Marinov <dag...@gm...> wrote: > Hello to all. > > Yesterday I committed TelescopeControl version 0.1.3 (rev. 5049). I > would like to hear feedback about the new interface and the way > telescopes are set up - by choosing a "device model" instead of a > telescope server. The Dummy server (the "Stellarium Virtual Telescope" > inside the plug-in) can be used to test the plug-ins behaviour if you > don't have a GoTo telescope. > > I would also like to hear suggestions for things to be added before > the release of Stellarium 0.10.3. I will have very little time for > programming from the beginning of the next week. > > - Should I add a GUI feature for adding new device models? > - "Colour picker" dialogs for labels' and reticle colours? > - A log area in the Telescopes windows, showing info and error messages? > - A button to export/back up telescope settings? Those are possible useful features, but I don't think it's necessary for the first release. I have however other comments about the GUI: - I really like the first window with the list, it's clean and clear. - I found the telescope-specific config window pretty confusing however: - What "type" means and its possible values are really unclear. Maybe it could be renamed "Setup type" and the possible values rephrased to be more explicit: like Control "through serial port", "through an external program (on this computer)", "through the network (server on another computer)" or something like that. - Also many GUI elements are displayed when irrelevant, this also adds to the confusion. It's good that they are disabled, but not displayed would be even simpler for the user. - You could group the options in 2 categories: the generical ones: Telescope name, Start/connect at startup, FOV circles and type, then depending on what the type is, the rest of the type-dependant options are dispayed accordingly. - Finally, it could make sense also to have Stellarium Virtual Server appear as a possible type instead of a specific serial port setup. Ok, that's a lot of comments, please please don't take them badly! These are just ideas and please ignore them if they don't fit your tastes! I really appreciate what you're doing and what you already did is infinitely better as how it used to be! Thanks, Fabien |
From: Barry G. <bar...@ho...> - 2009-09-25 21:31:47
|
Hi I have tested the Windows versions (5058) of Stellarium and the Telescope control program on three computers(all different) and I am quite impressed with the performance. Unlike Fabien I saw no problems with the GUI windows. I have loaded and tested the DummyTelescope, LX200, G11 and Autostar servers and they all work perfectly on my LX200 (of course all these use the same protocol) For my money I think 0.10.3 could be released now and put the next changes into 0.11.0. I packaged the completed program and installed it on all my computers without any problems. The only problems I see at the moment are concerned with the plugin for Telescope FOV which still only works as a static module and has the clash of the 7 and 8 keys and the provision of telescope servers. The problem of the telescope servers is odd in so far as the wiki supplied Windows exe's for the telescopes work but I have problems with the supplied Dummy telescope. I have re-compiled the Telescope_server in windows and cross compiled to make the exe's. With this the Dummy telescope works correctly but my cross compiled exe's for the rest do not and the size is only about half. I think it is something to do with the Com port. Also the servers that Matthew compiled do not work on my computer. I have also compiled in Linux but have trouble finding a suitable cross compiler in Linux. Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes > From: fab...@go... > Date: Fri, 25 Sep 2009 12:10:15 +0200 > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] TelescopeControl 0.1.3: Feedback, please > > On Thu, Sep 24, 2009 at 10:36, Bogdan Marinov <dag...@gm...> wrote: > > Hello to all. > > > > Yesterday I committed TelescopeControl version 0.1.3 (rev. 5049). I > > would like to hear feedback about the new interface and the way > > telescopes are set up - by choosing a "device model" instead of a > > telescope server. The Dummy server (the "Stellarium Virtual Telescope" > > inside the plug-in) can be used to test the plug-ins behaviour if you > > don't have a GoTo telescope. > > > > I would also like to hear suggestions for things to be added before > > the release of Stellarium 0.10.3. I will have very little time for > > programming from the beginning of the next week. > > > > - Should I add a GUI feature for adding new device models? > > - "Colour picker" dialogs for labels' and reticle colours? > > - A log area in the Telescopes windows, showing info and error messages? > > - A button to export/back up telescope settings? > > Those are possible useful features, but I don't think it's necessary > for the first release. > > I have however other comments about the GUI: > - I really like the first window with the list, it's clean and clear. > - I found the telescope-specific config window pretty confusing however: > - What "type" means and its possible values are really unclear. > Maybe it could be renamed "Setup type" and the possible values > rephrased to be more explicit: like Control "through serial port", > "through an external program (on this computer)", "through the network > (server on another computer)" or something like that. > - Also many GUI elements are displayed when irrelevant, this also > adds to the confusion. It's good that they are disabled, but not > displayed would be even simpler for the user. > - You could group the options in 2 categories: the generical ones: > Telescope name, Start/connect at startup, FOV circles and type, then > depending on what the type is, the rest of the type-dependant options > are dispayed accordingly. > - Finally, it could make sense also to have Stellarium Virtual > Server appear as a possible type instead of a specific serial port > setup. > > Ok, that's a lot of comments, please please don't take them badly! > These are just ideas and please ignore them if they don't fit your > tastes! I really appreciate what you're doing and what you already did > is infinitely better as how it used to be! > > Thanks, > Fabien > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ View photos of singles in your area Click Here http://dating.ninemsn.com.au/search/search.aspx?exec=go&tp=q&gc=2&tr=1&lage=18&uage=55&cl=14&sl=0&dist=50&po=1&do=2&trackingid=1046138&r2s=1&_t=773166090&_r=WLM_EndText |
From: Bogdan M. <dag...@gm...> - 2009-09-29 09:18:38
|
Hello. I've committed a new version. Please have a look at it and tell me what you think. On Fri, Sep 25, 2009 at 1:10 PM, Fabien Chéreau <fab...@go...> wrote: > On Thu, Sep 24, 2009 at 10:36, Bogdan Marinov <dag...@gm...> wrote: >> Hello to all. >> >> Yesterday I committed TelescopeControl version 0.1.3 (rev. 5049). I >> would like to hear feedback about the new interface and the way >> telescopes are set up - by choosing a "device model" instead of a >> telescope server. The Dummy server (the "Stellarium Virtual Telescope" >> inside the plug-in) can be used to test the plug-ins behaviour if you >> don't have a GoTo telescope. >> >> I would also like to hear suggestions for things to be added before >> the release of Stellarium 0.10.3. I will have very little time for >> programming from the beginning of the next week. >> >> - Should I add a GUI feature for adding new device models? >> - "Colour picker" dialogs for labels' and reticle colours? >> - A log area in the Telescopes windows, showing info and error messages? >> - A button to export/back up telescope settings? > > Those are possible useful features, but I don't think it's necessary > for the first release. OK. > I have however other comments about the GUI: > - I really like the first window with the list, it's clean and clear. I've added a label to display tips ("Press Ctrl+...") and warnings, as discussed in the other emails. > - I found the telescope-specific config window pretty confusing however: > - What "type" means and its possible values are really unclear. > Maybe it could be renamed "Setup type" and the possible values > rephrased to be more explicit: like Control "through serial port", > "through an external program (on this computer)", "through the network > (server on another computer)" or something like that. Yes, you are right, it's not very intuitive. I've renamed the group box and extended the tooltips a bit. I'm thinking of reducing the number of options to two, as there are actually only two cases. The "local connection" mode can be merged with the "remote connection" mode. And I will give them more intuitive names. > - Also many GUI elements are displayed when irrelevant, this also > adds to the confusion. It's good that they are disabled, but not > displayed would be even simpler for the user. All the hardware related stuff now becomes invisible when necessary. :) I'm going to try to solve the problems with telescope servers on Windows, so this is probably the last update of the plug-in for this week. Regards, Bogdan Marinov |
From: Barry G. <bar...@ho...> - 2009-09-27 01:24:17
|
Hi Fabien I have been saying for some time that the windows compiled versions of the telescope servers does not work with the telescopecontrol program. The Dummy server works but the only telescope servers that work are those from Johannes original compile. I have located where the problem starts by going back to earlier source code. Build 3875 works correctly but build 3876 does not. At this point a change was made to lx200connection.cpp as a win32 fix. I have been compiling in windows using "export CROSS_GPP=J:/mingw/bin/mingw32-c++.exe" as my cross compiler but export "CROSS_GPP=J:/mingw/bin/mingw32-g++.exe" also works and produces TelescopeserverDummy.exe, TelescopeSeverLX200.exe and TelescopeServerNextStar.exe. The other servers are derivatives of these. I can't read the code well enough to see what the problem is in the later lx200connection.cpp Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes _________________________________________________________________ POP access for Hotmail is here! Click here to find out more http://windowslive.ninemsn.com.au/article.aspx?id=802246 |
From: Bogdan M. <dag...@gm...> - 2009-09-27 05:04:00
|
On Sun, Sep 27, 2009 at 4:24 AM, Barry Gerdes <bar...@ho...> wrote: > Hi Fabien > > I have been saying for some time that the windows compiled versions of the > telescope servers does not work with the telescopecontrol program. The Dummy > server works but the only telescope servers that work are those from > Johannes original compile. > > I have located where the problem starts by going back to earlier source > code. Build 3875 works correctly but build 3876 does not. At this point a > change was made to lx200connection.cpp as a win32 fix. > > I have been compiling in windows using "export > CROSS_GPP=J:/mingw/bin/mingw32-c++.exe" > as my cross compiler but export "CROSS_GPP=J:/mingw/bin/mingw32-g++.exe" > also works and produces TelescopeserverDummy.exe, TelescopeSeverLX200.exe > and TelescopeServerNextStar.exe. The other servers are derivatives of these. > > I can't read the code well enough to see what the problem is in the later > lx200connection.cpp Thank you for your time, Barry! I was going to compile a list of servers with different revisions and ask you to test them. This is going to be easier. As far as I can see, the only differences are the use of a Windows-specific macro and a changed compiler optimization option. According to my man page about gcc, the -O4 optimization option does not exist. Could you please try to recompile, replacing -O4 with -O2 in /src/Makefile (it can be found three times on lines 40-43). If this fails to produce a difference, could you please try with adding #include "Socket.hpp" in the beginning of Lx200Connection.cpp and NexStarConnection.cpp? I have the suspicion that the macro may not be defined in that scope. Thank you again for your time finding out which revision breaks the code. :) Regards, Bogdan Marinov |
From: Barry G. <bar...@ho...> - 2009-09-27 06:42:29
|
Hi Bogdan I tried both you suggestions on the to the source code but neither gave any change. The LX200 exe files generated still did not work. What is you next sggestion Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes > Date: Sun, 27 Sep 2009 08:03:48 +0300 > From: dag...@gm... > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] TelescopeControl 0.1.3: Feedback, please > > On Sun, Sep 27, 2009 at 4:24 AM, Barry Gerdes <bar...@ho...> wrote: > > Hi Fabien > > > > I have been saying for some time that the windows compiled versions of the > > telescope servers does not work with the telescopecontrol program. The Dummy > > server works but the only telescope servers that work are those from > > Johannes original compile. > > > > I have located where the problem starts by going back to earlier source > > code. Build 3875 works correctly but build 3876 does not. At this point a > > change was made to lx200connection.cpp as a win32 fix. > > > > I have been compiling in windows using "export > > CROSS_GPP=J:/mingw/bin/mingw32-c++.exe" > > as my cross compiler but export "CROSS_GPP=J:/mingw/bin/mingw32-g++.exe" > > also works and produces TelescopeserverDummy.exe, TelescopeSeverLX200.exe > > and TelescopeServerNextStar.exe. The other servers are derivatives of these. > > > > I can't read the code well enough to see what the problem is in the later > > lx200connection.cpp > > Thank you for your time, Barry! I was going to compile a list of > servers with different revisions and ask you to test them. This is > going to be easier. > > As far as I can see, the only differences are the use of a > Windows-specific macro and a changed compiler optimization option. > > According to my man page about gcc, the -O4 optimization option does > not exist. Could you please try to recompile, replacing -O4 with -O2 > in /src/Makefile (it can be found three times on lines 40-43). > > If this fails to produce a difference, could you please try with adding > > #include "Socket.hpp" > > in the beginning of Lx200Connection.cpp and NexStarConnection.cpp? I > have the suspicion that the macro may not be defined in that scope. > > Thank you again for your time finding out which revision breaks the code. :) > > Regards, > Bogdan Marinov > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel _________________________________________________________________ Looking for a place to rent, share or buy this winter? Find your next place with Ninemsn property http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Edomain%2Ecom%2Eau%2F%3Fs%5Fcid%3DFDMedia%3ANineMSN%5FHotmail%5FTagline&_t=774152450&_r=Domain_tagline&_m=EXT |
From: Barry G. <bar...@ho...> - 2009-09-27 07:05:27
|
Hi Bogdan I forgot to mention that the size of the binary that works and the size of the one that doesn't are both 301568 bytes. This is quite a bit smaller than the original 452608 bytes that works and even smaller than the one Matthew compiled 583504 bytes. I think the original and Matthews were compiled in Linux and cross compiled from there. Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes From: bar...@ho... To: ste...@li... Date: Sun, 27 Sep 2009 16:42:22 +1000 Subject: Re: [Stellarium-pubdevel] TelescopeControl 0.1.3: Feedback, please Hi Bogdan I tried both you suggestions on the to the source code but neither gave any change. The LX200 exe files generated still did not work. What is you next sggestion Barry Gerdes Beaumont Hills Observatory S 33' 41' 44" E 150' 56' 32" 12" F10 GPS Polar mounted Home Page http://www.geocities.com/barrykgerdes > Date: Sun, 27 Sep 2009 08:03:48 +0300 > From: dag...@gm... > To: ste...@li... > Subject: Re: [Stellarium-pubdevel] TelescopeControl 0.1.3: Feedback, please > > On Sun, Sep 27, 2009 at 4:24 AM, Barry Gerdes <bar...@ho...> wrote: > > Hi Fabien > > > > I have been saying for some time that the windows compiled versions of the > > telescope servers does not work with the telescopecontrol program. The Dummy > > server works but the only telescope servers that work are those from > > Johannes original compile. > > > > I have located where the problem starts by going back to earlier source > > code. Build 3875 works correctly but build 3876 does not. At this point a > > change was made to lx200connection.cpp as a win32 fix. > > > > I have been compiling in windows using "export > > CROSS_GPP=J:/mingw/bin/mingw32-c++.exe" > > as my cross compiler but export "CROSS_GPP=J:/mingw/bin/mingw32-g++.exe" > > also works and produces TelescopeserverDummy.exe, TelescopeSeverLX200.exe > > and TelescopeServerNextStar.exe. The other servers are derivatives of these. > > > > I can't read the code well enough to see what the problem is in the later > > lx200connection.cpp > > Thank you for your time, Barry! I was going to compile a list of > servers with different revisions and ask you to test them. This is > going to be easier. > > As far as I can see, the only differences are the use of a > Windows-specific macro and a changed compiler optimization option. > > According to my man page about gcc, the -O4 optimization option does > not exist. Could you please try to recompile, replacing -O4 with -O2 > in /src/Makefile (it can be found three times on lines 40-43). > > If this fails to produce a difference, could you please try with adding > > #include "Socket.hpp" > > in the beginning of Lx200Connection.cpp and NexStarConnection.cpp? I > have the suspicion that the macro may not be defined in that scope. > > Thank you again for your time finding out which revision breaks the code. :) > > Regards, > Bogdan Marinov > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel Find your next place with Ninemsn property Looking for a place to rent, share or buy this winter? _________________________________________________________________ Looking for a new car this winter? Let us help with car news, reviews and more http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_OCT07&_m=EXT |
From: Bogdan M. <dag...@gm...> - 2009-09-27 10:54:17
|
On Sun, Sep 27, 2009 at 9:42 AM, Barry Gerdes <bar...@ho...> wrote: > Hi Bogdan > > I tried both you suggestions on the to the source code but neither gave any > change. The LX200 exe files generated still did not work. What is you next > sggestion Hm, that's bad. I've made some modifications and cross-compiled an executable on Ubuntu. It's attached to this patch at SourceForge.net: (it's marked as "Private", so you may need to log in) https://sourceforge.net/tracker/?func=detail&aid=2868023&group_id=48857&atid=454375 Could you please try it and send me the log file? Regards, Bogdan Marinov |