Skip to content
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

Incorrect RTS Info if stars with no name are subsequently selected #3610

Closed
worachate001 opened this issue Jan 27, 2024 · 2 comments
Closed
Assignees
Labels
bug Something likely wrong in the code
Milestone

Comments

@worachate001
Copy link
Member

There is another issue with RTS. Wrong times will be shown if stars with no name are subsequently selected.

Expected Behaviour

RTS recalculated for current selected object.

Actual Behaviour

RTS of previous star still shown.

Steps to reproduce

  • Select a faint star with no name, look at RTS.
  • Select another faint star with no name.

System

  • Stellarium version: 23.4
  • Operating system: Ubuntu 22.04
@worachate001 worachate001 added this to the 24.1 milestone Jan 27, 2024
@worachate001 worachate001 self-assigned this Jan 27, 2024
@worachate001 worachate001 added the bug Something likely wrong in the code label Jan 27, 2024
worachate001 added a commit that referenced this issue Jan 28, 2024
@alex-w alex-w added the state: published The fix has been published for testing in weekly binary package label Feb 3, 2024
Copy link

github-actions bot commented Feb 3, 2024

Hello @worachate001!

Please check the fresh version (development snapshot) of Stellarium:
https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot

@alex-w alex-w removed the state: published The fix has been published for testing in weekly binary package label Mar 26, 2024
Copy link

Hello @worachate001!

Please check the latest stable version of Stellarium:
https://github.com/Stellarium/stellarium/releases/latest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something likely wrong in the code
Development

No branches or pull requests

2 participants