Latest Beta

[Jon]

3.3.7.14 (10th July, 2011) (Beta)

- Fixed: Bad change to IE.au3 made in 3.3.7.8

- Fixed #1956: 3.3.7.10 COM error getting reference to document in frame.

- Fixed: Attempts to use values for COM OUT parameters trapped.

[Exit]

In announcement 3.3.7.14 (see ) are the links not clickable.

Discuss the beta here.

Report issues here.

Download here.

[MvGulik]

What links.

[taietel]

In announcement 3.3.7.14 (see ) are the links not clickable.

Go to 3.3.7.13 and they will take you right to 3.3.7.14.

[EDIT] Here

Edited July 10, 2011 by taietel

[Exit]

Thanks for your replies. My post should inform Jon about missing links. Perhaps my fault to not send a PM to Jon.

My beta is already on 3.3.7.14

[MvGulik]

Perhaps my fault to not send a PM to Jon.

Naa, Where talking beta here. Not production. (Besides, if its really something important. MVP's of other Dev's will pester Jon about it.)

[big_daddy]

In announcement 3.3.7.14 (see ) are the links not clickable.

Discuss the beta here.

Report issues here.

Download here.

Fixed

Edit: Next time just report the post and one of the mods will take care of it.

Edited July 11, 2011 by big_daddy

[archrival]

I'm drunk on a train home using intermittent 3G signals and can totally field that one.

The previous behavior was a retarded hack-o-mess and the new behaviour is what other sensible languages return.

Thanks, I always appreciate good humor in changelogs. Perhaps this should be the official change notification.

[andygo]

Hello, hope i'm right here.

my script run's fine with version 3.3.2.0. now i've tried the latest beta,

and i get an "error in expression" message. it must be about the following code-snippet.

when i set it as script-comment, everything is fine. but i cant se any error there or am i blind??

local $cfile = FileOpen(@AppDataDir & "\chk.ag", 0)
$tfile = filereadline($cfile, 1)
FileClose($cfile)
if $tfile <> "ein" Then
    MsgBox(16, $interface[18], $interface[138])
    if $apt = 1 then GUICtrlSetData($c29, "")
endif

Edited July 19, 2011 by andygo

[water]

Can you post the error message you get? So we get the line in error.

[andygo]

sorry for interrupt again, but my previous posting didnt contain errors, its at another part of my script.

here i have a stand-alone-code.

if i compile this with the newest beta, the error comes up (shorty after push the test-button on gui)

expandcollapse popup

#include <IE.au3>
#include <GUIConstantsEx.au3>

_IEErrorHandlerRegister ()
_IELoadWaitTimeout (1000)
$oIE = _IECreateEmbedded ()
Opt ("TrayIconHide", 1)
Opt("GuiOnEventMode", 1)
$maingui = GuiCreate("test", 305, 176)
GUISetOnEvent($GUI_EVENT_CLOSE, "_Quit")
$GUIActiveX = GUICtrlCreateObj($oIE, 2, 510, 1, 1)
$button = GUICtrlCreateButton("test", 20, 20, 50, 20)
GUICtrlSetOnEvent($button, "_test")

