@COM_EventObj - equivalent for Error ?

[mLipok]

I began to wonder if there is an equivalent of this macro @COM_EventObj, but working within the COM Error Handler Function ?

 

You can say there is: ".source Name of the Object generating the error (contents from ExcepInfo.source) "

but just simple test:
open helpfile for:

ObjEvent()

open first example, run it, and look in console output:

and what I get, is here:

ObjEvent.au3 (35) : ==> COM Error intercepted !
    err.number is:         0x80020006
    err.windescription:    Nieznana nazwa.

    err.description is:     
    err.source is:         
    err.helpfile is:     
    err.helpcontext is:     
    err.lastdllerror is:     0
    err.scriptline is:     35
    err.retcode is:     0x00000000

 

 

[trancexx]

Nope.
...Nor it should be.

[mLipok]

...Nor it should be.

 

With all due respect I do not fully understand the context of your expression.

It should not be - ie. It was not but I'm not sure why rather not have - EDIT: you say you are not sure ?
It should not - because they simply should not even in the future - EDIT: you say this is imposible and I can not wait for this in future ?

EDIT2: It is possible that I totally did not understand so short speech - if none of the above did not match, please make broader statement.

Edited September 14, 2015 by mLipok

[trancexx]

The context was provided by you.

You asked:

I began to wonder if there is an equivalent of this macro @COM_EventObj, but working within the COM Error Handler Function ?

...And I answered: "No, nor it should be."

What are you afraid of? If you have an idea or question then ask and explain your ideas. So what if some uber-developer thinks your ideas are stupid. You will never learn if you'd be afraid to ask the real questions.

If I were you I would say "Hey guys, I have an idea! What if we would be able to reference the object that a COM error was generated on inside the event handler function and then use that object to do... this and that. You think that'd be good idea?" Geeze mLipok.

[mLipok]

 

I have an idea.
I would like to have access to the object that causes the COM ERROR handler.
I would like the access was similar, eg for a macro @COM_EventObj

Why?
I think then it may be one function (for ERROR captured by COM ERROR Handler), which could in different ways handle these errors with relation to Object which fires ERROR .

Here is example.

expandcollapse popup

; User's COM error function. Will be called if COM error occurs
Func _MyErrFunc($oError)

    Local $sAutoItIncludeDir = StringReplace(@AutoItExe, '\Aut2exe.exe', '')

    If _
            StringInStr(ObjName(@COMERROR_obj, 1), 'IXMLDOMNamedNodeMap') Or _
            StringInStr(ObjName(@COMERROR_obj, 1), 'DOMDocument') Or _
            StringInStr(ObjName(@COMERROR_obj, 1), 'IXMLDOMNode') Or _
            StringInStr(ObjName(@COMERROR_obj, 1), 'IXMLDOMSelection') _
            Then
        ConsoleWrite(@ScriptDir & '\XMLWrapperEx.au3' & " (" & $oError.scriptline & ") : UDF ==> COM Error intercepted ! " & @CRLF
    ElseIf _ ; IN NEXT LINE I USE param =3 for ObjName )
            StringInStr(ObjName(@COMERROR_obj, 3), 'ADODB.Connection.6.0') _
            Then
        ConsoleWrite(@ScriptDir & '\_sql.au3' & " (" & $oError.scriptline & ") : UDF ==> COM Error intercepted ! " & @CRLF
    ElseIf _
            StringInStr(ObjName(@COMERROR_obj, 1), 'Word.Application') _
            Then
        ConsoleWrite($sAutoItIncludeDir & '\Include\word.au3' & " (" & $oError.scriptline & ") : UDF ==> COM Error intercepted ! " & @CRLF
    Else
        ; any other UDf ......
        ConsoleWrite(@ScriptName & " (" & $oError.scriptline & ") : ==> COM Error intercepted !" & @CRLF
    EndIf

    If StringInStr(ObjName(@COMERROR_obj, 3), 'ADODB.Connection.6.0') Then
        ; use this following example for SQL Error Collection:
        ; https://www.autoitscript.com/forum/topic/175845-objevent-ado-sql-error-collections/
        ; of coruse if I have @COMERROR_obj then I do not must have
        ;       Global $oADODB_Connection = ObjCreate("ADODB.Connection")
        ; as reference to this object would be in @COMERROR_obj
    Else
        ; continue dumping error details to console
        ConsoleWrite( _
                @TAB & "err.number is: " & @TAB & @TAB & "0x" & Hex($oError.number) & @CRLF & _
                @TAB & "err.windescription:" & @TAB & $oError.windescription & @CRLF & _
                @TAB & "err.description is: " & @TAB & $oError.description & @CRLF & _
                @TAB & "err.source is: " & @TAB & @TAB & $oError.source & @CRLF & _
                @TAB & "err.helpfile is: " & @TAB & $oError.helpfile & @CRLF & _
                @TAB & "err.helpcontext is: " & @TAB & $oError.helpcontext & @CRLF & _
                @TAB & "err.lastdllerror is: " & @TAB & $oError.lastdllerror & @CRLF & _
                @TAB & "err.scriptline is: " & @TAB & $oError.scriptline & @CRLF & _
                @TAB & "err.retcode is: " & @TAB & "0x" & Hex($oError.retcode) & @CRLF & @CRLF)
    EndIf

EndFunc   ;==>_MyErrFunc

 

As I said it by this snippet:

If StringInStr(ObjName(@COMERROR_obj, 3), 'ADODB.Connection.6.0') Then
        ; use this following example for SQL Error Collection:
        ; https://www.autoitscript.com/forum/topic/175845-objevent-ado-sql-error-collections/
        ; of coruse if I have @COMERROR_obj then I do not must have
        ;       Global $oADODB_Connection = ObjCreate("ADODB.Connection")
        ; as reference to this object would be in @COMERROR_obj
    Else

In this case some UDF do not need to define additional Global Varaibles to properly/completly handle COM errors.

 

Beside any body will be able to debug by example checking state or any properties of object that fires the error.

What you think dev, mod, MVP and others members ?

 

Edited September 15, 2015 by mLipok
wording

[mLipok]

In this case some UDF do not need to define additional Global Varaibles to properly/completly handle COM errors.

In this above statement I mean for example this following declaration:

Global $oADODB_Connection = ObjCreate("ADODB.Connection")

Which is needed in Global Scope only when somebody want Handling Error Collections.

 

EDIT:
I hope that @Jon will be able to look at here in his spare time, and give their opinion.

Edited September 14, 2015 by mLipok

[mLipok]

I'm thinking about opening FeatureRequest on TrackTicket.
In the meantime, I look forward to a possible discussion.
If my earlier statement was not clear, please me at this point.