New SciTE4AutoIt3 available with updated SciTE v3.4.1

[guinness]

I am currently using the au3.properties from the beta directory and I am getting this message in the console window...

! invalid property length for: calltips.color.highlight=

[Jos]

 

I am currently using the au3.properties from the beta directory and I am getting this message in the console window...

! invalid property length for: calltips.color.highlight=

It has issues with the " # Only available in SciTE4AutoIt3 version" comment part not being considered as comment.

I had a SciTEUSer.properties setting for this variable hence didn't get any error.

Fixed and uploaded.

Jos

[guinness]

Confirmed as fixed.

[mLipok]

Today I have another day cleanup of old scripts.
I started to use the new features "in AutoIt Functions are first class objects"

for example:

Global $fu_TEST = _TEST

$fu_TEST('Testing')

Func _TEST($sInfo)
    MsgBox(0, '', $sInfo)
EndFunc   ;==>_TEST

and here I miss feature which for variables prefixed with $ fu .... after using CTRL + j, looks up the reference to the function, and thus, would make the jump to the function.

 

Specifically:
Now there is such a message:

Unable to find function definition: $ fu_TEST

 

[FaridAgl]

That's a lot I guess.

[guinness]

I going to hazard a guess that this feature can't be added to due to the nature of what SciTE is.

[Jos]

Today I have another day cleanup of old scripts.

I started to use the new features "in AutoIt Functions are first class objects"

for example:

Global $fu_TEST = _TEST

$fu_TEST('Testing')

Func _TEST($sInfo)
    MsgBox(0, '', $sInfo)
EndFunc   ;==>_TEST

and here I miss feature which for variables prefixed with $ fu .... after using CTRL + j, looks up the reference to the function, and thus, would make the jump to the function.

 

Specifically:

Now there is such a message:

This requires script interpretation which is not something we should want.

It would be similar as asking for this to work with Ctrl+J:

Global $fu_TEST = "_TEST"

Call($fu_TEST)  ; Doesn't work
Call("_TEST")   ; Works

Func _TEST($sInfo="test")
    MsgBox(0, '', $sInfo)
EndFunc   ;==>_TEST

Jos

Edited July 25, 2014 by Jos

[mLipok]

Today I have another day cleanup of old scripts.

Among other things, I dealt with grouping functions in the regions.

 

At some point I noticed a problem with folding, so I prepare a small reproductive script:

#Region TESTING
Func TEST1()
EndFunc   ;==>TEST1

Func TEST2()
    #cs
        4: _
    #ce
EndFunc   ;==>TEST2
#EndRegion TESTING

HOWTO:

try to use NUMPAD KEY on #Region 

folding is ok.

 

try to use NUMPAD KEY on #EndRegion

folding is incorrect.

 

the issue is related to the continuation line .

EDIT: smaller repro

#Region TESTING
#cs
    4: _
#ce
#EndRegion TESTING

Edited July 25, 2014 by mLipok

[Jos]

The issue is actually that the #ce isn't interpreted since it is proceeded by a underscore and thus not resetting the #cs fold.

Just a matter of filtering it down to this simple code:

#cs
    4: _
#ce

It shows the #CE doesn't contain the end-fold indicator.

Jos

Edited July 25, 2014 by Jos

[mLipok]

Oh ... indeed.

After a brief additional test, this problem may be omitted by adding an additional new blank line before #ce

mLipok

[jaberwacky]

This requires script interpretation which is not something we should want.

I just wanted to meditate on this statement.

[mLipok]

In the new beta setup there is changed behavior of CTRL+f  ,   I mean "Find...." option ?

[Jos]

There is a whole bunch of updates to the SciTEGlobal.properties and this is one of them.

You could always actually read the documentation and look for what might the reason for changes you see.

In this case you would find these settings that control this behaviour:

find.use.strip=1
replace.use.strip=1

What the default should be is open for discussion.

Jos

[mLipok]

Today I have another day cleanup of old scripts.
 
And I have a AutoIt hardCrash (Production and Beta)

!>18:14:53 AutoIt3.exe ended.rc:-1073741819

This hard crash is repeatable so I just need to extract the part of the code responsible for this incident (EDIT: #2813).
I'am working on repro, but this is not the case I want to ask in this post.
 
Question:
Why    F4 - "Next message" do not jump to this error ?

Edited July 27, 2014 by mLipok

[mLipok]

What the default should be is open for discussion.

 

At first glance, I like the new option.

However, I question whether her behavior is easily modifiable?

eg

1

whether it can be always on the search bar?

2

why are you hiding when I press "Find Next"

3

I like the "Mark all"

but whether to change its operation better option would be: "Mark / Unmark all"

[Jos]

Today I have another day cleanup of old scripts.

 

And I have a AutoIt hardCrash (Production and Beta)

!>18:14:53 AutoIt3.exe ended.rc:-1073741819

This hard crash is repeatable so I just need to extract the part of the code responsible for this incident ..

I'am working on repro, but this is not the case I want to ask in this post.

 

Question:

Why    F4 - "Next message" do not jump to this error ?

Why would it as this is not a standard recognised error by SciTE?

[Jos]

At first glance, I like the new option.

However, I question whether her behavior is easily modifiable?

eg

1

whether it can be always on the search bar?

2

why are you hiding when I press "Find Next"

3

I like the "Mark all"

but whether to change its operation better option would be: "Mark / Unmark all"

sigh ..  Let me try to make something VERY VERY clear to you:

1. I am not the developer of SciTE!
2. Secondly: I am not the developer of SciTE
3. Thirdly: I am not the developer of SciTE.

So now we have that out of the way:

You have the exact same public sourcecode and information at your disposal as I have which allows you to sort out 80% of the questions yourself.

Don't get me wrong: I do appreciate your sharing your ideas, but I am not your personal SciTE tutor as I also need to research all these things myself in case I need to answer you.

Happy researching

Edited July 26, 2014 by Jos

[mLipok]

sigh ..  Let me try to make something VERY VERY clear to you:

• I am not the developer of SciTE!
• Secondly: I am not the developer of SciTE
• Thirdly: I am not the developer of SciTE.

So now we have that out of the way:

You have the exact same public sourcecode and information at your disposal as I have which allows you to sort out 80% of the questions yourself.

Don't get me wrong: I do appreciate your sharing your ideas, but I am not your personal SciTE tutor as I also need to research all these things myself in case I need to answer you.

 

Happy researching

 

It is clear to me.

And always was clear.

 

Don't get me wrong: 

Sometimes I ask a lot of questions.

Sometimes they come good things for the community.

For these inappropriate and sometimes silly, again sorry.

 

In this case, I just wanted to know, now I know that this is directly related to the SciTE and not of SciTE4AutoIt3.

 

Thanks again.

mLipok

EDIT:

and btw. my last question was related to your statements:

What the default should be is open for discussion.

Just my questions were first reaction to the new feature.

It is possible that they will meet with other readers attention and as a result will help to determine which option is better as a standard, it was my main intention when asking this 3 question.

Edited July 26, 2014 by mLipok

[mLipok]

hi Jos

I notcie you upload a new Autoit3Help.exe
but:

Error while launching:
"C:Program Files (x86)AutoIt3SciTE..betaAutoit3Help.exe" with Params:
""""
%1 nie jest prawidłową aplikacją systemu Win32.

 

Google translate:

%1 is not a valid Win32 application.

[Jos]

I don't get that error when I download and run it.

Do you get this when doing a double click on the program as well or just from SciTE?

Edited July 27, 2014 by Jos