Local $afile = FileOpen(@TempDir & "\au-ie.htm", 2)
FileWriteLine($afile, "<form action=""http://dummy.url")
FileWriteLine($afile, """ name=""auto"" method=""post""><input type=""text"" name=""title""><textarea name=""message"" id=""vB_Editor_001_textarea"" rows=""10"" cols=""60""></textarea><input type=""hidden"" name=""securitytoken"" value=""")
FileWriteLine($afile, """ /><input type=""hidden"" name=""do"" value=""postreply"" /><input type=""hidden"" name=""t"" value=""")
FileWriteLine($afile, """ /><input type=""hidden"" name=""loggedinuser"" value=""")
FileWriteLine($afile, """ /><input type=""submit"" class=""button"" name=""sbutton"" value=""Antworten"" accesskey=""s"" tabindex=""1"" /></form>")
FileClose($afile)

GuiSetState(@sw_show, $maingui)
While 1
    sleep(20)
WEnd

func _quit()
    Exit
endfunc

func _test()
    _IENavigate ($oIE, @TempDir & "\au-ie.htm")
    $oForm = _IEFormGetObjByName ($oIE, "auto")
    $otitle = _IEFormElementGetObjByName ($oForm, "title")
    $oQuery = _IEFormElementGetObjByName ($oForm, "message")
    $oSubmit = _IEGetObjByName ($oIE, "sbutton")
endfunc

when i compile ith with version 3.3.2.0. it works. i dont understand why the errormessage comes up.

regards, andy (germany)

[PsaltyDS]

That's a pretty crunchy demo, since the embedded IE control is not visible, doesn't call a valid FILE url, and the form action also uses and invalid URL. Fixing all that makes it work fine:

expandcollapse popup

#include <IE.au3>
#include <GUIConstantsEx.au3>

_IEErrorHandlerRegister()
_IELoadWaitTimeout(1000)
$oIE = _IECreateEmbedded()
Opt("GuiOnEventMode", 1)
$maingui = GUICreate("test", 600, 400)
GUISetOnEvent($GUI_EVENT_CLOSE, "_Quit")
$GUIActiveX = GUICtrlCreateObj($oIE, 5, 5, 590, 355)
$button = GUICtrlCreateButton("test", 250, 365, 100, 30)
GUICtrlSetOnEvent($button, "_test")

Local $afile = FileOpen(@ScriptDir & "\Temp1.htm", 2)
FileWriteLine($afile, "<form action=""http://www.autoitscript.com")
FileWriteLine($afile, """ name=""auto"" method=""post""><input type=""text"" name=""title""><textarea name=""message"" id=""vB_Editor_001_textarea"" rows=""10"" cols=""60""></textarea><input type=""hidden"" name=""securitytoken"" value=""")
FileWriteLine($afile, """ /><input type=""hidden"" name=""do"" value=""postreply"" /><input type=""hidden"" name=""t"" value=""")
FileWriteLine($afile, """ /><input type=""hidden"" name=""loggedinuser"" value=""")
FileWriteLine($afile, """ /><input type=""submit"" class=""button"" name=""sbutton"" value=""Antworten"" accesskey=""s"" tabindex=""1"" /></form>")
FileClose($afile)

GUISetState(@SW_SHOW, $maingui)
While 1
    Sleep(20)
WEnd

Func _quit()
    Exit
EndFunc   ;==>_quit

Func _test()
    _IENavigate($oIE, "File:///" & @ScriptDir & "\Temp1.htm")
    $oForm = _IEFormGetObjByName($oIE, "auto")
    $otitle = _IEFormElementGetObjByName($oForm, "title")
    $oQuery = _IEFormElementGetObjByName($oForm, "message")
    $oSubmit = _IEGetObjByName($oIE, "sbutton")
EndFunc   ;==>_test

Edit: Too snarky, too soon. Ran fine with 3.3.6.1 Prod, but failed with 3.3.7.13 and 3.3.7.14. I was thrown off by the reference to the old 3.3.2.0 version. The error is the same for both Betas:

>Running:(3.3.7.14):C:\Program Files\AutoIt3\Beta\autoit3.exe "C:\Temp\Test1.au3"    
--> IE.au3 V2.4-0 Error from function _IENavigate, $_IEStatus_InvalidObjectType
C:\Program Files\AutoIt3\Beta\Include\IE.au3 (1111) : ==> Error in expression.:
Local $o_col = $o_object.document.forms.item($s_Name)
Local $o_col = ^ ERROR
->22:20:30 AutoIT3.exe ended.rc:1

The error looks like it traces back to the known issues already being discussed with __IEIsObjType() failing at ObjName().

You can avoid that check for the navigation by replacing it with the direct method:

Func _test()
    ; _IENavigate($oIE, "File:///" & @ScriptDir & "/Temp1.htm")
    $oIE.navigate("File:///" & @ScriptDir & "/Temp1.htm")
    $oForm = _IEFormGetObjByName($oIE, "auto")
    ConsoleWrite("Debug: $oForm obj name = " & ObjName($oForm) & @LF)

    ; $otitle = _IEFormElementGetObjByName($oForm, "title")
    $otitle = $oForm.elements.item("title")
    ConsoleWrite("Debug: $otitle obj name = " & ObjName($otitle) & @LF)

    ; $oQuery = _IEFormElementGetObjByName($oForm, "message")
    $oQuery = $oForm.elements.item("message")
    ConsoleWrite("Debug: $oQuery obj name = " & ObjName($oQuery) & @LF)

    $oSubmit = _IEGetObjByName($oIE, "sbutton")
    ConsoleWrite("Debug: $oSubmit obj name = " & ObjName($oSubmit) & @LF)

    _IEFormElementSetValue($otitle, "$otitle")
    _IEFormElementSetValue($oQuery, "$oQuery")
    Sleep(2000)
    _IEAction($oSubmit, "click")
EndFunc   ;==>_test

Note the _IEFormElementSetValue() functions still get the same error for the same reason.

_IEGetObjByName() succeeds getting $oSubmit, because it doesn't call __IEIsObjType(), so that works.

Edited July 20, 2011 by PsaltyDS

[andygo]

hello,

your detailed answer implies that you take some time for my problem, thanks therefore.

i don't see it as snarky.

That's a pretty crunchy demo, since the embedded IE control is not visible, doesn't call a valid FILE url, and the form action also uses and invalid URL. Fixing all that makes it work fine:

not visible: i want it invisible, this function is for sending posting-data to a forum. dont worry, its NOT a bot or something illegal. i use it for posting screenshots.

valid FILE url: ok that was my fault.

invalid url: that was just as an example, in my script the url is valid

You can avoid that check for the navigation by replacing it with the direct method:

indeed, that works with the beta! i will run some more tests to watch it's stability.

Note the _IEFormElementSetValue() functions still get the same error for the same reason.

i use this at some other places in my script, have to watch it's attitude with the made changes now.

[PsaltyDS]

I get what you mean about wanting to hide the embedded IE, and that doesn't necessarily mean something malicious. But when you post a demo for the purpose of getting help it should be as short, clear, and simple as possible while still reproducing your symptoms. To the extent I was complaining, it was just that you were making unnecessarily difficult to help with your issue.

[andygo]

I get what you mean about wanting to hide the embedded IE, and that doesn't necessarily mean something malicious. But when you post a demo for the purpose of getting help it should be as short, clear, and simple as possible while still reproducing your symptoms. To the extent I was complaining, it was just that you were making unnecessarily difficult to help with your issue.

thanks again, next time i will explain it as simple as possible. as i can read in the ticket-system, the problem is already fixed:

http://www.autoitscript.com/trac/autoit/ticket/1975

[archrival]

I was wondering if there is a planned release date for a new release? I'm specifically wondering if there will be a new stable release before the end of Q4 2011? I'm in the stages of planning a project and my employer would like to not use a beta version of AutoIt. However, if the release is planned before my project end date we can code against the beta. Thank you for the information.

[Valik]

Tell your boss that we just decide one day to remove the beta designation and magically all bugs just vanish. Or you can tell him the truth that one day we just decide to remove the beta designation and the "final" release is virtually if not completely identical to the last "beta" release without the beta branding.

[archrival]

Tell your boss that we just decide one day to remove the beta designation and magically all bugs just vanish. Or you can tell him the truth that one day we just decide to remove the beta designation and the "final" release is virtually if not completely identical to the last "beta" release without the beta branding.

We aren't so much concerned about remaining bugs as we are about the designation "beta" has. We're a software company, we know software ships with known and unknown bugs, but you weigh the risk of releasing. I also know that when we start a project we have a target release date. I wasn't sure if anyone had a date in mind or if it is more of a calculated assessment of remaining bugs/issues and the date could be any time between now and 2038.

I've used the beta and have seen some minor increases in speed, any speed increase is welcomed for our project. If there weren't breaking changes in the beta in functions I use I wouldn't be as concerned either (granted the changes are simple to implement).

I hope I'm not coming across as some guy asking when Duke Nukem Forever will be released...

[Valik]

Duke Nukem Forever is out. I get your point, and yes, that is what you are. Our release policy always has been "When it's done."

[MvGulik]

(Nevermind)

Edited August 16, 2011 by iEvKI3gv9Wrkd41u