Marker selection fails

[alex-w]

The bug report was received via email.

Actual Behaviour

Please find attached a Stellarium Screenshot of the Sky near Abell 520.

I tried to select the star marked with Marker1 and the selection failed. Instead of the star marked with Marker 1 other stars in the neighbourhood were randomly selected. I could select stars in the neighbourhood, but also sometimes with changing/random results, selecting again other stars in the neighbourhood. I could not find a meaningfull pattern in this odd behaviour.

In cases, were a star had a proper name, selecting the star via the search dialog was always possible.

I use your latest weekly snapshot. All Star catalogues are completely loaded and stars up to mag 18 are shown.

[github-actions]

Hello @alex-w!

OK, developers can reproduce the issue. Thanks for the report!

[alex-w]

I can confirm problem with selection tool when FOV is very small.

[alex-w]

The issue probably related to #3136 and #365

[gzotti]

Yes, some stars seem to escape selection. Even if aberration is switched off.

[gzotti]

Yes, it's actually a duplicate of #3136.

[github-actions]

This issue already exists.

[10110111]

near Abell 520

How do I find it? I type "Abell", and the only result I get is "Abell" without a number, and clicking it twice does nothing (why?).

[alex-w]

ACO 520 or Abell 520

[10110111]

ACO 520 or Abell 520

OK, the search for "ACO 520" does find these both, but clicking any of them I get Train Wreck Cluster selected...

[gzotti]

Is that wrong? Remember our "Abell" is ACO, not the PN catalog (which should also go into Stellarium!)
And, seeing the result, should we add an icon for galaxy clusters? (And diameter info?)

[10110111]

Is that wrong?

OK, after googling it appears to be right. But it surely is confusing when you click an object with one name and get an object with another name selected, with no hint that it's the same object. (Yes, enabling Catalog numbers shows "Abell 520", this may be my fault that I had it disabled.)

The case with simply "Abell" search result still looks like a bug though.

[gzotti]

Yes, the Abell "hit" is strange. And it seems to open a query that does not end. Adding a number finally lists possible completions.
I then tried "Barnard" to receive many answers. Added any random number 45. This found LDN1744/Barnard 45. The screen label (after selecting the Barnard catalog in the DSO GUI) shows B45, the name in top-left InfoString is "LDN 1744". Probably when searching for a Barnard object and SIMBAD delivers an object that includes the Barnard number in its name list, also B45 should be retrieved as selected object. (Note I searched for "Barnard 45", not "B45" which does not require Simbad to identify. This adds a layer of complexity to resolve...)