27 November 2019: Uploaded a new SciTE4AutoIt3.exe v19.1127.1402.0 installer.

[argumentum]

The feature that updates Global Const $VERSION = "" in the compilation to the #AutoIt3Wrapper_Res_Fileversion value, is so cool.
It was in version 18.x.x.x but never documented. ( meaning I did not find it )
I just saw it in 19.x.x.x ( while adding "my touches**" to it ).

**is a bunch of none standard, useless for general distribution, tweaks

[Jos]

6 hours ago, argumentum said:

there is this line:
__ConsoleWrite('+>' & @HOUR & ':' & @MIN & ':' & @SEC & ' Starting AutoIt3Wrapper (' & $VERSION & '}')
and every time is see it is like, "now that's wrong", every time I see it. Is torture for my personality type !  

So you want the left bracket also changed to a curly bracket?  

5 hours ago, argumentum said:

The feature that updates Global Const $VERSION = "" in the compilation to the #AutoIt3Wrapper_Res_Fileversion value, is so cool.
It was in version 18.x.x.x but never documented. ( meaning I did not find it )

That isn't a feature but rather an internal solution to update the version of AutoIt3Wrapper after I made all AutoIt3 utility scripts run with AutoIt3.exe in stead of using a compiled version due to a constant stream of false positives on the compiled scripts. Before that it use to retrieve the version from the compiled PE version header.

Jos

Edited June 14, 2020 by Jos

[argumentum]

I saw that the top part of the new beta is heavily changed as is there is never going to be a compiled version anymore. And that conclusion leads to understand that the internal Global Const update in Update_Version() is also now without a purpose and bound to be removed.
It may very well be a feature, since like it or not, some users may have used it as such. I too use the PE to get the FileVersion of the compilation but having the $VERSION in the *_stripped.au3 can be useful to have when using /MO to match the error line to the script that got compiled ( if the user saved the file somewhere** and not just overwrite every time ).

So after all this rambling, my question is: are you gonna leave it as is, or remove it ?. ***

** I wrote a BackupScript.au3 that takes care of all that, so it may make the question, kind of non-sense.
*** If it's here to stay then I'll count on it while coding, otherwise forget the discovery.

[Jos]

38 minutes ago, argumentum said:

And that conclusion leads to understand that the internal Global Const update in Update_Version() is also now without a purpose and bound to be removed.

Of course not ...  it was added for the shear fact I stopped compiling, thus using "#AutoIt3Wrapper_Res_Fileversion="  had no purpose anymore!

So yes, I guess you can see it as an Feature as well in that respect.  

EDIT: I did restore a couple of directives as these are (of course) needed for the versioning and versionnumber. 

 

Edited June 14, 2020 by Jos

[argumentum]

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_Version=Prod
#AutoIt3Wrapper_Run_After=%OUT%
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****
MsgBox(262144, @ScriptName, "@AutoItVersion: " & @AutoItVersion, 30)

I don't generally use the Prod/Beta selection in the wrapper but using it, I found that the selection in the RadioButton does not matter as it obeys #AutoIt3Wrapper_Version= only ( that does update accordingly ).
To test, compile as one, and alternate between Prod/Beta to corroborate the finding.

[Jos]

You mean that the directive is updated when you change it in the GUI (Ctrl+F7) but it still compiles with its previous setting?
It only works when you run it the second time right now.

Jos

[argumentum]

1 minute ago, Jos said:

It only works when you run it the second time right now.

Yes. And when one is coding "beta mode" or "production mode", one is very unlikely to be constantly alternating back and forth anyway.

[Jos]

I never use that directive myself either ....   but it should be fixed again in the current Beta.  

Jos

[Purity8]

  

About a month ago, I wrote about Chinese Unicode characters:

On 5/21/2020 at 7:54 AM, Purity8 said:

Console doesn't seem to support Chinese characters.  I've set everything to UTF-8 encoding beforehand, so everything else displays Chinese characters normally. I learned this from using Notepad2.

When writing to console:

Global Const $sVar = 王

ConsoleWrite("sVar : " & $sVar)

In the console,  sVar will appear as question mark (?).

Exceptions are Msg & Input boxes. These display Chinese normally.

Then we found out:

On 5/21/2020 at 8:04 AM, wyf said:

The strange phenomenon occurs when the path string or file name has Chinese characters.

This was occurring in AutoIt3Wrapper 19.1127.1402.5 for Chinese Unicode characters.

The orange line states : "Main script copied to temp file because of Unicode characters in one of the filenames: test.au3".

 

I have upgraded to the beta version 19.1127.1402.9.

+>10:40:52 Starting AutoIt3Wrapper (19.1127.1402.9) from:SciTE.exe (4.2.0.0)

However, it remains the same. Unicode still displays as question mark (?) in the output console.

[Jos]

1 hour ago, Purity8 said:

However, it remains the same. Unicode still displays as question mark (?) in the output console.

That is an different topic as the other issue had to do with doublebyte characters in the filename or path and wasn't about the console STDOUT. There are multiple discussions on console output in the forum, so please have a look at those first.

Jos

Edited June 17, 2020 by Jos

[wyf]

13 hours ago, Purity8 said:

  

About a month ago, I wrote about Chinese Unicode characters:

Then we found out:

This was occurring in AutoIt3Wrapper 19.1127.1402.5 for Chinese Unicode characters.

Your AutoIt3 may not be the Chinese version downloaded domestically? Open SciTEGlobal.properties, find "output.code.page=0",

if this is the case, open SciTEUser.properties and add "output.code.page=936" in the last line .

Look at the console display again. If it works, it is recommended to add 2 more lines in SciTEUser.properties: code.page=936 and character.set=134

Edited June 18, 2020 by wyf

[mLipok]

On 5/27/2020 at 5:39 PM, mLipok said:

Works much better....
Will keep an eye on it.
 

I found one issue.

#include '..\Console.au3'

gives:

Quote

!->Includefile '..\Console.au3' not found.

this problem not occurs in this case:

#include "..\Console.au3"

so I think that AutoIt3Wrapper.au3 (19.1127.1402.9) is not properly works in case when single qoutes are used.

 

Edited July 1, 2020 by mLipok

[Jos]

Try current Beta which should have a fix for that.  

[mLipok]

at first glance, confirmed as fixed

[mLipok]

in one of my project I get:

!>13:36:39 AutoIt3.exe ended.rc:-1073741819
+>13:36:39 AutoIt3Wrapper Finished.
>Exit code: 3221225477    Time: 15.52

my questions:
Is that normal that in this case AutoIt3Wrapper ends with different exit code than returned by AutoIt.exe  ?

What mean exit code == 3221225477 ?

 

Edited August 10, 2020 by mLipok

[Jos]

Try running AutoIt3 directly from SciTE and see what SciTE tell you the returncode is, but that is what AutoIt3Wrapper gets:

$ExitCode = _ProcessExitCode($Pid, $Handle)
        _ProcessCloseHandle($Handle)
        Write_RC_Console_Msg("AutoIt3.exe ended.", $ExitCode)

These high numbers often mean there was a hardcrash.   

Jos

[mLipok]

hm... there was upgrade with this ActiveX component which I used, after using current version the problem is gone.
 

edit:
but your answer was valuable, thanks @Jos

Edited August 10, 2020 by mLipok

[Zedna]

This new Scite4AutoIt3 editor (latest beta) opens not maximized.

Previous versions are OK, ie. maximized.

Can this be somehow configured/overriden? Or is this some bug in this new version?

Thanks.

 

EDIT:

AutoIt (3.3.14.5)+Scite4AutoIt3(latest ZIP) unpacked from their ZIP packages to folder

C:\Program Files (x86)\AutoIt33145\

and run by command

C:\Program Files (x86)\AutoIt33145\SciTe\SciTE.exe

from file manager with parameter "full path to selected AU3 script" from "Start menu" in file manager (Total commander/Far manager)

Edited August 20, 2020 by Zedna

[Jos]

mmm... zip file as in "let's not use the installer and have everything properly set for me and then post having issues"..  

Seriously: When installed properly, the last settings are restored from the SciTE.session file :

# SciTE session file

position.left=105
position.top=5
position.width=1712
position.height=1028
position.maximize=1

which is stored in the directory indicated by the environment variable SCITE_USERHOME.

  

Edited August 20, 2020 by Jos

[Zedna]

Thank you very much for the info/solution Jos.