New SciTE4AutoIt3 available with SciTE v3.3.7

[Jos]

1/22/2014: re-Uploaded a new SciTE4AutoIt3.exe installer with the new SciTE v3.3.7 release.

This version contains a version of AutoIt3Wrapper and SciTEConfig which are recompiled with AutoIt3 v 3.3.10.2 to avoid te hardcrash with Athlon CPU's.

There are a couple of major changes:
- Updated our version of SciTE from 3.3.6 to 3.3.7

- AutoIt3Wrapper will now use  "c:users<userName>AppdataLocalAutoit v3Aut2Exe" as Temp directory.

- Updated syntax files.

Enjoy,
Jos


Addition/Changes/Fixes in the current installer:

expandcollapse popup

--------------------------------------------------------------------------------------------------
01/22/2014
*** Updated AutoIt3Wrapper v2.1.4.5 (Jos)
    - Fixed issue with undecleared variable error when using /Versioning_Commit
    - Recompiled with version 3.3.10.2 because 3.3.10.0 could give a hardcrash.
*** Updated SciTEConfig v1.6.11.1 (Jos)
    - Recompiled with version 3.3.10.2 because 3.3.10.0 could give a hardcrash.

--------------------------------------------------------------------------------------------------
12/29/2013
*** Fixed missing SciTEConfig in SciTE4AutoIt3 installer.
--------------------------------------------------------------------------------------------------
12/28/2013
*** Merged the updates of SciTE v 3.3.7 by Neil Hodgson with our own version of SciTE. (Jos)
*** Updated Production config files to 3.3.10.0
*** Updated AutoIt3Wrapper v2.1.4.0 (Jos)
    - Use "c:\users\<userName>\Appdata\Local\Autoit v3\Aut2Exe" as Temp directory for compiling and resource updating like aut2exe.
    - Fixed issue with Compile both and Pragma(x64,true)
    - Fixed inputfile in case Obfuscator needs to run but is skipped due to unsupported utf format.
    - Fixed UPX selection option to default to N and adding the Directive when checkbox is checked.
*** Updated Obfuscator.exe v1.0.31.1 (Jos)
    - Changed the code to leave #include statements that include a a3x file.
--------------------------------------------------------------------------------------------------
11/14/2013
*** Merged the updates of SciTE v 3.3.6 by Neil Hodgson with our own version of SciTE. (Jos)
    - Added check to avoid double shelling of the script via shortcuts of the tools menu items.
    - Added Properties option to set the default encoding of new files:
        NewFileEncoding=CodePage/UTF8/UTF8BOM/UTF16BE/UTF16LE
    - Fixed issue in AU3 lexer to show the last correctly when the previous line is a commentline, commentblock, Special and Directives.
*** Updated AutoIt3Wrapper v2.1.3.0 (Jos)
    - Fixed issue where a tempfile was left behind when files was checked by au3check and UTF encoded.
    - Added support for the #PRAGMA statement to avoid any conflicts. Warnings are now displayed in the Console output.
    - Added SciTE version to the displayed info in the Console Output.
    - Added #AutoIt3Wrapper_Res_Remove (wraithdu)
    - Added File compression for Resource Files (wraithdu)
        #AutoIt3Wrapper_Res_File_Add=%in%, 10, UNCOMPRESSED
        #AutoIt3Wrapper_Res_File_Add=%in%, -10, COMPRESSED
    - Updated option to change the TempDir in the INI file. Default changed to @UserProfileDir. (wraithdu)
    - Fixed adding /Beta to the Obfuscator line when using the /Beta on the commandline of Autoit3wrapper.
    - Fixed to ensure UPX is ran when needed.
    - Fixed: Allow | in run_before and Run_After directives.
*** Updated Tidy v2.4.0.0 (Jos)
    - Added support for 3.3.9.x changes.
    - Changed default EOF setting to add the CRLF. (End_With_NewLine=1)
    - Fixed removal of spaces for new Var/Func notation
    - Fixed crash caused by Function table load.
*** Updated SciTEConfig v1.6.11.0
    - Updates for Abbrev manager and User Calltip Manager (Melba23)
*** Updated Obfuscator.exe v1.0.31.0 (Jos)
    - Fixed ensure #pragma statements are not stripped.
    - Fixed Regression internal code cleanup done before. The Obfuscation was broken
    - Fixed #include logic for #Include not first checking the Directory where the file containing the include is located.
    - Added check for max 4100 character record len without causing a crash.
*** Added support for personal LUA functions. Look at "PersonalTools.lua" in your @UserProfileDir subdir for details.
*** Updated SciTEJump to the latest version v2.13.103.227 (guinness)
--------------------------------------------------------------------------------------------------

==> ScitillaHistory page containing all SciTE/Scintilla updates.
==> Visit the SciTE4AutoIt3 Download page for the latest versions
==> Check the online documentation for an overview of all extra's you get with this installer.
 

Edited February 14, 2014 by Jos

[mLipok]

thanks

[Iczer]

10x!

but - there are no "PersonalTools.lua" in the AutoIt3SciTELUA subdir

*** Added support for personal LUA functions. Look at "PersonalTools.lua" in the LUA subdir for details.

[Jos]

  On 11/14/2013 at 5:03 PM, Iczer said:

 

10x!

but - there are no "PersonalTools.lua" in the AutoIt3SciTELUA subdir

*** Added support for personal LUA functions. Look at "PersonalTools.lua" in the LUA subdir for details.

 

I need to update that statement because the "PersonalTools.lua" is now located in %USERPROFILE% (@UserProfileDir).

Jos

Edited November 14, 2013 by Jos

[francoiste]

thank you very much!

i just never understood why these type of announcements reside in the forum section "General -> Developer Chat".

the description reads: "General coding talk. Scripting, programming, C++, etc."

there's a much more suitable forum section: "Administration -> Announcements and Site News",

where the description reads: "AutoIt releases and site announcements."

[jaberwacky]

Exactly, or better yet a SciTE4AutoIt3 subforum.

[guinness]

Well Unofficial/Official tools, in that those which are recognised as being endorsed by the Dev/MVP team.

[francoiste]

i noticed the installer uses a new display version as discussed >here:
it is now reading: 13.11.14.16.

great.

however, seeing it for the first time "live" i'm now wondering if some additional optimization could be done.

SciTE4AutoIt3 is to be installed on top of the AutoIt 3.x series.
so maybe the "3" should also be reflected / retained in the installer of SciTE4AutoIt3.

here's one proposal:

!define /date MyDate "%y%m.%d"
!define MyVersion "3.${MyDate}"

this would make it: 3.YYMM.DD

example: 3.1311.14
 

Edited November 21, 2013 by francoiste

[Melba23]

francoiste,

 

  Quote

there's a much more suitable forum section: "Administration -> Announcements and Site News"

Only Admin, Devs and Mods can post in that section, so it is far from "suitable" for hosting a thread such as this.

And, because Jos is far too nice to say so and I have had a bastard of a week, as a relative newcomer why not just appreciate the work that he and others have put into creating the SciTE4Autoit3 package for the whole community rather than continually moaning that it is not exactly as YOU want it?

M23

[Jos]

The project (installer/SciTE/Tidy/Ofuscator/AutoIt3Wrapper/SciTEconfig+ other tools) has been here since its start and it is my personal project for this community.

It did grow into what it is today with its own Sub-web in the website and a lite version on request of Jon for inclusion in the AutoIt3 installer.

The SciTE source is now maintained in Jon's AutoIt3 source library, but the installer and it's tools are still maintained in my environment with me as the sole developer/maintainer.

There are of course a number of contributors, like mentioned in the credits section, which have supplied tools which are included in the Installer.

I would have no issues with a separate forum but is also fine in this place ...  whatever works.

to add on to Melba23's statements:

It is strange to see how people mostly take all the work we/I put in for granted, considering this thread was posted over a week ago and seeing the responses till now.

Guess the only credit these days one can get from doing development is not getting too much complaints after releasing a new version at contain shitload of modifications to accommodate the many changes made in the recent AutoIt3 syntax changes.

This is something I knew already being all my working life in IT, but just wanted to throw it out there.

Jos

[jaberwacky]

Eh, why is it that mentioning something which could make bug reporting/scite4au3 announcements even more organized be a sign of taking all of this for granted?  I for one highly appreciate your work and would not have continued to use AutoIt after all these years if it were not for SciTE4Au3.  But give it three minutes and my post here will be all but forgotten.  Maybe we should have a thread just for expressing our gratitude?

[francoiste]

i'm afraid Melba23 and Jos got it "all wrong":

  On 11/21/2013 at 8:26 PM, Melba23 said:

why not just appreciate the work that he and others have put into creating the SciTE4Autoit3 package for the whole community rather than continually moaning that it is not exactly as YOU want it?

 

  On 11/21/2013 at 9:38 PM, Jos said:

It is strange to see how people mostly take all the work we/I put in for granted, considering this thread was posted over a week ago and seeing the responses till now.

 

there has been absolutely no moaning or complaining.
instead, there is appreciation expressed, indeed.

1)
suggesting an "official announcement" and dedicated sub-forum just translates to:
"wow, this is great stuff! it deserves to be officially announced and officially discussed. what a pity it still treated as something semi-official, only."

