-
-
Notifications
You must be signed in to change notification settings - Fork 850
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weekly 1.22.2-5a6889b: can't select certain objects #2701
Comments
Please share your |
As requested, here is the config.ini |
Sorry, I cannot reproduce the issue on macOS in same version (I tried your and my configs). P.S. @gzotti @10110111 @worachate001 could you check the issue on your systems? |
Tested on Windows 10 and Ubuntu 20.04. I cannot reproduce the issue on both machines. |
cannot reproduce on Win10 21H2 either. When the nebula icons are switched on (not necessarily visible), the object can be selected. That is, if you have activated the SH2 catalog! |
Tested here again. |
That's possible. But when I activate limit mag, NGC1491 loses its hint. |
If you mean with hints, the info in the upper left corner: yes. |
No, hint=icon. (green square. ) So that means, objects with unknown magnitude are not displayed and not selectable when magnitude limiter is active. Well, how to deal with that? Handle as mag8 in such case? Or as mag14? How to deal with missing data? |
Ah ok, that's a hint :) |
I think in July I fixed one problem in this area. Maybe I introduced a new one... For now, disable the limiter. |
Is the issue resolved now? |
I recommended that for now at least @Menno5 should disable the delimiter. FYI the last fix in this area was #2563 in mid-August, following a discussion in a German astro forum. |
The point to keep under observation is the difference of magnitude (pure data item, may be 99 for unknown) and Nebula::getVisibilityLevelByMagnitude() (needed for display/visibility filter decisions; May introduce de-facto false values!) |
I just did see that this got the Opinion tag, so let me clarify :) As for a solution, a suggestion: add an option under or besides Limit Magnitude where we can check to show Brightest, Moderate and/or Low brightness objects? Because that info is most of the time in the description when there is no magnitude data available. That way a magnitude limit can be used and brightness. For example a limit MAG 14 objects and Moderate brightness. |
The fix mentioned above chose an arbitrary fallback mag=12 for all objects with unknown magnitude. If some info about brightness is available elsewhere, consistently, in all cases, of course this could be extended. This is really a matter of a few more if(...)s. Just which existing data can we exploit with which rules? |
Hello @Menno5! Please check the fresh version (development snapshot) of Stellarium: |
Hello @Menno5! Please check the latest stable version of Stellarium: |
Expected Behaviour
When clicking a indicated and labeled object, the object gets selected with a box around it and information is shown in the upper left corner
Actual Behaviour
When a indicated and labeled object is clicked, the object is not selected. Instead, the nearest star (if any) is selected.
Not all objects have this: all galaxies are getting selected for example.
Here a few examples that are not clickable/selectable: SH2-170 (Little Rosette Nebula), NGC 7822, Sh2-132 (Lion Nebula), NGC 7423, PK 064+15 1, LBN 742, NGC 1491 (Fossil Footprint Nebula)
This is just a small example. Most SH objects are not clickable
Steps to reproduce
See actual behaviour.
System
The text was updated successfully, but these errors were encountered: