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

API seems to be restricted to only accept fields of view above 0.001 #184

Open
ylvaselling opened this issue Mar 28, 2022 · 2 comments
Open

Comments

@ylvaselling
Copy link

When using the wwt application and passing JSON messages to it with the api, it seems like smaller fovs than 0.001 aren't used. It is possible to scroll in the window and change the field of view smaller however.

Using this message:
https://docs.worldwidetelescope.org/webgl-reference/latest/apiref/research-app-messages/interfaces/classicpywwt.centeroncoordinatesmessage.html

@pkgw
Copy link
Contributor

pkgw commented Apr 5, 2022

Hi Ylva,

Yes, the way that that message is handled, the FOV/zoom value is clamped:

zoom = DoubleUtilities.Clamp(zoom, ZoomMin, ZoomMax);

With a default minimum of about 0.001:

double zoomMin = 0.001373291015625;

It is possible to configure that minimum value in the underlying implementation, but we don't expose that functionality at the JavaScript/TypeScript/messaging level. Would you find it useful to reduce it?

@ylvaselling
Copy link
Author

I think it would be useful for some cases where the image has a very small field of view. For example, loading the image 'Antares' gives an unexpected behavior in OpenSpace because the fov animation stops when the image is almost not visible, but it is possible to zoom in further by scrolling.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants