New SciTE4AutoIt3 available with SciTE v3.30

[Jos]

It might be worthwhile to have Jon mention this and a link to the beta section in his AutoIt Beta announcements.

Yea, or I could also decide to publish the updates now ....  options... options ... choices ...choices

Edited August 16, 2013 by Jos

[guinness]

Yea, or I could also decide to publish the updates now ....  options... options ... choices ...choices

So long as there is a release after the next version of AutoIt is published, then fine by me. I would like to release the next SciTE Jump using AutoIt v3.3.10.0 that's why.

[Jos]

I can also publish an Beta installer that contains all the updates made till now and support the Beta AutoIt3 version.

Jos

[Iczer]

Hope it's a right topic to ask :
when you type some func($param_1, $param_1, $param_1 ...) in SciTE, after typing every ","  you get pop up (calltips?), but in case :

WinGetTitle()
StringRegExp()
StringRegExpReplace()

and maybe others, after typing comma pop up's disappear

and another - since it's a pain - can some option like "GenerateUnDeclaredVarsList" be added to the SciTE Tools menu ?

[mLipok]

You can use this directive to indicate UnDeclaredVars

#AutoIt3Wrapper_Au3Check_Parameters=-d -w 1 -w 2 -w 3 -w- 4 -w 5 -w 6 -w- 7

[mLipok]

do you type:  WinGetTitle(  and wait a second or WinGetTitle() and waiting ........ ?

[guinness]

If you have "," in a string then this can happen sometimes.

[mLipok]

You mean something like this

WinGetTitle('test1,',
WinGetTitle('test1,test2',

Strange: Only the first example has this problem

[Iczer]

do you type:  WinGetTitle(  and wait a second or WinGetTitle() and waiting ........ ?

i try to replace commas in already typed func($param_1, $param_2,  $param_3)  and  pop up not alwais appear

 

If you have "," in a string then this can happen sometimes.

thanks, it seems the case

mlipok

Posted 17 minutes ago

You can use this directive to indicate UnDeclaredVars

#AutoIt3Wrapper_Au3Check_Parameters=-d -w 1 -w 2 -w 3 -w- 4 -w 5 -w 6 -w- 7

i know, but my laziness tell me to auto it

[mLipok]

i know, but my laziness tell me to auto it

 

For me, this method is simpler, compile or run by F5, and instantly see where there are any errors. Then just press F4 and SciTE has moved in the right place, so you can immediately solve the problem.

Edited August 24, 2013 by mlipok

[mLipok]

for this example

WinMenuSelectItem('title1,','text','Item')

try to delete this comma ','text'  and press the comma key again - calltips does not appear

try to delete this comma ,'Item'  and press the comma key again - calltips appear

try to add new parameter after 'Item' by pressing the comma - calltips appear

In summary, CALLTIP does not appear if the previous parameter of type STRING, ends with a comma, like 'Title1,' in example

Edited August 24, 2013 by mlipok

[Jos]

and another - since it's a pain - can some option like "GenerateUnDeclaredVarsList" be added to the SciTE Tools menu ?

 

2 options:

1 is what mlipok stated to have au3check report the errors.

2. Have Tidy generate a report about your script. Par of the report is the location where a variable is defined and used.

Both require the full version of SciTE4AutoIt3 that comes as an extra installer.

Jos

[mLipok]

for this example

WinMenuSelectItem('title1,','text','Item')

try to delete this comma ','text'  and press the comma key again - calltips does not appear

try to delete this comma ,'Item'  and press the comma key again - calltips appear

try to add new parameter after 'Item' by pressing the comma - calltips appear

In summary, CALLTIP does not appear if the previous parameter of type STRING, ends with a comma, like 'Title1,' in example

 

@Jos

Is this error due to the operation of SciTE (Scintilla), or whether it is in terms of your ability to influence SciTE4AutoIT.

[Jos]

@Jos

Is this error due to the operation of SciTE (Scintilla), or whether it is in terms of your ability to influence SciTE4AutoIT.

This has been in the LUA script logic since we implemented the automatic popup of the calltips.

Reason is that the Style of the type character isn't known in the OnChar() LUA call.

I have been playing with this today and found a way around this problem.

There is no easy solution for highlighted keyword in the CallTip as SciTE simply counts comma's, so that remains.

Give the Beta version of "AutoItAutoComplete.lua" a test to see if that fixes it.

Jos

[mLipok]

works like a charm

[mLipok]

look in scite

MENU: Tools/Debug ...

MENU: Tools/Trace: ...

MENU: Tools/Debug Trace: ...

 

for example

MENU: Tools/Trace: Add Func trace line

 

this tool EDIT: are not created for  Create trace for Function names

 

 

Func _test($test = 1)
    ConsoleWrite('@@ (45) :(' & @MIN & ':' & @SEC & ') _test()' & @CR) ;### Function Trace
;~ ...
;~ ...
;~ ...
EndFunc ;==>_test

 

Can this function do that something:

Func _test($test = 1): START
    ConsoleWrite('@@ (45) :(' & @MIN & ':' & @SEC & ') _test():START' & @CR) ;### Function Trace : START
;~  ...
;~  ...
;~  ...
    ConsoleWrite('@@ (50) :(' & @MIN & ':' & @SEC & ') _test():END' & @CR) ;### Function Trace : END
EndFunc   ;==>_test

but If the last line in a function begins with "Return"

Func _test($test = 1): START
    ConsoleWrite('@@ (45) :(' & @MIN & ':' & @SEC & ') _test():START' & @CR) ;### Function Trace : START
;~  ...
;~  ...
;~  ...
    ConsoleWrite('@@ (50) :(' & @MIN & ':' & @SEC & ') _test():END' & @CR) ;### Function Trace : END
    Return $var
EndFunc   ;==>_test

Edited September 17, 2013 by mlipok

[Mat]

No, because the return doesn't have to be on the last line. The best way to do that would be to add a wrapper function like:

Func _test($test = 1)
    ConsoleWrite('@@ (45) :(' & @MIN & ':' & @SEC & ') _test():START' & @CR) ;### Function Trace : START

    Local $ret = __WRAPPED__test($test)
    Local $error = @error, $extended = @extended

    ConsoleWrite('@@ (50) :(' & @MIN & ':' & @SEC & ') _test():END' & @CR) ;### Function Trace : END
    Return SetError($error, $extended, $ret)
EndFunc

Func __WRAPPED__test($test = 1)
;~  ...
;~  ...
;~  ...
    Return SetError(1, 42, $test)
EndFunc   ;==>_test

[mLipok]

It depends on the "style of programming."

I always try to avoid the use of "Return", in the middle of a function.

 

 

Even if you do not have this habit, it usually functions are completed in the last line.

[jaberwacky]

Mat.  Would you mind explaining what mlipok was trying to describe?  Also, maybe a side note on HOW you knew that?

[BrewManNH]

It depends on the "style of programming."

I always try to avoid the use of "Return", in the middle of a function.

 

 

Even if you do not have this habit, it usually functions are completed in the last line.

That's far from true, what happens on an error? It jumps out of the function somewhere that's usually no where near the last line, sometimes it's within the first few lines on most of the UDFs included with AutoIt. I think the current process, where it tells you it is entering a function, should tell the experienced porgrammer wehre to start looking if things go wrong.