Do we need to un-register keyboard commands which have been registered
with StelGui::addGuiActions(...)?  What will happen if we don't
un-register them?

On 11 February 2012 09:07, Bogdan Marinov <daggers...@gmail.com> wrote:
> On Thu, Feb 9, 2012 at 1:31 PM, Alexander Wolf <alex.v.w...@gmail.com> wrote:
>> 2012/2/9 Bogdan Marinov <daggers...@gmail.com>:
>>> Bernhard Reutner-Fischer had proposed a dynamic loading mechanism some time 
>>> ago:
>>> https://code.launchpad.net/~rep-dot-nop/stellarium/http_proxy
>>> http://thread.gmane.org/gmane.science.astronomy.stellarium.devel/319
>>>
>>> I thought that this was (based on) his branch, but according to the
>>> log, it's not. Is this a separate development, or what?
>>
>> This branch based on code by Bernhard Reutner-Fischer + my patches +
>> inner merge with trunk for resolve conflicts
>
> OK, thank you. I was looking at the log on the website and I didn't
> notice the inner merge.
>
> Bogdan
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Stellarium-pubdevel mailing list
> Stellarium-pubdevel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Stellarium-pubdevel mailing list
Stellarium-pubdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel

Reply via email to