3.1.1++

[Josbe]

UDPOpen ( IPAddr, port )

Just gives me errors. I'm a total newbie though, so I might be doing things wrong. I just get an "Error in expression", when trying to do a

UDPOpen ( 127.0.0.1, 5678 )

Am I'm the one at fault here, or is there something wrong with the UDP functions?

<{POST_SNAPBACK}>

Just add the quotes to an expression like an IP:

UDPOpen ( "127.0.0.1", 5678 )

Read the manual about the Datatypes...

[MHz]

If that is the case, then:

UDPOpen ( IPAddr, port )

should be

UDPOpen ( "IPAddr", port )

in the helpfile.

[jpm]

If that is the case, then:

UDPOpen ( IPAddr, port )

should be

UDPOpen ( "IPAddr", port )

in the helpfile.

<{POST_SNAPBACK}>

We could have taken this convention but it is not the only place to change in the whole help.

What is the truth is what is described in the parameter definition. In fact I just copy what is in the MSDN doc.

Anyway I will improve the doc

Thanks

[MHz]

We could have taken this convention but it is not the only place to change in the whole help.

What is the truth is what is described in the parameter definition. In fact I just copy what is in the MSDN doc.

Anyway I will improve the doc

Thanks

<{POST_SNAPBACK}>

I have noticed on occasions.

MSDN, good guide. A little gesture with " " helps us know the difference.

Many thanks.

Especially big thanks from myself.

[jpm]

23th May 2005 - v3.1.1.39 (beta)

Fixed : GuiCtrlSetState on non active tab. (Thanks DaleHolm)

Updated : UDFs 1.15 (By JdeB/gafrost)

- Added 2 Functions to GuiListView.au3: _GUICtrlListViewSetItemSelState and _GUICtrlListViewSetItemText (gafrost)

- fixed type in _GUICtrlListViewGetExtendedListViewStyle helppage.

- fixed typo in _ViClose helppage.

[therks]