2)
suggesting an improved version number is not something an individual wants.
it is an ultra tiny little "contribution" - an idea how to improve it to add value.
caring about the project and making such suggestions could also be seen as appreciation, can't they?

3)
regarding the concern "It is strange (...) considering this thread was posted over a week ago and seeing the responses till now":

a) is it you dislike the contents of the responses so far?
i hope i was able to clarify the positive intent.

also you may have overlooked the previous: "thanks", "10x!" and "thank you very much!".

is it you are disappointed by the little amount of responses?
maybe it's because not many forum members have "found" or "run accross" this thread because it resides in some suboptimal location

--

anyways, just in case you have not been able to read the appreciation between the lines i'll explicitly repeat:

thanks a ton!! you are awesome.
please keep up the good work.
 

Edited November 22, 2013 by francoiste

[mLipok]

  On 11/22/2013 at 5:02 PM, francoiste said:

thanks a ton!! you are awesome.

please keep up the good work.

 

 

With all my heart and all my mind, I agree with the previous speaker.

And although I do not have such skills and abilities as you Dev / Mod / MVP,

if necessary, recommend myself as a volunteer to help.

 

  and of course SciTE4AutoIt3

[francoiste]

some feedback on the 2013-11-14 release and UPX:

• from SciTE invoke the "compile" command
• AutoIt3Wrapper GUI (2.1.3.0) opens
• enable the checkbox "Use UPX"
• click on "compile script"

effect: script is compiled including UPX-compression. good.

however, this setting is not persisted.
it's required to manually add this directive to the source:

#AutoIt3Wrapper_UserUpx=Y

i thought the wrapper GUI would persist all settings by automatically updating the directives in the source?

Edited November 26, 2013 by francoiste

[Jos]

Funny to see that 2 people report this to me today while it has been an issue for a while now since the default changed in AUT2EXE.

Anyway; it is fixed in the current Beta version of AutoIt3Wrapper available in the Beta directory.

Cheers

Jos

ps: Directives are removed in case they reflect the default setting. in this case when #AutoIt3Wrapper_UserUpx is set to N.

Edited November 26, 2013 by Jos

[mLipok]

Is the AutoItWrapper can add a new directive that after you execute Obfuscator.exe, will perform additional changes to the file ... _obfuscated.au3

 

example:

......
......
#EndRegion Run Obfuscator
If $INP_Run_Obfuscator = "y" Then
    _ReplaceScriptLineNumber($ScriptFile_In_Obfuscated)
EndIf
Func _ReplaceScriptLineNumber($hFile)
    Local $sFileContent = FileRead($hFile)
    Local $delim = ' @' & 'ScriptLineNumber'

    Local $aFileContent = StringSplit($sFileContent, $delim, 1)
    Local $sFileOut = ''
    If IsArray($aFileContent) = 1 And $aFileContent[0] > 1 Then
        Local $vFileContentRows = UBound($aFileContent, 1)
        Local $vLineOffset = 1
        For $i = 1 To $vFileContentRows - 2
            StringReplace($aFileContent[$i], @CRLF, @CRLF)
            $vLineOffset += @extended
            $sFileOut &= $aFileContent[$i] & ' ' & $vLineOffset
        Next
        $sFileOut &= $aFileContent[$vFileContentRows - 1]
    Else
        $sFileOut = $sFileContent
    EndIf
    Local $fFileWrite = FileOpen($hFile, 2)
    FileWrite($fFileWrite, $sFileOut)
    FileClose($fFileWrite)
EndFunc   ;==>_ReplaceScriptLineNumber
#Region Compile the script
......
......

 

I added it as you can see in the example, and I did some testing for me works well, except that it would be better if it were a separate directive.

 

Best regards

mlipok

[Jos]

What are you trying to do with that added code you are showing?

I am very reluctant to support a request to make changes to the output source from Obfuscator before the Compilation as a standard feature as that will only create confusion.

Jos

[mLipok]

ok

I understand your approach to this matter.

Is so that can I count on adding new directive, something like RunAfterObfuscator ?

[Jos]

Lets start with defining what it is you want to accomplish.

Jos

[mLipok]

I'm thinking about the possibility of changes in the combined file I mean ...._obfuscated.au3

 

This applies not only need to change the @ScriptLineNumber on the proper line in order to be able to use the line number in the compiled script.

I also wonder at the possibility of tracing the course of execution of the script by determining which function was used, something like a chronology of the use of the function.

 

For this, however, I need to be able to change the above mentioned file.

 

If you wish, I can manually prepare an example showing what I want to achieve.