New SciTE4AutoIt3 available with SciTE v2.27

[GEOSoft]

That's probably the problem. I'm in W7 right now and the same issue is there so I'll play with it here first and then go back to Vista. Funny it worked for some files yesterday but none today.

[GEOSoft]

Thanks @ProgAndy

That was the problem alright and it shall never again be an issue. I just added a function to my Fix_Scite script to handle it.

[Emiel Wieldraaijer]

@Jos,

Could you tell me what #AutoIt3Wrapper_res_compatibility does ? i looked in the online documentation but the information of the wrapper isn't updated yet with all the changes.

Thnx

Emiel

[Jos]

@Jos,

Could you tell me what #AutoIt3Wrapper_res_compatibility does ? i looked in the online documentation but the information of the wrapper isn't updated yet with all the changes.

Thnx

Emiel

This is the thread that triggered this option:

Vista has a popup box about compatibility or something and this can be avoided by this.

This MSDN page explains what is changed in the registry.

Jos

[Jos]

Uploaded the merged SciTE 2.28 and Scintilla version of Scite4AutoIt3 to the SciTE Beta directory.

Have a play when you want.

Jos

[wraithdu]

I found bug in the new AutoIt3Wrapper. I surrounds the new OutFile_X64 directive. It seems when compiling as x64 and not specifying this directive, that it is derived from the infile instead of the normal OutFile directive. That kinda breaks the whole OutFile directive. Here's the concerned code from line 534:

; Set default for x64 exe
If $ScriptFile_Out_x64 = "" Then
    If $INP_Compile_Both = 'y' Then
        If $ScriptFile_Out_Type <> "" Then
            $ScriptFile_Out_x64 = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '_x64.' & $ScriptFile_Out_Type
        Else
            $ScriptFile_Out_x64 = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '_x64.exe'
        EndIf
    Else
        If $ScriptFile_Out_Type <> "" Then
            $ScriptFile_Out_x64 = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.' & $ScriptFile_Out_Type
        Else
            $ScriptFile_Out_x64 = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.exe'
        EndIf
    EndIf
EndIf

I think maybe $ScriptFile_In just needs to change to $ScriptFile_Out... but I haven't analyzed all the path and outfile code to be sure. Edited August 7, 2011 by wraithdu

[wraithdu]

There's some other outfile code in the Aut2Exe section and obfuscator sections as well (not sure if that needs to be reviewed). But I also noticed that the OutFile_x86 directive is in there, but doesn't do anything at all. It only exists as a global variable and a preprocessor directive, maybe just not implemented yet?

[Jos]

There's some other outfile code in the Aut2Exe section and obfuscator sections as well (not sure if that needs to be reviewed). But I also noticed that the OutFile_x86 directive is in there, but doesn't do anything at all. It only exists as a global variable and a preprocessor directive, maybe just not implemented yet?

I know it is still in there but I changed my mind and kept the original #AutoIt3Wrapper_Outfile directive for x86. Just ignore it.

Will have a look what I did with the x64 outfile logic, but it indeed looks like I did something different from what I wrote in the Post about it.

Jos

Edited August 7, 2011 by Jos

[Melba23]

Jos,

A couple of niggles with the beta au3.properties file. It would not pick up the beta install on my machine.

- It had the AutoIt dir set to the x64 folder:

autoit3dir=C:\Program Files (x86)\AutoIt3

- It was missing the "\beta" in the "beta run" command":

bcommand.0="$(SciteDefaultHome)\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /beta /ErrorStdOut /in "$(FilePath)" /autoit3dir "$(autoit3dir)" /UserParams $(1) $(2) $(3) $(4)

Once I changed those and the BETA_AUTOIT flag, I got the beta run/compile options back.

M23

[Jos]

I found bug in the new AutoIt3Wrapper. I surrounds the new OutFile_X64 directive. It seems when compiling as x64 and not specifying this directive, that it is derived from the infile instead of the normal OutFile directive. That kinda breaks the whole OutFile directive. Here's the concerned code from line 534:

; Set default for x64 exe
If $ScriptFile_Out_x64 = "" Then
    If $INP_Compile_Both = 'y' Then
        If $ScriptFile_Out_Type <> "" Then
            $ScriptFile_Out_x64 = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '_x64.' & $ScriptFile_Out_Type
        Else
            $ScriptFile_Out_x64 = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '_x64.exe'
        EndIf
    Else
        If $ScriptFile_Out_Type <> "" Then
            $ScriptFile_Out_x64 = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.' & $ScriptFile_Out_Type
        Else
            $ScriptFile_Out_x64 = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.exe'
        EndIf
    EndIf
EndIf

I think maybe $ScriptFile_In just needs to change to $ScriptFile_Out... but I haven't analyzed all the path and outfile code to be sure.

Thinking about this I guess this should really do it and make it simpler:

;Set default for x86 exe
If $ScriptFile_Out = "" Then
    If $ScriptFile_Out_Type <> "" Then
        $ScriptFile_Out = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.' & $ScriptFile_Out_Type
    Else
        $ScriptFile_Out = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.exe'
    EndIf
EndIf
$ScriptFile_Out = _PathFull($ScriptFile_Out)
; fix _PathFull() problem
If StringLeft($ScriptFile_Out, 3) = "\\\" Then $ScriptFile_Out = StringMid($ScriptFile_Out, 2)
; Set default for x64 exe
If $ScriptFile_Out_x64 = "" Then
    $ScriptFile_Out_x64 = StringReplace($ScriptFile_Out, ".", "_x64.", -1)
EndIf

Will do some more testing and then upload it into the Beta directory.

Jos

[Jos]

Jos,

A couple of niggles with the beta au3.properties file. It would not pick up the beta install on my machine.

- It had the AutoIt dir set to the x64 folder:

autoit3dir=C:\Program Files (x86)\AutoIt3

- It was missing the "\beta" in the "beta run" command":

bcommand.0="$(SciteDefaultHome)\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /beta /ErrorStdOut /in "$(FilePath)" /autoit3dir "$(autoit3dir)" /UserParams $(1) $(2) $(3) $(4)

Once I changed those and the BETA_AUTOIT flag, I got the beta run/compile options back.

M23

The proper directory is set in the au3.properties by UpdateDefs.exe, which is ran at the end of the installer process.

Just run SciTEConfig and swap the config between Prod<->Beta and you will see it is updated.

You do not need \Beta as the is added by autoit3wrapper already.

Jos

Edited August 7, 2011 by Jos

[Melba23]

Jos,

I had just put the new file directly into the properties folders. Can you run UpdateDefs.exe manually after having done this?

M23

[Jos]

Jos,

I had just put the new file directly into the properties folders. Can you run UpdateDefs.exe manually after having done this?

M23

SciTEConfig runs it for you when you change between Beta and Prod definitions, or just do:

UpdateDefs.exe /s latest

Jos

[Melba23]

Jos,

SciTEConfig runs it for you when you change between Beta and Prod definitions

Aha, I had run SciTEConfig but had not swapped the defs.

Dank je wel!

M23

[wraithdu]

Thinking about this I guess this should really do it and make it simpler:

;Set default for x86 exe
If $ScriptFile_Out = "" Then
    If $ScriptFile_Out_Type <> "" Then
        $ScriptFile_Out = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.' & $ScriptFile_Out_Type
    Else
        $ScriptFile_Out = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.exe'
    EndIf
EndIf
$ScriptFile_Out = _PathFull($ScriptFile_Out)
; fix _PathFull() problem
If StringLeft($ScriptFile_Out, 3) = "\\\" Then $ScriptFile_Out = StringMid($ScriptFile_Out, 2)
; Set default for x64 exe
If $ScriptFile_Out_x64 = "" Then
    $ScriptFile_Out_x64 = StringReplace($ScriptFile_Out, ".", "_x64.", -1)
EndIf

Will do some more testing and then upload it into the Beta directory.

Jos

Not quite. Unless I have Compile_Both set, I don't want AutoIt3Wrapper changing my OutFile name just because it is compiling an x64 exe. So I think adding that test in there for the addition of '_x64' to the outfile name would make more sense.

[wraithdu]

Oh, and you still need to call _PathFull (and the \\\ fix) for the x64 outfile in case it is given as a directive.

Here's what I ended up with:

;Set default for x86 exe
If $ScriptFile_Out = "" Then
    If $ScriptFile_Out_Type <> "" Then
        $ScriptFile_Out = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.' & $ScriptFile_Out_Type
    Else
        $ScriptFile_Out = StringTrimRight($ScriptFile_In, StringLen($ScriptFile_In_Ext)) & '.exe'
    EndIf
EndIf
$ScriptFile_Out = _PathFull($ScriptFile_Out)
; fix _PathFull() problem
If StringLeft($ScriptFile_Out, 3) = "\\\" Then $ScriptFile_Out = StringMid($ScriptFile_Out, 2)
; Set default for x64 exe
If $ScriptFile_Out_x64 = "" Then
    If $INP_Compile_Both = "y" Then
        $ScriptFile_Out_x64 = StringReplace($ScriptFile_Out, ".", "_x64.", -1)
    Else
        $ScriptFile_Out_x64 = $ScriptFile_Out
    EndIf
EndIf
$ScriptFile_Out_x64 = _PathFull($ScriptFile_Out_x64)
;
; fix _PAthFull() problem
If StringLeft($ScriptFile_Out_x64, 3) = "\\\" Then $ScriptFile_Out_x64 = StringMid($ScriptFile_Out_x64, 2)
;If $INP_Icon <> "" Then $INP_Icon = _PathFull($INP_Icon)
; save current workdir for later use

Edited August 7, 2011 by wraithdu

[Jos]

Oh, and you still need to call _PathFull (and the \\\ fix) for the x64 outfile in case it is given as a directive.

True, I considered the _FullPath() and Fix being done in the X86 name but that obviously is only the case when the X64 outfile isn't specified.

Thanks

Jos

[Emiel Wieldraaijer]

This is the thread that triggered this option:

Vista has a popup box about compatibility or something and this can be avoided by this.

This MSDN page explains what is changed in the registry.

Jos

Thanks Jos

Edited August 13, 2011 by Emiel Wieldraaijer

[Richard Robertson]

Is it possible to change the directory that SciTE stores the user files? I don't want them just sitting in my user directory.

[MvGulik]

On Windows, the global properties file is located in the directory of the executable. The user properties file is looked for in the user profile directory as set in the USERPROFILE environment variable, or in the directory of the executable if USERPROFILE is not set. For GTK+ the user properties file is found in the user's home directory and the global properties in a directory set at build time - normally /usr/share/scite. If the "SciTE_HOME" environment variable is set on either Windows or GTK+ then it is where both the global and user properties files are found.

Yes?

The alternative ... (import) is probably not what your looking for.