kevingy

Have you reported this as a bug? If not, I can. If it's on the AutoIt side, unless one of the AutoIt devs is aware of this, it won't get fixed.

I can't have all of my users do this manually every time the browser window opens. This is a good suggestion, but it won't work for me. Thanks anyway!

Dale, I realize you likely have higher priorities than this, but have you made any progress? Kevin

I'm glad you've found something and are working on it. Thank you!

Anyone else having this problem? It's been quiet since uploading my sample code. My scripts are working perfectly (right now, as a matter of fact) on my computer with IE8.

Dale, Thanks for the reply. The reason I had to download and install IE9 was because of issues my company was experiencing with the new browser. We had the same "it's always worked before" thoughts too. At the end of the day, we had to force IE9 to operate in IE8 standards mode to avoid lots of work (10 days before roll-out) to "fix" our compatibility issues. In our case, we were easily able to add the needed meta tag to the page header. With my automation tasks, I don't have control over the third party web sites to be able to add the tag. The attached file will crash on IE9 with the error: --> IE.au3 V2.4-0 Error from function _IETagNameGetCollection, $_IEStatus_InvalidObjectType D:\Program Files\AutoIt3\Include\IE.au3 (1727) : ==> Variable must be of type "Object".: For $img In $imgs For $img In $imgs^ ERROR Kevin (Found a problem with the original ie9Test.au3 file. Uploaded new version that demonstrates problem.) ie9test.au3

It would appear that _IETagNameGetCollection is working in some cases, but not in others. I also just found that _IEAction is also working in some cases, but not in others. More to come...

I had to upgrade from IE8 to IE9 for work. Now, many of my AutoIt scripts that perform IE automation are broken. It would appear that there IE9 compatibility issues in AutoIt. I've done some quick and dirty debugging. It looks like calls to _IETagNameGetCollection either returns null or no results in cases where there were valid results under IE8. Furthermore, any _IE methods that rely on _IETagNameGetCollection (for example, _IEFormImageClick) also fail and/or crash. I'll keep looking to see if I can find and fix the problem. If I find it, I'll share the fix. Has anyone else had this issue? If you're doing IE automation and are considering IE9, I'd wait until this issue is resolved. (If you're reading this, though, it's likely already too late.)

I did a brief search for previous requests for this. Do you know why they have dismissed it? It seems like a logical request - to be able to embed the AutoIt scripting engine into an application.

I've already determined that AutoItX doesn't include the interpreter. The intention of my post was to ask, "Shouldn't it?" I suggest adding the interpreter to a version of AutoItX, or perhaps creating a separate product for just this purpose - perhaps AutoItE: AutoIt Embedded. Is the souce available? I'll write it and contribute it. I really want to run scripts, but I'd prefer not to distribute AutoIt3.exe. I'd prefer to run scripts in my own process space rather than having to essentially shell out to another external application. At the end of the day, if that's not an option, I'll have to do one of two things I'd prefer not to do: either shell out to AutoIt.exe or use something other than AutoIt. The trick will be determining which I prefer not to do less.

Unless it's undocumented, I don't see a AutoItX method that will allow me to make a call to run an AutoIt3 script from within my application. When I started looking into AutoItX, I expected to see two methods: AU3_RunScript(LPCWSTR szScript, bool bBlock, long nTimeout) and AU3_RunScriptFile(LPCWSTR szPath, bool bBlock, long nTimeout) to allow my application to run pre-written (from files) or dynamically-generated (in memory) AutoIt3 scripts. Without these two methods, isn't AutoItX nothing more than a high-level WIN32 API wrapper? Can't all languages listed in the AutoItX Introduction make calls into WIN32 API without AutoItX? Granted, the AutoItX API is clean and straightforward, but coding to it requires me to recompile my application when the scripts need to change rather than just updating the script. Am I missing something? I hope I am! I'd really like to use AutoIt3/AutoItX in my application. Kevin