New SciTE4AutoIt3 available with updated SciTE v3.4.1

[guinness]

Sorry Jos, but I didn't say using 14 failed for me. I was just looking at the AutoIt3Wrapper source code whilst creating a resource update function and I wanted to use the structure for the bitmap header instead of just 14 (I was first curious as to where this value came from). This is when I found AutoIt was returning 16 bytes and not 14 for the struct size. So I then filed a report to you after I tested on my machine that 16 worked in the AutoIt3Wrapper as well.

But I now see from the wiki article 14 is the correct size and that it's just confidence  that 16 was working as well. No issue or change required.

Edited July 19, 2014 by guinness

[jchd]

There is dword alignment after the first word in the tag cited. If one wants the structure to be 14 bytes, one needs to adjust with align:

Global Const $tagBITMAPFILEHEADER = 'word bfType;dword bfSize;word bfReserved1;word bfReserved2;dword bfOffBits'
Local $t = DllStructCreate($tagBITMAPFILEHEADER)

ConsoleWrite(_VarDump($t) & @CRLF) ; 16 bytes

Global Const $tagBITMAPFILEHEADER14 = 'align 2;word bfType;dword bfSize;word bfReserved1;word bfReserved2;dword bfOffBits'
Local $t = DllStructCreate($tagBITMAPFILEHEADER14)

ConsoleWrite(_VarDump($t) & @CRLF) ; 14 bytes

[guinness]

jchd,

Did you see my >update? -_0

[Jos]

Sorry Jos, but I didn't say using 14 failed for me. I was just looking at the AutoIt3Wrapper source code whilst creating a resource update function and I wanted to use the structure for the bitmap header instead of just 14 (I was first curious as to where this value came from). This is when I found AutoIt was returning 16 bytes and not 14 for the struct size. So I then filed a report to you after I tested on my machine that 16 worked in the AutoIt3Wrapper as well.

But I know see from the wiki article 14 is the correct size and that it's just confidence  that 16 was working as well. No issue or change required.

No problem, glad things cleared up.

[jchd]

Sorry for stating the obvious, I missed that.

[mLipok]

Uploaded v1.2.1.3 that now works for at least 150 levels deep.

Jos

Works OK.

Thanks.

[mLipok]

So I try to fix it in a next week.

Please leave this case for me as a challange.

 

All yours

 

I works on this

and here are my results:

---

I can not fix it how I wanted.

But I can propose a workaround:

in AutoIt3Wrapper.au3

inside Func RunAutoItDebug

change this line:

FileWriteLine($fhDebugFile, StringFormat("%sConsoleWrite('%04u: ' & $__err%s[0] & '-' & $__err%s[1] & ': %s' & @CRLF)", $sIndent, $iSavedLine, $iRandom, $iRandom, $sModifiedLine))

to this:

FileWriteLine($fhDebugFile, StringFormat("%sConsoleWrite('Line #' & @TAB & '%04u' & ' = ' & $__err%s[0] & '-' & $__err%s[1] & ': %s' & @CRLF)", $sIndent, $iSavedLine, $iRandom, $iRandom, $sModifiedLine))

and now 

according to the HelpFile for the ConsoleWrite() should work this functionality:

ConsoleWrite('Start with String or Integer then ' & @TAB & '6' & ' = Pink (jump to line 6 when double-clicked)' & @CRLF)

Unfortunately did not work (even that of the example taken from HelpFile ).

I think it is related to SciTE4AutoIt, if so - Can it be fixed ?

Edit: typo and wording

Edited July 19, 2014 by mLipok

[wraithdu]

But I now see from the wiki article 14 is the correct size and that it's just confidence  that 16 was working as well. No issue or change required.

 

IIRC when I wrote that function, I got 14 bytes from empirical tests - size of original bitmap versus size of the bitmap resource after Resource Hacker had embedded it.

[mLipok]

Today, as usual, I was working on my programs.

At one time I used TIDY and received strange error message.

Here's reproductive script:

Func _test()
    #region Test1 inside Func _test()

    #EndRegion
    #region Test12 inside Func _test()

    #EndRegion
EndFunc

and console output:

