Removed feature sweepChunk.
The feature was implemented for version 0.19.0 as an iterative way to calculate renderableTrailTrajectory.
However, due to the function not being active by default, and due multithreading being on the horizon for SPICE2, this code is now removed.
- Removed SweepChunk feature
- Added toggle for Accurate Trail Points (in asset: AccurateTrail)
- Changed min number of accurate points from 0 to 2
- Removed max vertices ceiling
- Fixed issue where number of vertices were not calculated properly
- Fixed point size rendering issue for RenderableTrail
- Changed start/end time for voyager 1 & 2
- Updated description for SampleInterval and TimeStampSubsampleFactor to be more clear
- Moved full sweep pass from update function to new updateBuffer function
- Fixed trail rendering issue when time is exact same as start time of a trail
* Add a function for getting all propertyowners matching a certain regex
* Fix broken toggleFade - now works with multiple nodes
* Utilize updated toggle fade function in existing toggle actions
* Make `openspace.propertyOwner` work when only tag is included
* And make toggleFade work in a situation where tag matches both a screenspace renderable and scene graph node
* Remove mistakenly added scene graph node (it is really a screenspace renderable)
* Cleanup property check code to reuse check in both property and propertyowner function
* documentation in FITS renderable
* selected color range bug fix, parameter documentation for fits sphere and field lines sequence renderables
* Very compact description in mission panel
* field line vs fieldline
* Alex comments
* Add missing punctuation
* emmas comments
---------
Co-authored-by: Emma Broman <emma.broman@liu.se>
* Fix faulty log category and minor inconsistencies in GlobeTranslation and GlobeRotation
* Small refactor
* Remove unused return value from initialize function
* Fill attached node in globetranslation initialize and initialize all timeline
Should make the timeline translation work with globetranslations in other cases that the renderabletrails
* Do the same type of change for rotation and scale
* Update initialize function singatures
* Initialize and update translation in trail before use
* Screenspace renderable renderable - move initialize call to initialize
* Refactor trail position calls to make it clearer what is being done
* Call timeframe initialize functions in transform classes
* Do not call update in trail position after all - it borks up the performance
* GlobeTransform: Only fill attached node in init and onchange, and allow nodes without renderable
* Correctly initialize the multi-transform types
* Apply suggestions from code review
* Apply suggestions from code review
Co-authored-by: Alexander Bock <alexander.bock@liu.se>
* Address code review comment
* Update comments in renderabletrail
---------
Co-authored-by: Alexander Bock <alexander.bock@liu.se>
* updates to night sky assets and new actions for ui panel;
* Apply suggestions from code review
Co-authored-by: Alexander Bock <alexander.bock@liu.se>
* swap order of east/south declaration
* updated zeropoint_data to synched resource
* rework action to use fadeIn
* Apply suggestions from code review
update to ns navigation actions
Co-authored-by: Alexander Bock <alexander.bock@liu.se>
* update to position function for review
* removed action based on review
* Update data/assets/actions/nightsky/createsuntrails.asset
up formatting of suntrails action
Co-authored-by: Alexander Bock <alexander.bock@liu.se>
* update to nightsky grids for segement property name change
* updated fade distances for mercury and venus label to be visible from earth when close
* fix to nightsky grid segments
* added time actions to list of nightsky assets
* Update default UI panels to include night sky panel
* fix to add sun trails action
* Show night sky panel in nightsky profile
---------
Co-authored-by: Alexander Bock <alexander.bock@liu.se>
Co-authored-by: Emma Broman <emma.broman@liu.se>
* Remove keybindings to the UP key
Removed the actions as well as they are probably not needed. We have the "now" button and it is rare that one want to interpolate to now
* Replace property_helper usage with function from core_scripts (only `invert` was used)
And retire the property_helper and renderable_helper assets. They are no longer needed!
Alexander Bock