New SciTE4AutoIt3 available with updated SciTE v3.4.4

[Jos]

There was a recent change for ShowProgress when using F7.

The progressbar isn't shown anymore.

#AutoIt3Wrapper_ShowProgress=N/Y

may be used to alter the behaviour.

And a INI setting

progressbar=1

can do the job, due to the change log.

My question:

What is the full pathname of the user INI file and what is the section name.

Please give me the link to this information.

Thanks

Correct, the /NoStatus parameter was added to F7 as the status is already seen in the SciTE output pane.

The location of the INI files is depending on the SCITE_USERHOME environment variable as described in the Helpfile: SciTE4AutoIt3 File Location

The INI keyword is ShowProgress and section is described in the AutoIt3Wrapper help page.

Jos

[Jos]

Au3Stripper /rsln replaces an incorrect number for @ScriptLineNumber in a function parameter default value.

v14.801.1932.0 currently replaces @ScriptLineNumber in a function parameter default with the line number of the callee code.  It should be the line number of the caller code.  To implement this, it could automatically insert default arguments for all unspecified function arguments and also the line number of the calling code, where the function call occurs.

 

Here is the bug report that I posted for this issue:

https://www.autoitscript.com/trac/autoit/ticket/2867#ticket

 

Thanks Jos for making quality tools for AutoIt development.

The whole intent was to show the line number of the actual included script, not the original source.

The idea is that this gives you the ability to do better debugging on the included code, which is easy to generate with au3stripper.

so. no bug and please only post a bug report when you have some confirmation or at least post a replicator script and what you are expecting as result.

Avoids me to having to do any interpretations of phrases like "callee code".

Jos

[Jos]

Just uploaded a new Beta of SciTE that has the following change:

*** Merged the SciTE v 3.5.0 by Neil Hodgson with our own version of SciTE. (Jos)

    Added  utf8.auto.check which will autodetect UTF8 encoded files without BOM and files containing Highvalue ASCII characters and setting the correct encoding.
        We have set the default to 4 which means that the encoding is set to UTF8 without BOM for any script containing normal ASCII characters.
        #~ Enhance function of auto checking utf8: providing two methods
        #~ utf8.auto.check=1: detect utf8 and add BOM automatically
        #~ utf8.auto.check=2: detect utf8 and do not add BOM
        #~ utf8.auto.check=3: detect ascii high characters and if none found set default encoding to UTF8 and add BOM
        utf8.auto.check=4: detect ascii high characters and if none found set default encoding to UTF8 and do not add BOM

You obviously need to add the utf8.auto.check=4 key yourselves to either SciTEGlobal.properties or your SciTEUser.properties to test this feature.

Jos

Edited August 29, 2014 by Jos

[Exit]

Correct, the /NoStatus parameter was added to F7 as the status is already seen in the SciTE output pane.

The location of the INI files is depending on the SCITE_USERHOME environment variable as described in the Helpfile: SciTE4AutoIt3 File Location

The INI keyword is ShowProgress and section is described in the AutoIt3Wrapper help page.

 

Jos

 

Unfortunately, the ShowProgress keyword is missing in the AutoIt3Wrapper.ini.example file.

[Jos]

 

Unfortunately, the ShowProgress keyword is missing in the AutoIt3Wrapper.ini.example file.

 

Seen that already and found I had an installer issue,  as the source directory does contain it properly.

Jos

[Exit]

Seen that already and found I had an installer issue,  as the source directory does contain it properly.

 

Jos

I had no luck using the AutoIt3Wrapper.ini file.

 

But this setting in my SciTEUser.properties

command.build.$(au3)="$(SciteDefaultHome)\AutoIt3Wrapper\AutoIt3Wrapper.exe" /prod /in "$(FilePath)"

did the trick.

[Jos]

I had no luck using the AutoIt3Wrapper.ini file.

 

But this setting in my SciTEUser.properties

command.build.$(au3)="$(SciteDefaultHome)\AutoIt3Wrapper\AutoIt3Wrapper.exe" /prod /in "$(FilePath)"

did the trick.

Just realised that there is a order of priority. The INI value setting is overridden by the commandline.

Sequence of priority for defining settings/options:

1. #AutoIt3Wrapper DIrectives
2. Scriptfilename.ini
3. Commandline parameters
4. AutoIt3Wrapper.ini

Jos

[CyberMax]

Using the latest scite.exe and SciLexer.dll beta gives me error loading scintilla but replacing SciLexer.dll with an older beta version works fine.

[Melba23]

CyberMax,

Works fine for me.

M23

[CyberMax]

CyberMax,

Works fine for me.

M23

Well, I'm using windows xp, and replacing the SciLexer.dll beta(latest) with an older version, then the error msg no longer appear so I'm not sure what the problem is.

[Jos]

Well, I'm using windows xp, and replacing the SciLexer.dll beta(latest) with an older version, then the error msg no longer appear so I'm not sure what the problem is.

Which WinXP version are you using?

[CyberMax]

I'm using windows xp sp2 32bit.

[BrewManNH]

I'm using windows xp sp2 32bit.

Why? SP3 has been out for years now, has been tested and works as well as XP can work. 

[Jos]

The current beta versions of Autoit3 and scite have a mimimum requirement of xp sp3.

Jos

[CyberMax]

Why? SP3 has been out for years now, has been tested and works as well as XP can work. 

 

I setup the system base on the minimum os on the deployment system.

The current beta versions of Autoit3 and scite have a mimimum requirement of xp sp3.

Jos

If its because of xp sp2 then I'll stick with the current release version instead of beta, or if I want use the beta, I'll use the previous beta scite dll then.

[BrewManNH]

I setup the system base on the minimum os on the deployment system.

Not a clue what that's supposed to mean.

[mLipok]

When I try to use the latest beta

SciTE.exe 02-Sep-2014 19:52  871K

then I get this message:

 

OK
Nie można uruchomić programu, ponieważ na komputerze nie znaleziono MSVCR120.dll. Spróbuj ponownie zainstalować program, aby naprawić ten problem.

 

here is GOOGLE TRANSLATION:

 

OK
Program can not start because the computer was not found MSVCR120.dll. Try reinstalling the program to fix this problem.

 

and the second message:

 

OK
The Scintilla DLL could not be loaded.  SciTE will now close

 

EDIT:

here is solution: Visual C++ Redistributable Packages for Visual Studio 2013

Edited September 3, 2014 by mLipok

[Jos]

Just checked the project and have recompiled them both and uploaded them.

Could you try these to see if that works as I am not sure if that fixed it as they didn't change in size, but I don't get the error so can't test.

Jos

[mLipok]

The same issue.

[Jos]

What OS and SP level are you using?