Custom Query (3927 matches)

The reason I ask for this is for the company I work for, one of the big things they look for in scripts is so that even if it crashes and burns, it will not bother the end user.

In a few other scripting languages I've used there have been options to write all errors to a log and not display them, and this is what I am asking for.

I know that you may be hesitant to put this in, as it could also be useful for malware not alerting users to it's presence, but there are so many other options for that that I don't think it's prohibitive.

I understand that the vast majority of errors can be caught and handled with good coding, but there are some that I don't believe can be done this way, and that is why I make this request.

The folowing script consists of two files: HTTP_UDF.au3:

#include "XMLDomWrapper\_XMLDomWrapper.au3"

Func __HTML_Navigate($sURL, $sUName = "", $sPass = "", $sParam = "", $sMethod = "GET")

[...]
		_XMLFileOpen($sHTMLFile)
		; At that place is $sHTMLFile = "F:\Archiv5\SERG\Development\AutoItScripts\ScriptsSVN\Libs\HTML_UDF\Html_zmzlvdd.tmp"
	EndIf
EndFunc

And _XMLDomWrapper.au3 by Stephen Podhajecki VER:1.0.3.87 :

Func _XMLFileOpen($strXMLFile, $strNameSpc = "", $iVer = -1, $bValOnParse = True)
	; Now $strXMLFile = "F:Erchiv5rERGEevelopmenteutoItScriptsucriptsSVNcibsiTML_UDFTtml_zmzlvdd.tmp"

[...]

EndFunc   ;==>_XMLFileOpen

At no one place the value of $sHTMLFile or $strXMLFile was changed. Only the simple call of _XMLFileOpen with $sHTMLFile as $strXMLFile parameter is changing the value.

"$WS_EX_LAYERED Creates a layered window. Note that this cannot be used for child windows."

And yet example 2 uses $WS_EX_LAYERED in a child window.