|
Hi all,
maybe I've found a bug in kix32 (v4.66). Let me explain:
Sometimes, I want to be able to debug my scripts, I do this calling them the following way:
kix32.exe test.kix %debug%
%debug% is normally empty, so kix script runs not in debug mode. As soon as assign " /d" to debug, kix script is called with /d parameter and can be debuged. This worked fine in Windows 8.1 environment, but not with Windows 10. Doing the same in W10 results in the following:
kix32.exe test.kix %debug%
Start of Scrpt
KIX Version is 4.67
End of Script
ERROR : failed to find/open script [ /d]!
Seems that parameter /d is treated as script..
Strange...
| 
