Closed mmikeww closed 3 years ago
see also Issue #21
it looks like maybe AHK changed the call stack at some point, because the exception now needs to be back to -1
@hoppfrosch am i doing something wrong? it looks like you fixed issue #21 in commit 49f0f3b26f9 , but on my machine, i need -1
in order to get the correct line number. -2
shows the Yunit.ahk line number
Sorry for the much to late answer .... lost this project out of focus.
Verified that -1 is the correct value with AutoHotkey v2.0beta1. Cannot comprehend when call stack was changed.
the output modules check the
result.line
andresult.file
to give the user more information, but these always point to the main Yunit.ahk file, which is useless in helping to quickly find the location of the assertion fail