I finally got around to having some free time, when I discover that the option,'GUIDataSeparatorChar' does not work (hasn't seemed to work since .36 or before, not sure). Otherwise everything seems to be okay.

But a question, when this option is fixed, is there a posibility for it to be expanded to also affect other functions which use | as a seperator? Like the return from FileOpenDialog when multiple files are selected? There are others I think, but can't recall them offhand.. It's not really a huge deal, but it could be handy.

Oh, and one thing I found that was odd. You'll have to try this one for yourself. Open up the AutoIt.chm. Go to the search tab, type in "separator" (no quotes). Hit 'List Topics', and if you have the same file as I do, you should see:

• ASCII Characters
• Function GUICtrlCreateMenuitem
• Function GUICtrlCreateContextMenu
• Function GUICtrlCreateMenu
• Function TrayCreateItem
• Standard Windows Fonts

Now click on the last one (Standard Windows Fonts), and you will be brought to the page with all the GUI control styles! Weird eh?

[steve8tch]

Just a quick note to say "Well done"with all these extra bits inAut3.

Been using the COM, Control Read and StdOut stuff extensively recently -

absolutely brilliant.

Thanks to the devs and testers!!!

AutIt3...progressing nicely...

[jpm]

26th May 2005 - v3.1.1.40 (beta)

Added : "OnAutoItExit" called on system shutdown or user logoff. (Thanks JoeCool)

Fixed : Doc on Func OnAutoItStart(), Func OnAutoItExit(), @EXITMODE, @EXITCODE (Thanks CyberSlug)

Fixed : OnAutoItExit() call on Fatal error. (Thanks CyberSlug, Valik)

Fixed : Opt("GUIDataSeparatorChar", "\") (Thanks Saunders)

[JoeCool]

26th May 2005 - v3.1.1.40 (beta)

Added :        "OnAutoItExit" called on system shutdown or user logoff. (Thanks JoeCool)

Fixed :          Doc on Func OnAutoItStart(), Func OnAutoItExit(), @EXITMODE, @EXITCODE (Thanks CyberSlug)

Fixed :          OnAutoItExit() call on Fatal error. (Thanks CyberSlug, Valik)

Fixed :          Opt("GUIDataSeparatorChar", "\") (Thanks Saunders)

<{POST_SNAPBACK}>

I installed 3.1.1.40 but I got an unknown macro error when I try to used @EXITMODE ...

onAutoItExit() is correctly called from each scenario :-)

Thanks it's really usuful :-)

[GaryFrost]

I confirm

>Running: (3.1.1.40):C:\Program Files\AutoIt3\beta\autoit3.exe "C:\Documents and Settings\Gary\My Documents\test2.au3" 

C:\Documents and Settings\Gary\My Documents\test2.au3 (5) : ==> Unknown macro.:

MsgBox(0,"","after last statement " & @EXITMODE)

MsgBox(0,"","after last statement " & ^ ERROR

[Lazycat]

OnAutoItExit() call on Fatal error

Just great addition! Now we can made some cleanup if something really wrong occured. Anyway, it's better not permit those situations

[JoeCool]

Just great addition! Now we can made some cleanup if something really wrong occured. Anyway, it's better not permit those situations

<{POST_SNAPBACK}>

So I guest you should also add a new value for the @EXITMODE macro

something like returning 5 if exit with Fatal error .

Edited May 27, 2005 by JoeCool

[jpm]

I installed 3.1.1.40 but I got  an unknown macro error when I try to used @EXITMODE ...

onAutoItExit() is correctly called from each scenario :-)

Thanks it's really usuful :-)

<{POST_SNAPBACK}>

@exitmode can only use inside the OnAutoExit() function.

Where does the error occurs?

[jpm]

So I guest  you should also add a new value for the @EXITMODE macro

something like returning 5 if exit with Fatal error .

<{POST_SNAPBACK}>

We discuss when OnAutoItExit() with others dev and we conclude that Fatal error should not call it.

Try to open a thread on this subject to see if the situation change. Do not use this one which is pretty long now.

[JoeCool]

@exitmode can only use inside the OnAutoExit() function.

Where does the error occurs?

<{POST_SNAPBACK}>

not working in the example (neither in my code)

Opt("OnExitFunc", "endscript")
MsgBox(0,"","first statement")

Func endscript()
    MsgBox(0,"","after last statement " & @EXITMODE)
EndFunc

Edited May 27, 2005 by JoeCool

[jpm]

not working in the example (neither in my code)

Opt("OnExitFunc", "endscript")
MsgBox(0,"","first statement")

Func endscript()
    MsgBox(0,"","after last statement " & @EXITMODE)
EndFunc

<{POST_SNAPBACK}>

My mistake @EXITMODE = @EXITMETHOD

it was the macro choosen by JON not documented I write the doc and the example badly. I will correct in 3.1.1.41 use @EXITMETHOD

[jpm]

27th May 2005 - v3.1.1.41 (beta)

Fixed : Doc on @EXITMETHOD in Func OnAutoItExit(). (Thanks JoeCool)

Fixed : Prevent StringRegExpReplace from replacing on a zero-character match. (Thanks .../Nutster)

26th May 2005 - v3.1.1.40 (beta)

Added : "OnAutoItExit" called on system shutdown or user logoff. (Thanks JoeCool)

Fixed : Doc on Func OnAutoItStart(), Func OnAutoItExit(), @EXITMETHOD, @EXITCODE (Thanks CyberSlug)

Fixed : OnAutoItExit() call on Fatal error. (Thanks CyberSlug, Valik)

Fixed : Opt("GUIDataSeparatorChar", "\") (Thanks Saunders)

Fixed : TreevieItem notify when clicking a second time on the same item. (Thanks .../Holger)

[JoeCool]

We discuss when OnAutoItExit() with others dev and we conclude that Fatal error should not call it.

Try to open a thread on this subject to see if the situation change. Do not use this one which is pretty long now.

<{POST_SNAPBACK}>

I thought reading LazyCat' message and release note of 3.1.1.40 that the func OnAutoItExit() was call on fatal error so I though to have a constant value FatalError into @exitmethod was something logical ;-)

26th May 2005 - v3.1.1.40 (beta)

Added : "OnAutoItExit" called on system shutdown or user logoff. (Thanks JoeCool)

Fixed : Doc on Func OnAutoItStart(), Func OnAutoItExit(), @EXITMETHOD, @EXITCODE (Thanks CyberSlug)

Fixed : OnAutoItExit() call on Fatal error. (Thanks CyberSlug, Valik)

Fixed : Opt("GUIDataSeparatorChar", "\") (Thanks Saunders)

Fixed : TreevieItem notify when clicking a second time on the same item. (Thanks .../Holger)

[MSLx Fanboy]

Is there anyway to use HotKeySet() to use embedded functions that do not require parameters

Example:

HotKeySet("{ESC}", "Exit")

It would be nice to be able to do that, without having to create a function just to send the Exit function

The only way I know how to do this now is:

HotKeySet("{ESC}", "ExitProgram")

Func ExitProgram()
Exit
EndFunc

[therks]

Yes, that is the only way. This isn't really the appropriate place to ask that question either, this thread is supposed to be for beta news.