SCITE

[Jos]

Just had a play and added the option to copy the comments with the current available Tidy version in Beta:

Quote

added option  to copy comments from #CS to #CE. Default is to copy the comments.
Added Tidy Parameters:  /Skip_CE_Comment or /scec will skip this copy action
Added INI option:
* * *  Add comment to #CE/#CommentEnd and make it the same as the #CS/CommentStart Comments.
ce_comment=1
 

Jos

[Skysnake]

Morning

Another question. Maybe I miss something.

Scite can add the version to the source, on Build or Compile, such as 123.1.2.3. 

But what I am actually looking for is to include the COMPILE DATE in the source code. 

 

Is there a switch for this?

 

Thanks

Edited February 16, 2018 by Skysnake

[Jos]

I guess you mean AutoIt3Wrapper. I use this directive to add that to the PE header:

://////=__=

Jos

Edited February 18, 2018 by Jos

[Skysnake]

My dear Sir, please be so kind as to explain your explanation?

"C:\AutoIt\pegasi\main.au3" (15) : ==> Error in expression.:
://////=__=
^ ERROR
->19:56:51 AutoIt3.exe ended.rc:1
+>19:56:51 AutoIt3Wrapper Finished.
>Exit code: 1    Time: 13.13

;                The last header lines...
#AutoIt3Wrapper_Run_AU3Check=n
#AutoIt3Wrapper_AU3Check_Parameters=-d -w 1 -w 2 -w 3 -w 4 -w 6 -q
#Au3Stripper_Parameters=/rm
://////=__=
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

Or, If I move it to the version line....

! Invalid FileVersion value 4=50://////=__=. It will be changed to:50
-> No changes made..

Yes. You are probably right about the AutoItWrapper.  Where should I place this?

[Jos]

mmm I see the forum is screwing with my posted code.

Lets see if this works without codebox: #AutoIt3Wrapper_Res_Field=Compile Date|%date% %time%

Or quote:

Quote

#AutoIt3Wrapper_Res_Field=Compile Date|%date% %time%

Jos

[Skysnake]

Thank you.  This has resolved another issue I had.

But I still want an answer for a question, perhaps best phrased like this: when I build/compile, the EXE can contain a FileVersion, which can be auto updated.  It is written to the source code (and included in the out file).

Is it possible to write the build/compile date to source code as well? 

[Jos]

I guess I have lost you as to what you want.  Give me an example script how you use the fileversion information so I understand what you mean.

Jos

[Skysnake]

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_Outfile_type=a3x
#AutoIt3Wrapper_LastBuild=201802192031 <<<<<<<<<<<<<<<<<<<<<<<<<<<<< system updated on build
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

#include <MsgBoxConstants.au3>

MsgBox($MB_SYSTEMMODAL, "Title", "This message box will timeout after 10 seconds or select the OK button.", 10)

I hope this helps.  So whenever I open the source file, I can see when is the last time this source was built.

 

[Jos]

Sorry but that doesn't make it any clearer for me.
How is the line I posted not right for you? It will write the compile date into the PE header.

Try compiling and running this script:

Quote

#AutoIt3Wrapper_Res_Field=Compile Date|%date% %time%
#AutoIt3Wrapper_Res_FileVersion=1.2.3.4
MsgBox(262144, 'FileGetVersion(@ScriptName):', FileGetVersion(@ScriptName))
MsgBox(262144, 'FileGetVersion(@ScriptName,"Compile Date"):', FileGetVersion(@ScriptName, "Compile Date"))

Jos

Edited February 18, 2018 by Jos

[Skysnake]

Thank you.

Your code works.  It shows the date in the MsgBox. As expected.

However, I would like that date written to the ???.au3 source file. So that when I open the source in my editor (Scite) it is visible there.  Especially when compiling to a3x that date may not be apparent until runtime.

I hope I explained my intention clearly. Thank you for your trouble.

Edited December 22, 2018 by Skysnake

[Jos]

Ah, ok... understand now. That function is not build into AutoIt3Wrapper, sorry.  

Jos

[Simpel]

Hi.

