Shouldn't it be ATan2(x, y) instead, to reduce user error and confusion? y, x would just introduce an inconsistency because other functions like Pixel/ImageSearch start with x and then y, instead of the other way around.Added ATan2(y, x). [PR #319 by sswwaagg]
ATan2
- Animan8000
- Posts: 58
- Joined: 11 May 2022, 05:00
- Contact:
ATan2
Re: v2.1-alpha.1
Perhaps @swagfag knows. I've never needed that function and honestly put zero thought into it.
A quick search shows that this is the common way to do it.
A quick search shows that this is the common way to do it.
Re: v2.1-alpha.1
x=y=0 should throw as it is not defined. Although y,x are just variable names and we can call them whatever we like, it should probably say y,x in the docs, due to it being conventional. Other conventions exist though, eg, in LibreOffice it is atan2(x,y), which behaves as atan2(y,x) in this new bif. msdn atan2 says y,x.
Cheers.
Cheers.
Return to “AutoHotkey Development”
Who is online
Users browsing this forum: NPerovic and 10 guests