0

[Bug - Needs Path To Reproduction] Incorrect Telescope Selected For FOV

Sander Berents

April 14, 2018 01:42

None

Follow

I have added multiple telescopes, eyepieces, a camera, a barlow and two focal reducers to the equipment list. Besides the (known) inability to remove them, another issue I run into is that when I select them for the FOV overlay, always the first telescope is selected. For example if it lists "None", A, B, and when I select B, it uses A for the overlay. If I then select the FOV for editing, it selects "None" in the telescope list.

It only seems to be an issue with the first dropdown, for the telescope selection.

This is on SkySafari 6.0.2 Pro on macOS 10.13.4.

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Bill Tschumy April 16, 2018 13:48

  I'm not seeing this.  Are you sure you have the same FOV indicator shown (checkmarked) as you are changing?

• 0
  
  Sander Berents April 17, 2018 05:25

  The problem is unrelated to the checkmark. Only the "None" and the first telescope in the list sticks. Right now I have 4 FOVs. I just set them all back to "None" for telescope (I can't delete any), so then have 4x "Choose Equipment...", the last of which also has the sublabel "Fetching...". Then I once again tried to use the 2nd telescope for some, but they all still stick to the 1st telescope. The last one always gets that blue sublabel "Fetching..." when I select "None" as telescope for it, whereas the others have no sublabel if I do the same.

• 0
  
  Bill Tschumy April 17, 2018 14:08

  First question: You say you can't delete any of the FOV indicators?  If you select one, doesn't the "-" button enable?  I haven't sen that either.

  Second question: The fact that you are seeing "Fetching..." indicates a problem somewhere.  The you say that only "None" or the first telescope "sticks", can yo explain that a bit more?  Can choose other telescopes?  When does it go back to either None or the first one?  Is it after you dismiss the panel and return to it?

  I'm going to turn this forum post into a support ticket.  This is unlikely to be of general interest and it look like we will need to dig down a bit.  Please answer via the email you should get for the ticket.