New SciTE4AutoIt3 available with SciTE v3.4.1

[Jos]

Have you specified the /MO option? 

In that case it will indeed only do a MergeOnly now as this is what that option really should do.

[TechCoder]

#Au3Stripper_Parameters=/mo /soi

[Jos]

stripped file using the download beta = 19338 lines

stripped file using SciTE compile = 188 lines

Interesting note (hope it helps)

- stops at 20 errors

- stops right after the call to the main function 

- the last error being 'undefined function'

program runs fine with 'Go' - no errors

uses mostly standard UDFs plus a couple from the forum and two I built.  I can zip them all up and send them to you if needed.

 

The au3stripper in the installer has a bug when /MO together with other options are used.

So what is it you want to do?  MergeOnly of Stripping?

Edited April 27, 2014 by Jos

[TechCoder]

 

The au3stripper in the installer has a bug when /MO together with other options are used.

sure does........

still showed up until (not positive where exactly, but the steps are simple in case someone else comes across this);

1. removed the other option (in my case /soi)

2. Deleted the old 'merged' file

3. closed the main file

4. reopened the main file and compiled

The merge_stripped file runs now.  And compiles/runs.

Thanks!

[Inververs]

If output console has long string, than scite crashed when used F4 (Next message).

For example this script crash scite.

$line = '+++ 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
ConsoleWrite($line & @CRLF)

Run Script, than press F4.

Windows 7x86  Scite 3.4.1

[Jos]

This issue is present in the original SciTE supplied by Neil Hodgson.

Will update the source in SciTEBuffers.cxx to limit the max line length in SciTEBuffers.cxx to stay within the MAX_PATH lenght.

Jos

[Jos]

This how the original code works. It goes one indent back on an EndIf;Wend;EndFunc  etc.

Not sure how easy it is to fix this as the LUA code is not able to keep the Indent levels.

Suggestions are welcome.

Jos

I have totally re-written the logic used in AutoItIndentFix.lua to fix the auto indent issues for:

• Single If line.
• Case line
• EndSwitch/EndSelect (and now all End??? statements)

This should be a better/easier base code to make corrections.

It also supports correcting the Indents when the caret is in-front of the Keyword.

Please try it and tell me if this works better or whether there are other issues now that weren't there before.

Jos

Edited April 30, 2014 by Jos

[FaridAgl]

Func SetWindowTheme($hWnd, $sSubAppName)
    DllCall("uxtheme.dll", "long", "SetWindowTheme", _
            "HWND", $hWnd, _
            "wstr", $sSubAppName, _
            "ptr", 0)
EndFunc

Pressing Enter after EndFunc still has the previous issue, also it says:

...am Files (x86)\AutoIt3\SciTE\Lua\AutoItIndentFix.lua:63: attempt to call method 'FirstWord' (a nil value)

[Jos]

Func SetWindowTheme($hWnd, $sSubAppName)
    DllCall("uxtheme.dll", "long", "SetWindowTheme", _
            "HWND", $hWnd, _
            "wstr", $sSubAppName, _
            "ptr", 0)
EndFunc

Pressing Enter after EndFunc still has the previous issue, also it says:

...am Files (x86)\AutoIt3\SciTE\Lua\AutoItIndentFix.lua:63: attempt to call method 'FirstWord' (a nil value)

Forgot that I also added a function to common.lua which is now also available in the Beta directory.

Just copy that too.

Jos

[mLipok]

I have a question about CallTips

When I type:

