SunMoon calculator

[ravkr]

This script calculates information about the Moon and the Sun (position on the sky, rise, transit, set, Moon phase etc.)

Just enter your longitude and latitude wait a second

 

 

Maybe I'll add ISS, asteroids and planets but I don't promise anything.

 

Needed help with translating!

If you want to translate it to your language just copy section (eg. [English]) from lang.ini, translate all messages and post it here

 

Download link: http://ravkr.duckdns.org/autoit/sunmoon_v1.zip

Report any bugs.

 

Feedback is welcome

 

PS. It's my first script published on this forum

Edited June 16, 2019 by ravkr
fixed links

[Werty]

Boht lniks borken.

Sounds interesting though.

[ravkr]

Boht lniks borken.

Sounds interesting though.

fixed

underscore in links was the problem

[lorenkinzel]

Looks promising; any way we could get:

Includesrav.au3'   ?

[ravkr]

Looks promising; any way we could get:

Includesrav.au3'   ?

my bad

just remove that line :/ its old file where some functions used to be (now its empty)

[mLipok]

there is no space before "Then"

 

>Running AU3Check (3.3.13.0)  from:C:Program Files (x86)AutoIt3  input:L:AU3AU3_z_Forumsunmoon_v1sunmoon.au3
"L:AU3AU3_z_Forumsunmoon_v1sunmoon.au3"(1096,27) : error: missing separator character before keyword.
  If IsArray($BlankBox[0])Then
  ~~~~~~~~~~~~~~~~~~~~~~~~^
L:AU3AU3_z_Forumsunmoon_v1sunmoon.au3 - 1 error(s), 0 warning(s)

[mLipok]

do not use magic number
 
look in 
WindowsConstants.au3
 

Global Const $WM_SYSCOMMAND = 0x0112

look in
MenuConstants.au3

Global Const $SC_CLOSE = 0xF060

 

---

 
please use tidy.exe (CTRL+T in SciTE4AutoIT)
 

---

Func OnSysCommand($hWnd, $Msg, $wParam, $lParam)
;~      ConsoleWrite($hWnd & @TAB & $Msg & @TAB & $wParam & @TAB & $lParam & @LF)
    If BitAND($wParam, 0xFFF0) = 0xF060 Then
        If $hWnd = $GUI Then
            stop()
        EndIf
    EndIf
EndFunc   ;==>OnSysCommand

first check $hWnd and after that check $wParm

Func OnSysCommand($hWnd, $Msg, $wParam, $lParam)
;~      ConsoleWrite($hWnd & @TAB & $Msg & @TAB & $wParam & @TAB & $lParam & @LF)
    If $hWnd = $GUI Then
        If BitAND($wParam, 0xFFF0) = 0xF060 Then
            stop()
        EndIf
    EndIf
EndFunc   ;==>OnSysCommand

 

---

When I change Language then Window is moving to the bottom right corner of screen.

---

 
read some about variable names

---

btw.

Very good script, especially the concept and implementation of the GUI.

 

Dzięki za podzielenie się skryptem i tym samym wiedzą.

Thanks for sharing the script and the same knowledge.

mLipok

[mesale0077]

