Thatsgreat2345 0

Thatsgreat2345 0

Share this post

Link to post

Share on other sites

MHz 74

MHz 74

Looks like Au3Check with Beta defintions used, as ObjEvent is recognized. I would guess that the latest Au3Check with latest definitions is NOT being used. Cannot tell with the limited output as shown to be sure.

Share this post

Link to post

Share on other sites

DaleHohm 62

DaleHohm 62

I downloaded the lastest version of IE.au3, and now I am getting errors when I run a script that used to work with the old IE.au3.

Errors:

C:\Program Files\AutoIt3\Include\IE.au3(2435,53) : ERROR: SetError() [built-in] called with wrong number of args.

If @error Then Return SetError(@error, @extended, 0)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^

C:\Program Files\AutoIt3\Include\IE.au3(2448,39) : ERROR: SetError() [built-in] called with wrong number of args.

Return SetError(@error, @extended, 0)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^

C:\Program Files\AutoIt3\Include\IE.au3(2534,55) : ERROR: ObjEvent() [built-in] called with wrong number of args.

Local $sCurrentErrorHandler = ObjEvent("AutoIt.Error")

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^

Any advice would be great. Thanks.

Those look like AU3Check errors rather than run-time errors. AU3Check is distributed with SciTe, so you may want to insure you have upgraded SciTe in addition to the AutoIt beta. AU3Check's parser rules get updated as significant changes are made to AutoIt and the number of accepted parameters to SetError was changed in a relatively recent beta.

I did not use ObjEvent in the previous version of IE.au3 so you would not have seen taht error... again, I recall AU3Check being enhanced to understand that a single parameter was acceptable for ObjEvent.

I appreciate you including the error messages, but if you had backed up and included ALL of the output it would have been clear where these errors were comming from.

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=YDoesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?

Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=YDoesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?

Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble

_IELoadWait has been rewritten in the new version to address just this issue (an inconsistent timing issue). It is trying to check the readystate of the document before the browser has completed instatiation of it.

If you can, upgrade to the new test version. If you can't, set the $f_wait parameter in your function call to 0 and then call _IELoadWait on your own and pass a $i_delay to it to work around the issue.

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=YDoesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?

Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble

Share this post

Link to post

Share on other sites

MHz 74

MHz 74

It has changed from CompileAu3 to AutoIt3Wrapper in the output. You do have an Else statement in your AutoIt3Wrapper source that can use the old logic with Au3Check if it is not found in the AutoIt3 Dir or Beta Dir as needed?