WinActive(

then CallTip appear

and now I type again a bracket

WinActive((

QUESTION:

Can you make that in case of re-entering the "bracket", also disappeared CallTip ?

[mLipok]

What are the practical differences in these two files:

au3.user.calltips.api

au3.UserUdfs.properties

I mean the result of their actions, not the structure.

[Jos]

I have a question about CallTips

 

When I type:

WinActive(

then CallTip appear

 

and now I type again a bracket

WinActive((

QUESTION:

Can you make that in case of re-entering the "bracket", also disappeared CallTip ?

The Idea is that the CallTip will be displayed as long as you are within the Function.

Jos

[Jos]

What are the practical differences in these two files:

au3.user.calltips.api

au3.UserUdfs.properties

 

I mean the result of their actions, not the structure.

 

Thought you were that one guy that actually read the SciTE4AutoIt3 helpfile.

 

 

AutoComplete

Installing SciTE adds a special file to the user profile "au3.UserUdfs.properties" - this stores the function names from the UDFs to add to the AutoComplete combos.  The contents look like this:

au3.keywords.user.udfs=_function1 _function2 _function3       

     _function4 _function5 _function6 _function7

Note that the entries are all in lowercase and all lines other than the first begin with a TAB character.  You can open this file via the <Options> menu in SciTE.

CallTips

Another special file added to the user profile is "au3.user.calltips.api" - this stores the CallTip data for each function.  The data is stored in a single line for each function like this:         _Function($param1, $param2, $param3) Explanation of function (Requires: #Include UDF.au3) Of course you need to change the Function, $param and UDF words to the correct values for the UDF function you want to include. Again you can open this file via the <Options> menu in SciTE.

Now looking at this I think the author of this specific section has made a mistake and this the way it works:

• The API file is used for displaying in AutoComplete and CallTips information
• The Properties file for the Lexer definitions (Color Coding) of the UserUDF's.

Will make an update to this section of the helpfile.

Jos

Edited May 2, 2014 by Jos

[mLipok]

Thought you were that one guy that actually read the SciTE4AutoIt3 helpfile.

.... .........

 

Now looking at this I think the author of this specific section has made a mistake and this is the way it works:

• The API file is used for displaying in AutoComplete and CallTips information
• The Properties file for the Lexer definitions (Color Coding) of the UserUDF's.

Will make an update to this section of the helpfile.

Jos

 

So now I know what did not fit me in the description

Edited May 2, 2014 by Jos

[mLipok]

can I set my own color for my UDF ?

[mLipok]

I am in the process of writing a UDF file for:

Debenu Quick Pdf Library

I'm trying to do syntax highlighting.

 

Examples I show in the attached files.
An example is quite unusual so I would ask for some opinions, tips, comments, veryfication.

Here are Function Reference for these two examples from attached files

http://www.debenu.com/docs/pdf_library_reference/GetPageText.php

http://www.debenu.com/docs/pdf_library_reference/DrawBox.php

SciTE.zip

Edited May 3, 2014 by mLipok

[mLipok]

btw.

I wonder if calltips guide can be displayed in three lines, rather than as is currently the case in two. Of course, provided that calltips guide consists of three parts.
Because as you can see the second example (GetPageText) shows the drawback of the current solution.

The following examples shows the effect what I would like to achieve:

DrawBox(Left, Top, Width, Height, DrawOptions)
  Draw a rectangle on the selected page.
    (may be required: #include "QuickPDF.au3")

GetPageText(ExtractOptions)
  This function provides two different methods for extracting text from the selected page, and presents the results in a variety of formats.
    (may be required: #include "QuickPDF.au3")

mLipok

Edited May 3, 2014 by mLipok

[mLipok]

It occurred to me one more question:
how easy it is to use a new file, the user calltips guide (for Example au3.QPdf.calltips.api) without removing the existing au3.user.calltips.api.

Is there some mechanism that causes you copy a new file, it starts working right away?

So that the creator of the UDF file could easily deliver new definition files for calltips guide?

[Jos]

Jeez .. you've been busy ..

can I set my own color for my UDF ?

The UDF's added to au3.UserUdfs.properties will get the standard UDF Color defined for:

style.au3.15=fore:#0080FF,italics,bold,back:#F0F4F9

Not sure what you are asking with the posted project.

There is no option for 3 lines in the CallTips as far I I know.

To add your own API file just add it to the end of this line:

api.$(au3)=$(SciteDefaultHome)\api\au3.api;$(SciteDefaultHome)\api\au3.autoit3wrapper.api;$(SciteUserHome)\au3.user.calltips.api

You also need to ensure this is done in the correct file or else with the next upgrade you will loose your change.

The properties files need to be added in SciTEUser.Properties with in Import like:

import au3.UserUdfs

Jos

Edited May 3, 2014 by Jos

[MHz]

btw.

I wonder if calltips guide can be displayed in three lines, rather than as is currently the case in two. Of course, provided that calltips guide consists of three parts.

...

Perhaps you have forgotten as you left a like in this post >here about the use of multiple calltip lines > 2 lines. The feature has been available since Scite 3.04.

Set calltip.*.use.escapes=1 in Scites properties file.

Use C like escapes in the calltip definitions i.e. n for new line, t for tab etc.

So a calltip definition would be like

DrawBox ( Left, Top, Width, Height, DrawOptions ) Draw a rectangle on the selected page.\n\t (may be required: #include "QuickPDF.au3")

and will popup a calltip when invoked as 3 lines.