20-9-2015: New SciTE4AutoIt3 available with the updated SciTE v3.6.0 release.

[Jos]

For the is is all about making clear decisions on "what is in" and "what is out" or else you end up with 5 times more features and the code becomes unmanageable leading to not using it anymore. Doubt there are many of you that even have a clue about all the current options the full version has.

Any way: I have uploaded updates to the Beta directory for:

• au3.properties
• SciTEConfig.au3
• AutoItAutoComplete.lua
• SmartAutoCompleteHide.lua

SciTEConfig will now generate includes.txt in the "SCITE_USERHOME" directory each time you click the "Save,+Apply" button.
The file is also created at the end of the installer when SciTEConfig is ran with parameter /Installer. (Future versions of course) 

See if that also works for you all,

Jos

Edited October 25, 2015 by Jos

[kcvinu]

Thank you @Jos. 

[Jos]

I have an updated version that works also when typing spaces after #include and doesn't need the <> characters as word character.
The dropdown now shows all standard files as "UDF.au3>" after type "<".

Like this better than the previous version.
Update:

• au3.properties
• AutoItAutoComplete.lua
• SmartAutoCompleteHide.lua

Jos

[mLipok]

Works awesome with #include <

but when you use #include "

then in console you get: 

stop:'
stop:'
stop:"
stop:"
stop:"
stop:"

 

 

[kcvinu]

As far as i know, double quotes are used when you need to include files which resides in your script directory. So you know the proper name of the file and you can easily type that. 

[mLipok]

also trying to write this some weired line:

;fddfadff

I get in ConsoleOuput pane:

stop:f
stop:d
stop:d
stop:f
stop:a
stop:d
stop:f
stop:f

 

[Jos]

That is a debug print I forgot to take out in the SmartAutoCompleteHide.lua script.
Just put a # in front of it and I'll fix and upload the update later today.

Jos 

[mLipok]

Thanks.

btw.
Based on this new functionality, I asked myself:
Is it possible to make such a feature which open call tips with methode / property list for some object ?

For example:
$oIE. should open calltips with list of methods and properties for this object.
$oXmlDoc.  should open calltips list of methods and properties for this object.
$oQP. should open calltips list of methods and properties for this object.
?

 

If you confirm this, then I start to learn LUA for this reason.

mLipok

 

Edited October 26, 2015 by mLipok

[Jos]

A lot is possible but let's take a step back and have a closer look at logic here first.
The variable name you shown is just that: "a variable name" which could be $oIE.  but also $MickeyMouse. so how would you link that variable to the correct object and subsequently its .options?

Jos

[kcvinu]

Take variables related with ObjCreate and ObjGet functions. 

[Jos]

Take variables related with ObjCreate and ObjGet functions. 

I hope you do not mean we want to build something with hardcoded variable names... or am I misinterpreting your one-liner ?

Jos

[TheDcoder]

@Jos I think he means something like this:

Local $oObject
$oObject = ObjCreate("shell.application") ; SciTE will detect that this is a object by this line

Local $oNotAnObject = "" ; SciTE will no detect this as an object

[kcvinu]

@TheDcoder Yes, you said it. I thought that i can express my idea in just a oneliner. @Jos, i think he made my point very clear now.

[Jos]

I like the fresh ideas you guys have but am wondering whether you even first think about what that potentially means to create the logic for it and the overhead it could create.  

Jos 

[mLipok]

A lot is possible but let's take a step back and have a closer look at logic here first.
The variable name you shown is just that: "a variable name" which could be $oIE.  but also $MickeyMouse. so how would you link that variable to the correct object and subsequently its .options?

Jos

Yes I know. EDIT: This is: One of the many challenges

 

I like the fresh ideas you guys have but am wondering whether you even first think about what that potentially means to create the logic for it and the overhead it could create.  

Jos 

Because of this I state I start to learn LUA to make it happen, as I do not want to burden you with this as it would be mainly for my needs.

mLipok

 

Edited October 26, 2015 by mLipok

[Jos]

No worries about burdening me.
For me it is important, when adding functionality, that it is easy to maintain and easy/logical to use. 
The #include idea and its current implementation adheres to this, but hardcoded variable names for Object to present the proper methods/objects isn't in my opinion, so would never even consider adding it until it makes sense.

Jos

[mLipok]

.. but hardcoded variable names for Object to present the proper methods/objects isn't in my opinion, so would never even consider adding it until it makes sense.

for now .... nice to talk with you .... but now must to go to other projects.

Thanks again.
mLipok

 

[kcvinu]

@Jos & @mLipok, I have an idea. We can make an additional help file which includes all methods and properties of possible objects. Like the one in VBA in excel and word. What do you say ?

[Jos]

@Jos & @mLipok, I have an idea. We can make an additional help file which includes all methods and properties of possible objects. Like the one in VBA in excel and word. What do you say ?

When I need information I simply use the internet as all information is available there and many examples in eg VBS.
Creating your own source of information (helpfile) requires maintenance and not many will be willing to keep that up after the initial creation.

for now .... nice to talk with you .... but now must to go to other projects.

Thanks again.
mLipok

That makes it sound like you are frustrated with my answers while I am just providing you my honest feedback based on my experience, 

Jos

[kcvinu]

@Jos  It's Ok.