Hi<br><br>Is it possible to include apparent magnitude as an index along with the HTM indices within this duration of time?<br><br>I see that this will help us set up magnitude filters properly, because if an object is not shown, it should not be listed in the Find Dialog as well. If we cannot see it in this version, we will postpone this to the next version.
<br><br>James and I were discussing about the same and we realised that it is going to be pretty complicated for asteroids. I hope we can implement it for Deep Sky Objects within this version itself... can we?<br><br>Plus.. I'm stuck up at some point and need help:
<br>As Jason knows, I fixed some bugs with regard to display of asteroids and magnitude limits. I added a clause to selectively popup context menus for asteroids only if their magnitude was smaller than the limiting magnitude. But I am still unable to remove the asteroids from the Find Dialog because the QLists are directly appended without any limiting magnitude criteria. I will have to modify this behaviour to implement a magnitude limit, but that will slow down the startup process. I would like suggestions on how this can be fixed without delaying the startup.
<br><br>Thanks.<br><br>Regards<br>Akarsh<br><a href="http://www.bas.org.in">http://www.bas.org.in</a><br><div><span class="gmail_quote"><br>On 8/11/07, <b class="gmail_sendername">Jason Harris</b> <jharris<br>@<a href="http://30doradus.org">
30doradus.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br><br>Looks like it's now "official", since Allen announced the beta2 freeze on k-d
<br>and k-c-d:<br><a href="http://www.nabble.com/Prepare-for-a-Feature-Freeze-tf4250808.html">http://www.nabble.com/Prepare-for-a-Feature-Freeze-tf4250808.html</a><br><br>regards, and happy hacking!<br>Jason<br><br>On Friday 10 August 2007 11:03, Jason Harris wrote:
<br>> Hello,<br>><br>> On the release-team mailing list we are hashing out a plan to postpone the<br>> application freeze date until the release of beta2. This is currently<br>> scheduled for Aug 20th, but it may slip a bit.
<br>><br>> While the decision has not yet been finalized, it looks like we still have<br>> 1.5 to 2 weeks to get new features in for 4.0.0.<br>><br>> Note that the messages freeze is supposed to happen on that date also.
<br>><br>> We should compile a list of things we want to get into the 4.0 release, and<br>> decide what is realistic. Here's what I'd like to see:<br>><br>> + (James) HTM and SkyLabeler<br>> + (Jasem) DBUS interfaces working, including the ScriptBuilder tool
<br>> + (me) All Calculator modules updated to simplified layouts, including<br>> batch modes.<br>> + (me) Use Quaternions instead of spherical trig to project the sky (much<br>> of the infrastructure is in place, but I'm having trouble getting it
<br>> working. I've asked Torsten (author of marble) to help me with my<br>> implementation).<br>><br>> Anything else? Do we have enough time to get these in (it doesn't have to<br>> be perfect, we can bugfix after Aug 20th)? I'm not sure I'll have time to
<br>> finish the Calculator, but I'll do my best.<br>><br>> regards,<br>> Jason<br><br>--<br>Jason Harris<br><a href="mailto:jharris@30doradus.org">jharris@30doradus.org</a><br>_______________________________________________
<br>Kstars-devel mailing list<br><a href="mailto:Kstars-devel@kde.org">Kstars-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/kstars-devel">https://mail.kde.org/mailman/listinfo/kstars-devel</a><br></blockquote>
</div>