_IEAction

[DW1]

when using _IEAction either forward or back, I get an error if there is no page to goto. In other words, if you open a new embedded browser control, and have it start at www.google.com and send the _IEAction( $oIE, "forward" ) command, my script will crash (there is no page to go to, as I am at the furthest page in the history)

Is there a way to view the forward and back list of pages?

Or anything that solves this issue?

[DaleHohm]

Take a look at the example in the helpfile for _IECreateEmbedded -- it does EXACTLY what you are trying to do.

Dale

[DW1]

OMG... LOL thanks

I was missing this:

_IEErrorHandlerRegister ()

[mikehunt114]

Hi Dale, I was looking at this situation and was wondering if there's a reason you couldn't include a trap for this in _IEAction. The CommandStateChange event could alert you of the enabled/disabled state of the forward or backward actions. A switch on the command value and whether it changed the forward or backward parameter value, along with an "If enabled" statement should trap this, no? Just so you get where I'm coming from:

Global Const $CSC_UPDATECOMMANDS = 0xFFFFFFFF
Global Const $CSC_NAVIGATEFORWARD = 0x00000001
Global Const $CSC_NAVIGATEBACK = 0x00000002

$oSinkObject = ObjEvent($oIE, "IEEvent_", "DWebBrowserEvents")

Func IEEvent_CommandStateChange($command, $enable)
    Switch $command
        Case $CSC_NAVIGATEFORWARD
            If $enable = True Then
                $allowForward = True
            Else
                $allowForward = False
            EndIf
        Case $CSC_NAVIGATEBACK
            If $enable = True Then
                $allowBack = True
            Else
                $allowBack = False
            EndIf
    EndSwitch
EndFuncoÝ÷ Ù8^)È-ò¢èî²ÙÞyÖ§jëh×6If $allowForward Then
    ;appropriate code here
Else
    SetError(1)
EndIf

I realize it can be dealt with every easily by adding _IEErrorHandlerRegister() to your script, but for completeness' sake, could a trap in _IEAction be a better solution?

[DaleHohm]

Hi Dale, I was looking at this situation and was wondering if there's a reason you couldn't include a trap for this in _IEAction.

Yes, housekeeping.

Those event procedures are associated to a specific IE instance... you can create any number of IE instances in a particular session... when would I release one? When might I try to reuse one?

So, if you want to do this sort of thing it is left to you in your script.

The only event traps I deal with are AutoIt.Error and even that is very complex...

Dale