I tried to fill that into AutoIt3Wrapper.ini so I hadn't to write it manually into my scripts:

Field1Name=Compile Date
Field1Value=%date% %time%

But message box shows "%date% %time%" instead of a date and time. Is there a solution for?

Regards, Conrad

[Jos]

4 hours ago, Simpel said:

Is there a solution for?

Sure. It is just a matter of running the result of IniRead() through the Func Convert_Variables(). Till now that is only done for Directives, but easy enough to implement for INI defaults. I've updated it for the below fields in the INI in the current available beta of AutoIt3Wrapper:

17.224.935.11 allow for variables (e.g. %date%) in Comment/Description/FieldValue1/FieldValue2

Jos

[Simpel]

Great. With this hint just edited AutoIt3Wrapper.au3.

[Jos]

9 hours ago, Simpel said:

Great. With this hint just edited AutoIt3Wrapper.au3.

Did you make more changes than the Beta version, which also should be made in my version? if so, could you share what those changes are?

Jos 

[mLipok]

47 minutes ago, Jos said:

Did you make more changes than the Beta version, which also should be made in my version? if so, could you share what those changes are?

I would be also interested to see this answer.

 

[Simpel]

Hi.

I made a two liner of yours:

$INP_FieldValue1 = Convert_Variables(IniRead($ScriptFile_In & ".ini", "Res", "Field1Value", "")) ; #552
$INP_FieldValue2 = Convert_Variables(IniRead($ScriptFile_In & ".ini", "Res", "Field2Value", "")) ; #554

and a four liner of:

If $INP_FieldValue1 = "" Then $INP_FieldValue1 = Convert_Variables(IniRead($AutoIt3WapperIni, "Res", "Field1Value", "")) ; #595
If $INP_FieldValue2 = "" Then $INP_FieldValue2 = Convert_Variables(IniRead($AutoIt3WapperIni, "Res", "Field2Value", "")) ; #597

I did not:

$INP_Comment = Convert_Variables(IniRead($ScriptFile_In & ".ini", "Res", "Comment", "")) ; #540
$INP_Description = Convert_Variables(IniRead($ScriptFile_In & ".ini", "Res", "Description", "")) ; #541
If $INP_Comment = "" Then $INP_Comment = Convert_Variables(IniRead($AutoIt3WapperIni, "Res", "Comment", "")) ; #583
If $INP_Description = "" Then $INP_Description = Convert_Variables(IniRead($AutoIt3WapperIni, "Res", "Description", "")) ; #584

So I think yours is more complete.

Can you give me a hint (or maybe you did it in the beta already) how the added lines inside AutoIt3Wrapper.ini will appear later inside my au3?

Regards, Conrad

[Jos]

1 minute ago, Simpel said:

So I think yours is more complete.

Why not  simply copy my Beta version into the Scite\AutoIt3Wrapper directory?

1 minute ago, Simpel said:

Can you give me a hint (or maybe you did it in the beta already) how the added lines inside AutoIt3Wrapper.ini will appear later inside my au3?

Not sure what you are asking here? Could you explain please?

Jos

[Simpel]

1 minute ago, Jos said:

Why not  simply copy my Beta version into the Scite\AutoIt3Wrapper directory?

As you may remember I did another change due to include stripped and unstripped source: https://www.autoitscript.com/forum/topic/191887-au3stripper-sendto/?do=findComment&comment=1377255

But I think about merging both.

4 minutes ago, Jos said:

Not sure what you are asking here? Could you explain please?

When I compile nearly all defaults I put inside AutoIt3Wrapper.ini then are standing as **** Directives created by AutoIt3Wrapper_GUI **** inside the just compiled script.

Field1Name, Field1Value, Field2Name, Field2Value do not. Run_Au3Stripper=y, Au3Stripper_Parameters=/mo inside wrapper.ini don't appear in actual au3 script after compiling, too. What tool is responsible for that, AutoIt3Wrapper? And how to add all lines giving directives for wrapping inside wrapper.ini after compiling into actual au3 script?

Conrad

[Jos]

Try current Beta changes: Added lines 4059-4064.

Jos