>"C:\Program Files (x86)\AutoIt3\SciTE\tidy\tidy.exe" "Z:\TOOLs\Macro\_TEST\Test_TIDY_Func.au3"
Tidy AutoIt3 v2.4.1.6   Copyright (c) Jos van der Zande  June 2, 2014
! oops: right char is not =#region Test1 inside
"Z:\TOOLs\Macro\_TEST\Test_TIDY_Func.au3"(5) : ### Tidy Warning -> #EndRegion statements without #Region.
! oops: right char is not =#region Test12 inside
"Z:\TOOLs\Macro\_TEST\Test_TIDY_Func.au3"(8) : ### Tidy Warning -> #EndRegion statements without #Region.
"Z:\TOOLs\Macro\_TEST\Test_TIDY_Func.au3"(3) : ### Tidy Error -> "func" is never closed in your script.
"Z:\TOOLs\Macro\_TEST\Test_TIDY_Func.au3"(2) : ### Tidy Error -> "func" is never closed in your script.
!> there were  2 error(s) encountered. look in your source for:### Tidy Error:
+> Tidy AutoIt3 finished. Original copied to:"Z:\TOOLs\Macro\_TEST\BackUp\Test_TIDY_Func_old1.au3"
>Exit code: 2    Time: 1.016

[mLipok]

according to the HelpFile for the ConsoleWrite() should work this functionality:

ConsoleWrite('Start with String or Integer then ' & @TAB & '6' & ' = Pink (jump to line 6 when double-clicked)' & @CRLF)

Unfortunately did not work (even that of the example taken from HelpFile ).

I think it is related to SciTE4AutoIt, if so - Can it be fixed ?

 

Any chance for any answers?

[Jos]

 

Today, as usual, I was working on my programs.

At one time I used TIDY and received strange error message.

Here's reproductive script:

Fixed in the current Beta v 2.4.1.7

Jos

[mLipok]

Thanks

[Jos]

Any chance for any answers?

This example is supposed to use the standard error lexing of SciTE and guess something changed there.

This means some digging work in the source to figure out what changed and what it should be.

Jos

Edit: these are the common formats found in LexOthers.cpp

 

        // Look for one of the following formats:

        // GCC: <filename>:<line>:<message>

        // Microsoft: <filename>(<line>) :<message>

        // Common: <filename>(<line>): warning|error|note|remark|catastrophic|fatal

        // Common: <filename>(<line>) warning|error|note|remark|catastrophic|fatal

        // Microsoft: <filename>(<line>,<column>)<message>

        // CTags: <identifier>t<filename>t<message>

        // Lua 5 traceback: t<filename>:<line>:<message>

        // Lua 5.1: <exe>: <filename>:<line>:<message>

 

Edited July 22, 2014 by Jos

[mLipok]

Thanks for the explanation.

[Jos]

Thanks for the explanation.

see update in previous post.

[mLipok]

I'm sorry but I'm not so familiar with SciTE API.
Can you explain a little more what this is reflected in this case ?

[Jos]

I'm sorry but I'm not so familiar with SciTE API.

Can you explain a little more what this is reflected in this case ?

That are the formats the Error Lexer recognises and does the autojump for when double clicked.

We are using the Microsoft format in Tidy;au3stripper and au3check. I only modified it to allow for double quotes around the filenames.

Jos

[mLipok]

so... 

As I understand your statement ConsoleWrite will no longer work as described in HelpFile ?

ConsoleWrite('Start with String or Integer then ' & @TAB & '6' & ' = Pink (jump to line 6 when double-clicked)' & @CRLF)

---

So I have further question about:

ConsoleWrite('(5) : = Red (jump to line 5 when double-clicked)' & @CRLF) ; '(5) :' red text color and double click jumps to (line number)

Can this work like this:

ConsoleWrite('(000005) : = Red (jump to line 5 when double-clicked)' & @CRLF) ; '(5) :' red text color and double click jumps to (line number)

but in this case (when using leading zeros) without red txt color ?

[Jos]

Dunno and don't really want to dive into the lexer code what format is and what isn't supported at this moment.

Just download the public SciTE source code and look at file LexOthers.cpp when you want to figure out all these details.

Edited July 22, 2014 by Jos

[mLipok]

Roger that.
I stay with what I know, no further questions in this regard.