Dates (Heat Overlay): Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 7: | Line 7: | ||
==Notes== | ==Notes== | ||
* It is recommended to use the Heat Overlay Wizard to generate and edit the dates. | * It is recommended to use the Heat Overlay Wizard to generate and edit the dates. | ||
* * The [[Sun altitude (Heat Overlay)|sun altitude]] and [[Sun azimuth (Heat Overlay)|sun azimuth]] are (re)calculated automatically based on the project world location and the date, when the | * * The [[Sun altitude (Heat Overlay)|sun altitude]] and [[Sun azimuth (Heat Overlay)|sun azimuth]] are (re)calculated automatically based on the project world location and the date, when the dates of the overlay are modified via the Heat Overlay configuration wizard. They are not automatically recalculated when the dates attribute of the Heat Overlay is modified directly. | ||
* The dates are stored as '''doubles''' but interpreted as '''longs''', with the value in milliseconds. This is known as a {{timestamp}}. | * The dates are stored as '''doubles''' but interpreted as '''longs''', with the value in milliseconds. This is known as a {{timestamp}}. | ||
Revision as of 10:03, 19 December 2019
Notes
- It is recommended to use the Heat Overlay Wizard to generate and edit the dates.
- * The sun altitude and sun azimuth are (re)calculated automatically based on the project world location and the date, when the dates of the overlay are modified via the Heat Overlay configuration wizard. They are not automatically recalculated when the dates attribute of the Heat Overlay is modified directly.
- The dates are stored as doubles but interpreted as longs, with the value in milliseconds. This is known as a timestamp.