-
Notifications
You must be signed in to change notification settings - Fork 4
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
spectra appearance #102
Comments
Nadia Halidi <[email protected]> writes:
I find it difficult to compare spectra when I change or add a new entry as each time I change
something the spectra appear as coming from the bottom of the page and not just appear on the
page. It would make it easier to have no effects when a new setting is loaded.
Looking at the docs I think we can remove the animation but I am busy
with my grant till at least late tomorrow. I will try to look at it
after that.
The laser can be easily integrated by creating a file with....
## Name: 639-laser
## Type: laser
wavelength,intensity
638,0
639,1.0
640,0
then use the import... to add it to a running copy of spekcheck. I will
add it to the main version when we have time.
Ian
|
This worked great. Sure, no rush adding it to the main version. We will have the 639nm in ~ September. Thanks. |
I played with the animation and it does work but not as well as you might hope. The graph still flickers and it isn't easy to see that changes versus the static stuff. This is because selecting a new setup destroys the existing graph and creates a whole new one. What are you trying to compare? we may be able to do it better if we have a specific use case in mind |
I find it difficult to compare spectra when I change or add a new entry as each time I change something the spectra appear as coming from the bottom of the page and not just appear on the page. It would make it easier to have no effects when a new setting is loaded.
The text was updated successfully, but these errors were encountered: