AutoIt v3.3.9.22 Beta

[jpm]

Many thanks I fix the webfile name which was not in accordance with SQLite.dll.au3

Now it is working with the current .22 beta

[jchd]

Ah, warm thanks JP.

[Iczer]

almost forgot about old good bug

it present since stable release. see colour change after mouse hovering on Checkbox1. also attached demo-pic.

#include <ButtonConstants.au3>
#include <GUIConstantsEx.au3>
#include <TabConstants.au3>
#include <WindowsConstants.au3>
#Region ### START Koda GUI section ### Form=
$Form2 = GUICreate("Form2", 320, 250, 555, 555)
$Tab1 = GUICtrlCreateTab(16, 16, 289, 193)
$TabSheet1 = GUICtrlCreateTabItem("TabSheet1")
$Checkbox1 = GUICtrlCreateCheckbox("Checkbox1", 52, 75, 97, 17)
$Checkbox2 = GUICtrlCreateCheckbox("Checkbox2", 52, 107)
GUICtrlCreateTabItem("")
GUISetState(@SW_SHOW)
#EndRegion ### END Koda GUI section ###

While 1
    $nMsg = GUIGetMsg()
    Switch $nMsg
        Case $GUI_EVENT_CLOSE
            Exit

    EndSwitch
WEnd

[guinness]

That issue isn't present when running the stable on Windows 8.1 x64.

[Iczer]

I'm on WinXP x64

also - it's only happen if Checkbox is plased on tab-control

Edited November 10, 2013 by Iczer

[BrewManNH]

Must be an XP thing, because it doesn't happen on Vista x86.

[Iczer]

Created Bug #2527

[kylomas]

Win7 Home 64bit

no problems in stable or beta (run from SCiTE)

[iCode]

anyone else having problems running tidy on their script?

prior to .21 i think it worked fine

in .21 it would run and format the script, then crash every time

in .22 it crashes on startup every time without formatting the script

running it with no extra parms

i can supply a dump file for tidy.exe if it helps

win 7 x64, autoit 3.3.9.2.2 - 32 bit tools mode

Edited November 14, 2013 by iCode

[Exit]

Just use the newest beta of tidy:
http://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/Tidy.exe

[Jos]

anyone else having problems running tidy on their script?

prior to .21 i think it worked fine

in .21 it would run and format the script, then crash every time

in .22 it crashes on startup every time without formatting the script

running it with no extra parms

i can supply a dump file for tidy.exe if it helps

win 7 x64, autoit 3.3.9.2.2 - 32 bit tools mode

 

Should indeed be solved in the current Beta version of Tidy as this was a table space issue with the growing number of UDF's.

Jos

[Exit]

Found a bug in beta 3.3.9.22
My script is very large and therefore I made this small reproducer.

#include <IE.au3>
Func _AutoitError()
    $Text = "Autoitversion = " & @AutoItVersion & @CR
    $Text &= "Scriptline = " & $oIEErrorHandler.scriptline & @CR
    $Text &= "HexError = " & Hex($oIEErrorHandler.number, 8) & @CR
    $Text &= "Description = " & StringStripWS($oIEErrorHandler.WinDescription, 2) & @CR
    Beep(2000, 100)
    MsgBox(48 + 262144, "COM Error in "&@ScriptName, $Text)
EndFunc   ;==>_AutoitError

$oIEErrorHandler = ObjEvent("AutoIt.Error", "_AutoitError")
WinClose("[class:CabinetWClass]") ; close control window
For $i = 1 To 999
    If $i = 3 Then ShellExecute("Control")  ; open control window
    ConsoleWrite("**** " & $i & " ******" & @CRLF)
    $oIE = _IEAttach("nonsense")
    Sleep(3000)
Next

Tested in XP, Win7 and Win 8.1

When running in Prod (3.3.8.1), COM Error is NOT raised.

In Beta(3.3.9.22), COM Error is raised, when certain browser/explorer windows exist. e.g. control panel.

The script closes eventual existing control panels.

A control window is started at the third Iteration of the loop and then, the COM error handler is raised.

 _IEAttach() function seems to be involved.

  

[mLipok]

I test your repro code

the same effect

Win7 Pro 64Bit + AutoIt 3.3.9.22

in both case AutoIt 3.3.9.22 and 3.3.8.1  

Control Panel opens at 3 attempt

but only in 3.3.9.22 error hanlder show the MsgBox

[mLipok]

When I use the Beta version of AutoIt (3.3.9.22) on one of my programs, I have this message:

!>19:54:04 AutoIt3.exe ended.rc:-1073741819

>Exit code: -1073741819    Time: 58.103

 

 

 

 

Can anyone tell me if the number -1073741819 is the result of a some kind of system debug and that on this basis, one of the developers can deduce roughly where the error is.

 

I know I should be prepared reproductive code, for now I'm on track.

 

But the question I've always wondered.

[Jos]

Found a bug in beta 3.3.9.22

My script is very large and therefore I made this small reproducer.

#include <IE.au3>
Func _AutoitError()
    $Text = "Autoitversion = " & @AutoItVersion & @CR
    $Text &= "Scriptline = " & $oIEErrorHandler.scriptline & @CR
    $Text &= "HexError = " & Hex($oIEErrorHandler.number, 8) & @CR
    $Text &= "Description = " & StringStripWS($oIEErrorHandler.WinDescription, 2) & @CR
    Beep(2000, 100)
    MsgBox(48 + 262144, "COM Error in "&@ScriptName, $Text)
EndFunc   ;==>_AutoitError

$oIEErrorHandler = ObjEvent("AutoIt.Error", "_AutoitError")
WinClose("[class:CabinetWClass]") ; close control window
For $i = 1 To 999
    If $i = 3 Then ShellExecute("Control")  ; open control window
    ConsoleWrite("**** " & $i & " ******" & @CRLF)
    $oIE = _IEAttach("nonsense")
    Sleep(3000)
Next

Tested in XP, Win7 and Win 8.1

When running in Prod (3.3.8.1), COM Error is NOT raised.

In Beta(3.3.9.22), COM Error is raised, when certain browser/explorer windows exist. e.g. control panel.

The script closes eventual existing control panels.

A control window is started at the third Iteration of the loop and then, the COM error handler is raised.

 _IEAttach() function seems to be involved.

 

Don't use the Errorhandler in this way as this is already done internally in the IE functions.

Read the IE.au3 code and look at line 329 - 343.  Line 343 is giving the error now.

Jos

[trancexx]

 

When I use the Beta version of AutoIt (3.3.9.22) on one of my programs, I have this message:

 

 

Can anyone tell me if the number -1073741819 is the result of a some kind of system debug and that on this basis, one of the developers can deduce roughly where the error is.

 

I know I should be prepared reproductive code, for now I'm on track.

 

But the question I've always wondered.

 

It's impossible to say what's causing the error without seeing the code you run.

However, AutoIt shouldn't ever error out that way. It's strong indicator of internal bug.

[Jos]

Google is your friend: The error number -1073741819 in hex is 0xC0000005 which indicates an access violation in windows.

When you are just using internal functions this could be a bug or are you doing DLL stuff?

Jos

[mLipok]

Initially it looks like a problem with _sql.au3

But I'm not sure.

I have to spend on analysis of more time.

[mLipok]

Google is your friend: The error number -1073741819 in hex is 0xC0000005 which indicates an access violation in windows.

When you are just using internal functions this could be a bug or are you doing DLL stuff?

Jos

 

I do a test:

first I create _Obfuscated.au3   (/MO)

and to this I add #AutoIt3Wrapper_run_debug_mode=Y

and here are the results:

 

bingo:    DLL 

 

 

44821: 0-0: If $b_czy_nowe_okno_diagnostyczne = True Then

44822: 0-0: _DiagnosticOut_NEW($s_out_text, $v_edit_number)

44875: 0-0: If IsHWnd($h_DiagnosticGUI) = 0 Then Return

44876: 0-0: Local $h_memo = ControlGetHandle($s_nazwa_okna_diagnostycznego, "", "Edit" & $v_edit_number)

44877: 0-0: Local Const $WM_GETTEXTLENGTH = 0x000E

44878: 0-0: Local Const $EM_SETSEL = 0xB1

44879: 0-0: Local Const $EM_REPLACESEL = 0xC2

44880: 0-0: Local $nLen = _SendMessage($h_memo, $WM_GETTEXTLENGTH, 0, 0, 0, "int", "int")

0526: 0-0: Local $aResult = DllCall("user32.dll", $sReturnType, "SendMessageW", "hwnd", $hWnd, "uint", $iMsg, $wParamType, $wParam, $lParamType, $lParam)

0527: 0-0: If @error Then Return SetError(@error, @extended, "")

0528: 0-0: If $iReturn >= 0 And $iReturn <= 4 Then Return $aResult[$iReturn]

44881: 0-0: _SendMessage($h_memo, $EM_SETSEL, $nLen, $nLen, 0, "int", "int")