>Running AU3Check (3.3.11.6)  from:C:\Users\hppc\Desktop\autoit-v3.3.11.6\install
"C:\Users\hppc\Downloads\sunmoon_v1\sunmoon.au3"(145,40) : warning: $ghGDIPDll: possibly used before declaration.
    Local $aResult = DllCall($ghGDIPDll,

error

autoit version: autoit-v3.3.11.6

os :win8

[ravkr]

>Running AU3Check (3.3.11.6)  from:C:\Users\hppc\Desktop\autoit-v3.3.11.6\install
"C:\Users\hppc\Downloads\sunmoon_v1\sunmoon.au3"(145,40) : warning: $ghGDIPDll: possibly used before declaration.
    Local $aResult = DllCall($ghGDIPDll,

error

autoit version: autoit-v3.3.11.6

os :win8

I was still using 3.3.9.24 :/

in new version of GDIPlus.au3 $ghGDIPDll is replaced with $__g_hGDIPDll

I'll fix it in few minutes

Fixed

now it works for old and new UDF

 

Edited June 16, 2014 by ravkr

[UEZ]

Those functions are also included in the GDIPlus.au3 already!

--> _GDIPlus_TextureCreate and _GDIPlus_BitmapCreateFromScan0

Br,

UEZ

[ravkr]

Those functions are also included in the GDIPlus.au3 already!

--> _GDIPlus_TextureCreate and _GDIPlus_BitmapCreateFromScan0

Br,

UEZ

it's my first script with GDI+

I just copied these few lines from veeeery old tutorial

Edited June 16, 2014 by ravkr

[coffeeturtle]

Beautiful work, thank you for sharing.

[czardas]

This looks fantastic and it's a really good idea: quite different from the majority of example scripts posted here. I guess it depends on the intended use, but I was wondering if including some different calendar systems might be useful - perhaps to historians of astronomy. You would need to be selective - using only those calendars which are linked to ancient astronomical observations. This is just an idea and it may require some study - or you might find advice from an online astronomical community. Great idea from you, thanks.

[jchd]

Going far back in time is difficult and full of pitfalls in the case where accuracy is important. Various calendars have not taken their effect uniformly (very far from that) and neither at a precise date in general. So an old event dated with some old calendar in historical documents may have been shifted in time significantly by local unexpected adjustment. In all cases this would be a real mess to get that right despite the various bodies of universe not behaving randomly.

[SlowCoder74]

This looks like a really neat project!  I'm following ...

[czardas]

Going far back in time is difficult and full of pitfalls in the case where accuracy is important. Various calendars have not taken their effect uniformly (very far from that) and neither at a precise date in general. So an old event dated with some old calendar in historical documents may have been shifted in time significantly by local unexpected adjustment. In all cases this would be a real mess to get that right despite the various bodies of universe not behaving randomly.

 

Ah! Very good point. Also many ancient observations were made with imprecise calibration, such as arm length; or stranger still, the size of your earlobe. I read some text about an Egyptian (or Indian) method where two scribes sat opposite one another, night after night, making observations with an hourglass. When a star appeared behind your colleagues head, ear, or another part of their body, the time and position of the celestial appearance was logged. These ancient texts read something like:

'Betelgeuse ascends the right shoulder after seven and a quarter turns (of the glass)'.

I believe that quite a lot of celestial data was recorded this way, over quite a long period of time. I can just imagine the puzzlement on the faces of the historians when they first tried to decipher these ancient writings - 'OMG what have we got here?'. Of course the significance of the text is not immediately apparent.

Edited June 18, 2014 by czardas

[RTFC]

@czardas & jchd:

It's not necessarily always that bad. For example, Stephenson et al. (see here or here or here) used historical solar eclipses to reconstruct the changes in earth's diurnal rotation due to tidal friction and postglacial rebound over several thousand years, going back to Babylonian times.

Calendars can be confusing, but for example the adherence and transition from Julian to Gregorian ( shift of 10+x days, x depending on the reference century) in European sources is often consciously expressed by the author during the period that both systems were used side by side, or can be deduced from other sources with known calendar style that describe the same event.

Complications arise with New Year's Style (instead of Jan 1, maybe Mar 1, or Easter (which moves with the lunar cycle), for example), so you'd read about an event happening in Feb year X, only to discover later that the source used Easter Style, so in modern reckoning it was already year X+1 (this happened to me). Unlike Julian/Gregorian, that's the kind of shift size that really matters when reconstructing geo/astrophysical dynamics. At the other end of the spectrum, historical clock time (uncalibrated by astronomical events such as Venus transits) is often impossible to reconstruct  (in Medieval times, even the next village could be in a different time zone), and local time can be  dependent on the choice of prime meridian, and that is itself a can of worms (there have been hundreds used in the historical past, often without explicit identification). Use of different calendars is far less of a headache in that respect.

Edited June 20, 2014 by RTFC

[jchd]

You're right. Having been a time nut list follower for long time I know that going back in time is harder than within distinct calendars. Even keeping time isn't as easy as it sounds.

In any case, kudos for your app.

[RTFC]

Yeah ravkr, forgot to say so earlier; nice  contribution, it looks great.

RT