Sign in to follow this  
Followers 0
sherkas

IE control

2 posts in this topic

When I use silent mode for IE settings it does not supress dialog boxes... but then I am unable to get any code to work to detect or close those dialog boxes after.

When I use _IEPropertySet( $browser, "silent", true) it still shows IE dialog boxes.

I read that you can use _IEAttach( "title", "DialogBox") to attach to the box. I tried this and it does not work

$browser = _IEAttach( "Windows Internet Explorer", "DialogBox") ;IE 7

C:\Program Files\AutoIt3\Include\ie.au3 (4088) : ==> Subscript used with non-Array variable.:

If IsObj($aRet[4]) Then

If IsObj($aRet^ ERROR

>Exit code: 1 Time: 0.313

so now im stuck with this... I am trying to write a script for a webpage however they have reload issues with javascript (the reason the reload dialog boxes come) so ive tried a few methods and im out of solutions for this. I cant get autoit to work with them so how can I deal with these dialogboxes that pop up from IE?

Share this post


Link to post
Share on other sites

C:\Program Files\AutoIt3\Include\ie.au3 (4088) : ==> Subscript used with non-Array variable.:

If IsObj($aRet[4]) Then

If IsObj($aRet^ ERROR

This is a result of a bug on AutoIt 3.2.10.0 function DllCall. It is fixed in the next beta release... I imagine this will be soon, but I have no way of knowing. I installed the 3.2.9.0 beta from the /sav download folder so that I could use _IEAttach with SciTe Alt-F5.

Dale


Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curl

MSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object model

Automate input type=file (Related)

Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded  Better Better?

IE.au3 issues with Vista - Workarounds

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn'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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0