0526: 0-0: Local $aResult = DllCall("user32.dll", $sReturnType, "SendMessageW", "hwnd", $hWnd, "uint", $iMsg, $wParamType, $wParam, $lParamType, $lParam)

0527: 0-0: If @error Then Return SetError(@error, @extended, "")

0528: 0-0: If $iReturn >= 0 And $iReturn <= 4 Then Return $aResult[$iReturn]

44882: 0-0: _SendMessage($h_memo, $EM_REPLACESEL, True, $sMessage, 0, "int", "wstr")

0526: 0-0: Local $aResult = DllCall("user32.dll", $sReturnType, "SendMessageW", "hwnd", $hWnd, "uint", $iMsg, $wParamType, $wParam, $lParamType, $lParam)

0527: 0-0: If @error Then Return SetError(@error, @extended, "")

0528: 0-0: If $iReturn >= 0 And $iReturn <= 4 Then Return $aResult[$iReturn]

44883: 0-0: Local $nLen = _SendMessage($h_memo, $WM_GETTEXTLENGTH, 0, 0, 0, "int", "int")

0526: 0-0: Local $aResult = DllCall("user32.dll", $sReturnType, "SendMessageW", "hwnd", $hWnd, "uint", $iMsg, $wParamType, $wParam, $lParamType, $lParam)

0527: 0-0: If @error Then Return SetError(@error, @extended, "")

0528: 0-0: If $iReturn >= 0 And $iReturn <= 4 Then Return $aResult[$iReturn]

44884: 0-0: _SendMessage($h_memo, $EM_SETSEL, $nLen, $nLen, 0, "int", "int")

0526: 0-0: Local $aResult = DllCall("user32.dll", $sReturnType, "SendMessageW", "hwnd", $hWnd, "uint", $iMsg, $wParamType, $wParam, $lParamType, $lParam)

0527: 0-0: If @error Then Return SetError(@error, @extended, "")

0528: 0-0: If $iReturn >= 0 And $iReturn <= 4 Then Return $aResult[$iReturn]

44885: 0-0: _GUICtrlEdit_LineScroll($h_memo, 0, _GUICtrlEdit_GetLineCount($h_memo))

8882: 0-0: If $Debug_Ed Then __UDF_ValidateClassName($hWnd, $__EDITCONSTANT_ClassName)

8883: 0-0: If Not IsHWnd($hWnd) Then $hWnd = GUICtrlGetHandle($hWnd)

8884: 0-0: Return _SendMessage($hWnd, $EM_GETLINECOUNT)

0526: 0-0: Local $aResult = DllCall("user32.dll", $sReturnType, "SendMessageW", "hwnd", $hWnd, "uint", $iMsg, $wParamType, $wParam, $lParamType, $lParam)

0527: 0-0: If @error Then Return SetError(@error, @extended, "")

0528: 0-0: If $iReturn >= 0 And $iReturn <= 4 Then Return $aResult[$iReturn]

8989: 0-0: If $Debug_Ed Then __UDF_ValidateClassName($hWnd, $__EDITCONSTANT_ClassName)

8990: 0-0: If Not IsHWnd($hWnd) Then $hWnd = GUICtrlGetHandle($hWnd)

8991: 0-0: Return _SendMessage($hWnd, $EM_LINESCROLL, $iHoriz, $iVert) <> 0

0526: 0-0: Local $aResult = DllCall("user32.dll", $sReturnType, "SendMessageW", "hwnd", $hWnd, "uint", $iMsg, $wParamType, $wParam, $lParamType, $lParam)

0527: 0-0: If @error Then Return SetError(@error, @extended, "")

0528: 0-0: If $iReturn >= 0 And $iReturn <= 4 Then Return $aResult[$iReturn]

44886: 0-0: EndFunc

44823: 0-0: Else

44826: 0-0: If $b_czy_file_log_all = True Then

44829: 0-0: EndFunc

44866: 0-0: EndIf

44867: 0-0: EndFunc

54093: 0-0: EndFunc

52937: 0-0: EndIf

!>23:16:14 AutoIt3.exe ended.rc:255

>Exit code: 255    Time: 562.364

 

 

But I use it with UDF

I mean I use:

_GUICtrlEdit_LineScroll($h_memo, 0, _GUICtrlEdit_GetLineCount($h_memo))

[Exit]

@Jos

Don't use the Errorhandler in this way as this is already done internally in the IE functions.
Read the IE.au3 code and look at line 329 - 343.  Line 343 is giving the error now.

Throwing an error to determine if it is a browser type...?.
Lines 337 to 353 should be replaced by this single line

If $o_window.name = "Windows-Explorer" Then ContinueLoop