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

ocular view: mouse dragging should be just as effective #2086

Closed
axd1967 opened this issue Dec 6, 2021 · 9 comments · Fixed by #2089
Closed

ocular view: mouse dragging should be just as effective #2086

axd1967 opened this issue Dec 6, 2021 · 9 comments · Fixed by #2089
Assignees
Labels
enhancement Improve existing functionality opinion OP thinks something should behave differently
Milestone

Comments

@axd1967
Copy link
Contributor

axd1967 commented Dec 6, 2021

When enabling Ocular view, the mouse becomes restricted to object selection followed by a jump to the selected object; the user can only move the view via cursor keys.

Instead, normal mouse dragging should be possible.

@axd1967 axd1967 changed the title ocular view: mouse navgiation should be just as affective ocular view: mouse dragging should be just as effective Dec 6, 2021
@alex-w
Copy link
Member

alex-w commented Dec 6, 2021

Mouse navigation disabled in eyepiece mode by design to avoid set the wrong FOV

@alex-w alex-w added the state: won't fix We have a reason not to do it label Dec 6, 2021
@github-actions
Copy link

github-actions bot commented Dec 6, 2021

We have a strong reason not to do it! Some reasons for it in the FAQ:
https://github.com/Stellarium/stellarium/wiki/FAQ#Why_dont_you_implement

@github-actions github-actions bot closed this as completed Dec 6, 2021
@axd1967
Copy link
Contributor Author

axd1967 commented Dec 6, 2021

How can a wrong FOV ever be set by mouse?

@axd1967
Copy link
Contributor Author

axd1967 commented Dec 6, 2021

just found, related: #1317
there is no objective reason given there, other than "by design", "has been implemented on purpose in 2010, Just get used to it." -> this is not how software evolves

2021-12-06.09-16-35.mp4

@axd1967
Copy link
Contributor Author

axd1967 commented Dec 6, 2021

If the problem is a "wrong FOV" by "mouse", then the problem is rather "wrong FOV by scrollwheel"; this is a matter of not touching the scrollwheel, not by artificially restricting the user.

@axd1967
Copy link
Contributor Author

axd1967 commented Dec 6, 2021

As the conversation is locked as "too heated" in #1317 (and is likely to get overheated here...), I'll state my use case here:

While searching for C/2021 A1, I needed to fine-move the ocular view in order to perform a star hopping. The cursors did not provide a sufficiently fluid way to do this.

I don't know what the impact would be for tablet users such as @Astro-Martin , but desktop users should not find this a problem.

@alex-w
Copy link
Member

alex-w commented Dec 6, 2021

just found, related: #1317 there is no objective reason given there, other than "by design", "has been implemented on purpose in 2010, Just get used to it." -> this is not how software evolves

Alex, sorry, but you do not known how software evolves in principle, because you are ignore physical laws and objective reality by no objective reason. As proof for working the tool A you are share example for how works the tool B. Other example in this issue: you are ask how zooming by mouse may caused the changing of FOV. Sorry, but this is elementary knowledge and elementary logic.

@axd1967
Copy link
Contributor Author

axd1967 commented Dec 6, 2021

@alex-w please stop insulting me in public. you are here publicly (and repeatingly, ad nauseam, for reasons that you cannot provide despite me repeatingly asking for them) accusing me of

  • being a professional software engineer, not knowing how software evolves
  • ignoring physical laws
  • ignoring "objective reality" (whatever that means)
  • lack of elementary knowledge
  • lack of elementary logic

you are always starting this kind of war, I'm so tired of it because I always try to stay nice, but I will not accept being ridiculed.

my arguments are always and everywhere (because this is a recurring theme in our discussions) the same: as long as there are no theoretical or mathematical limits, there is no reason to impose restrictions to the user. it is the responsibility of the user to correctly interpret the behaviour; it is the responsibillity of the developer to protect the user from actions that could lead to problems.

@xalioth @gzotti @Atque @treaves @Jocelyn1109 please help me here.

@alex-w
Copy link
Member

alex-w commented Dec 6, 2021

My patience has run out! @axd1967 has been banned due permanent toxic behaviour

@Stellarium Stellarium locked as off-topic and limited conversation to collaborators Dec 6, 2021
@alex-w alex-w self-assigned this Dec 8, 2021
@alex-w alex-w added enhancement Improve existing functionality and removed state: won't fix We have a reason not to do it labels Dec 8, 2021
@alex-w alex-w added this to the 0.21.3 milestone Dec 8, 2021
@github-actions github-actions bot reopened this Dec 8, 2021
@alex-w alex-w linked a pull request Dec 8, 2021 that will close this issue
12 tasks
@alex-w alex-w added the opinion OP thinks something should behave differently label Dec 8, 2021
axd1967 referenced this issue in axd1967/stellarium Dec 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Improve existing functionality opinion OP thinks something should behave differently
Development

Successfully merging a pull request may close this issue.

2 participants