New SciTE4AutoIt3 available with updated SciTE v3.4.1

[mLipok]

SciTE v 3.4.3 Beta version is now available in the Beta-Directory.

Please test the highlight.current.word* functionality to ensure all modification made in our version still work correctly.

Jos

thanks

Checked, looking good.

btw.

in SciTE Config for AutoIt3 ver:1.6.11

"CallTip displayed above function" do not works correctly.

[Jos]

btw.

in SciTE Config for AutoIt3 ver:1.6.11

"CallTip displayed above function" do not works correctly.

This one requires a restart of SciTE.

There is an option to "tell" SciTE that this is changed without a restart, so will implement that for this option.

EDIT: Let me know when you find others that do not update by a reload properties and require a SciTE restart at this moment.

Jos

Edited June 7, 2014 by Jos

[mLipok]

This one requires a restart of SciTE.

not working even if I restart SciTE

 

Let me know when you find others that do not update by a reload properties and require a SciTE restart at this moment.

Ok.

[Melba23]

Jos,

Looks good so far.

The highlight.current.word* change will cause a few raised eyebrows for those who use spaces between parameters in their code - basically anyone who uses Tidy. As the SciTE changelog shows no bug number attached to this, do you happen to know why it was changed?

M23

[Jos]

not working even if I restart SciTE

Ok.

don't know as it does work for me.

[Jos]

Jos,

Looks good so far.

The highlight.current.word* change will cause a few raised eyebrows for those who use spaces between parameters in their code - basically anyone who uses Tidy. As the SciTE changelog shows no bug number attached to this, do you happen to know why it was changed?

M23

this is a change in the standard SciTE. I think it is listed on the change log.

Jos

[mLipok]

I think it is listed on the change log.

 

You mean this:

SciTE's highlight current word feature no longer matches the selection when it contains space.

 

 

?

Edit: typo

Edited June 7, 2014 by mLipok

[wraithdu]

New beta looks good to me so far. BTW, I noticed two phase draw (two.phase.draw) and  Direct2D / DirectWrite (technology) are disabled or missing in the current global options file. Particular reason for that? I enabled them and they seems to work fine.

[Jos]

You mean this:

?

Correct

 

New beta looks good to me so far. BTW, I noticed two phase draw (two.phase.draw) and  Direct2D / DirectWrite (technology) are disabled or missing in the current global options file. Particular reason for that? I enabled them and they seems to work fine.

I haven't tried for a while to sync up the latest SciTEGlobal.properties with the current supplied version.

Maybe I should start supplying the standard one without wanting to change that.

Jos

[jaberwacky]

The highlight.current.word* change will cause a few raised eyebrows

Oh wow, they went backwards as far as I'm concerned.

[Jos]

The highlight.current.word* change will cause a few raised eyebrows for those who use spaces between parameters in their code - basically anyone who uses Tidy. As the SciTE changelog shows no bug number attached to this, do you happen to know why it was changed?

 

Oh wow, they went backwards as far as I'm concerned.

 

The original SciTE is really copying the behaviour of Visual Studio and be default auto select the current word.

I believe the reason was to stop the current word highlight at a space to avoid SciTE slowing down on long selections.

It is probably very easy to add yet another option to highlight.current.word.* to make this selectable if this is really a desired function.

One thing I like to avoid though is making more an more modifications in our version that will make it harder to maintain. This time around I had some difficulties making my modifications to work again as the code was changed a lot around this option.

Jos

[jaberwacky]

Very reasonable.  If the SciTE developer(s) thought it should go away then I guess it's probably for the best.  Though, I guess I can entertain the thought of seeing if I can work out a lua solution.

[Danp2]

How to fix this issue of variables "comment.box.start.au3", "comment.box.middle.au3", and "comment.box.end.au3", not being declared when trying to insert a block comment?

Also get a GPF in Scite when attempting to insert a Stream Comment under some circumstances. Not sure if this is helpful, but here's the info show:

 

[Jos]

How to fix this issue of variables "comment.box.start.au3", "comment.box.middle.au3", and "comment.box.end.au3", not being declared when trying to insert a block comment?

SciTE seems to insist on a value for "comment.box.middle.au3="

Try adding something like ";~" for it and you see it works, but I don't particularly like that option in that way.

Also get a GPF in Scite when attempting to insert a Stream Comment under some circumstances. Not sure if this is helpful, but here's the info show:

Any way I can replicate the Error so I can have a look at it?

Thanks

jos

[Jos]

Very reasonable.  If the SciTE developer(s) thought it should go away then I guess it's probably for the best.  Though, I guess I can entertain the thought of seeing if I can work out a lua solution.

 

I have added a keyword to allow you to override the default behaviour of stopping at a Space character:

highlight.current.word=1
highlight.current.word.by.style=1
highlight.current.word.colour=#00D040
highlight.current.word.autoselectword=0    # Only available in SciTE4AutoIt3 version
highlight.current.word.wholeword=0         # Only available in SciTE4AutoIt3 version
highlight.current.word.matchcase=0         # Only available in SciTE4AutoIt3 version
highlight.current.word.minlength=3         # Only available in SciTE4AutoIt3 version
highlight.current.word.stoponspace=1       # Only available in SciTE4AutoIt3 version

This is implemented in the current Beta version available, so have a spin and see if that works correctly.

Also added an updated SciTEGlobal.properties which has this one added and also some of the missing parameters mentioned:

New beta looks good to me so far. BTW, I noticed two phase draw (two.phase.draw) and  Direct2D / DirectWrite (technology) are disabled or missing in the current global options file. Particular reason for that? I enabled them and they seems to work fine.

 

The two.phase.draw parameter is already in there with the same default as the original distribution and am not sure it can be safely changed? Thought there were some issue with these 2 in the beginning but haven't really followed that discussion..

#two.phase.draw=0
if PLAT_WIN
    technology=1

Let me know when there are things missing or some of the defaults in there should be changed.

Jos

Edited June 8, 2014 by Jos

[Danp2]

Any way I can replicate the Error so I can have a look at it?

 

Not consistently. Here are the steps that I am performing:

1) Launch Scite, which opens with the previously editted script already loaded

2) Type a random word, such as "test"

3) Press Ctrl-Shift-Q to perform a Stream comment

[Melba23]

Jos,

The highlight.current.word.stoponspace change works nicely - thanks.

M23

[Jos]

I can replicate the bug and found it is a generic one that exists in the original SciTE.

It happen when the Caret is at the last character of the file and you hit Ctrl+Shift+Q, because it is trying to write the text to insert at the Caret position +1.

It sometimes does a hardcrash and sometimes just doesn't write the #ce.

Jos

Edited June 8, 2014 by Jos

[Danp2]

Glad you were able to reproduce it.

[Jos]

Glad you were able to reproduce it.

Should be fixed in the current Beta ...