BETA: SciTE v5x & lua Dynamic_include and "Smart" AutoComplete for Vars/UDFs/Abbrevs

[mLipok]

@Jos would you be so nice and put all current files on 

https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/SciTE5-with-DynamicFunctions/

 

[Jos]

  On 12/18/2024 at 11:20 AM, mLipok said:

and put all current files on 

Expand  

I can take a look, but first like to understand what it is you are asking.  

Is your question whether I can merge all changes/update into the Beta installer and portable zip file or something else?

[mLipok]

  On 12/18/2024 at 12:50 PM, Jos said:

Beta installer and portable zip file

Expand  

would be the best

[Jos]

... or were you asking whether the those files in there are the latest versions?  ( which they are except change I am not fully sure about)

 

[mLipok]

  On 12/18/2024 at 1:58 PM, Jos said:

which they are except change I am not fully sure about

Expand  

As separate test single file please.

[Jos]

  On 12/18/2024 at 3:08 PM, mLipok said:

As separate test single file please.

Expand  

That is not the approach. You will find the "sets" of files or installers which all belong together. 
The latest LUA scripts I am sure of will be in the file:    SciTE_changes_Dynamic_Includes_LUA.zip
There could be temporarily another file there, but they shouldn't be there for long.

(hope i understood you better this time or else please PM me with a little more context.  

[Jos]

Just uploaded SciTEx86.zip & SciTEx64.zip which contain the Latest SciTE 5.5.4 versions released today 18 December 2024.

[donnyh13]

Hi Jos,

Just another minor trouble I found. I can type and paste in the Console, but when I use backspace, it backspaces in the main editor, not the console.

Edited March 13 by donnyh13

[Jos]

  On 12/29/2024 at 6:42 PM, donnyh13 said:

.. but when I use backspace, it backspaces in the main editor, not the console.

Expand  

That is indeed a glitch in AutoitAutoComplete.lua. Try changing line 52 to add a test which pane has the focus to:

function AutoItAutoComplete:OnKey(code, shift, control, alt)
    if editor.Lexer ~= SCLEX_AU3 or props['FileNameExt'] == '' or not editor.Focus  then

 

[donnyh13]

  On 12/29/2024 at 8:46 PM, Jos said:

Try changing line 52

Expand  

That fixed it, thanks Jos!

[mLipok]

I found a problem with the blinking cursor disappearing.

Try pressing Enter after "closing bracket" at the end of the second line, in this following testing snippet:

Func _1()
    For $i = 1 To $a[0] 
    Next
EndFunc

 

Edited January 1 by mLipok

[Jos]

I indeed see the same on the current Beta happening, but started to work on an update for the "indent fix" logic, and that version is not having this symptom anymore.
So guess you will have to wait a bit till I am feeling the urge to finish that, and an update is published.  

 

[BinaryBrother]

I'm curious about a few things. I did read the first three pages.

How exactly do we set this up?

Is it working alright, or is it glitchy? I'm also wondering why, with the added capability that it isn't default.

[Jos]

The first post is all you need to read really and should give enough info for the setup.

[BinaryBrother]

I can see, now, that you've put plenty of effort into presenting this. The GIFs are spot-on. I just missed one line of your text, and it was the Beta Installer location.

Thanks again for the massive upgrade.

Edited January 11 by BinaryBrother

[BinaryBrother]

Can I turn off the orange upside-down triangles that appear? I searched the forums for symbols, orange triangles, etc and didn't see anything.

Here's a highlighted pic.

 

I believe they indicate last edits, since that's where they all appear. After a while the code gets a little cluttered with them.

[Jos]

This is an added change.history feature that can be tweaked with these settings:

  Quote

change.history marker.reverted.to.origin marker.saved marker.modified marker.reverted.to.modified indicator.reverted.to.origin.insertion indicator.reverted.to.origin.deletion indicator.saved.insertion indicator.saved.deletion indicator.modified.insertion indicator.modified.deletion indicator.reverted.to.modified.insertion indicator.reverted.to.modified.deletion

The change.history property controls whether changes to the document (insertions, deletions, saved chanes, ...) are shown as margin markers or indicators within text. It is a set of bit flags (1=enable, 2=margin markers, 4=indicators in text) so the most likely settings are 0=disabled; 3=enabled with margin marks, or 7=enabled with margin markers and in-text indicators. There is a default set of visuals for this feature but they may be altered with the marker.* and indicator.* properties. As change history can only be enabled when the file is in its original state, this property only takes effect when a file is loaded.

Expand  

The markers will reset each time you do a save file.
I have set change.history=3 for myself to only get the line markers at the beginning of each changed line.

See this discussion earlier in this thread: 

 

 

[BinaryBrother]

Well, if people search for an upside-down triangle, they can find the solution now! lol

Thanks again, Jos.

[BinaryBrother]

When I create or modify a function, ex

Func _Test()

When I hit return at the end of that line, it doesn't auto-tab like the normal Scite does, so you're starting in the right place. Furthermore, when I do hit tab, it adds a line of whitespace underneath.

I recorded a video of what I'm talking about.

If I knew the names of what I'm talking about I could search the threads. I'm so naive when it comes to ScITE behavior. I don't remember this happening before... Maybe I accidentally changed something?

https://app.screencast.com/Ye8sgIrN5jn2R?conversation=kVzfwHR5ziWsdaEyCkgKKr

Edited January 27 by BinaryBrother

[Jos]

  On 1/27/2025 at 7:23 PM, BinaryBrother said:

When I hit return at the end of that line, it doesn't auto-tab like the normal Scite does, so you're starting in the right place. Furthermore, when I do hit tab, it adds a line of whitespace underneath.

Expand  

I know... been discussed a couple of times in this "long ass thread"...  One day I might pick it up again and finish the changes required for the AutoIndent functionality, unless somebody beats me to it and get it done for us.  One other option I am still considering is dropping the Full SciTE development and start supporting the Visual Studio Code movement.