Organize Includes in Scite for Autoit

[CoolDomi]

Hi Mega,

1st great work!!, great utility thx a lot .

I am currently not using any Beta version of AutoIt, and I your script stop working due to I think this:

If $InstallPath <> '' And $normalOrBetaOrBoth = 1 Or $normalOrBetaOrBoth = 3 Then _ArrayAdd($includesPathes_A, $InstallPath & '\Include\')
If $betaInstallPath <> '' And $normalOrBetaOrBoth = 2 Or $normalOrBetaOrBoth = 3 Then _ArrayAdd($includesPathes_A, $betaInstallPath & '\Include\')

Should add parenthesis to separate the OR condition from the AND:

If $InstallPath <> '' And ($normalOrBetaOrBoth = 1 Or $normalOrBetaOrBoth = 3) Then _ArrayAdd($includesPathes_A, $InstallPath & '\Include\')
If $betaInstallPath <> '' (And $normalOrBetaOrBoth = 2 Or $normalOrBetaOrBoth = 3) Then _ArrayAdd($includesPathes_A, $betaInstallPath & '\Include\')

and it works again like a charm (or at least works for me again .

Dom

[martin]

Hi Mega,

1st great work!!, great utility thx a lot .

I am currently not using any Beta version of AutoIt, and I your script stop working due to I think this:

If $InstallPath <> '' And $normalOrBetaOrBoth = 1 Or $normalOrBetaOrBoth = 3 Then _ArrayAdd($includesPathes_A, $InstallPath & '\Include\')
If $betaInstallPath <> '' And $normalOrBetaOrBoth = 2 Or $normalOrBetaOrBoth = 3 Then _ArrayAdd($includesPathes_A, $betaInstallPath & '\Include\')

Should add parenthesis to separate the OR condition from the AND:

If $InstallPath <> '' And ($normalOrBetaOrBoth = 1 Or $normalOrBetaOrBoth = 3) Then _ArrayAdd($includesPathes_A, $InstallPath & '\Include\')
If $betaInstallPath <> '' (And $normalOrBetaOrBoth = 2 Or $normalOrBetaOrBoth = 3) Then _ArrayAdd($includesPathes_A, $betaInstallPath & '\Include\')

and it works again like a charm (or at least works for me again .

Dom

Or maybe

If $InstallPath <> '' And BitAnd($normalOrBetaOrBoth,1) Then _ArrayAdd($includesPathes_A, $InstallPath & '\Include\')
If $betaInstallPath <> '' And BitAnd($normalOrBetaOrBoth ,2) Then _ArrayAdd($includesPathes_A, $betaInstallPath & '\Include\')

[engine]

Doesn't work on release 3.2.12.0

Please make it work.

Thanks.

[CoolDomi]

Hi,

Another "fix" for the next release:

In the function getIncludes() instead of:

For $i = 1 To $lines_A[0] - 1

write

For $i = 1 To $lines_A[0]

otherwise you will miss the last file referenced in the includes.ini file (in my case WindowsConstants.au3 )

Dom.

[Xenobiologist]

Hi,

thanks everybody. I will fix the stuff you posted now.

Anything left?

Thanks!

Mega

[foggw]

Thanks for the great program, very useful.

One suggestion, change the 'default'

Global $normalOrBetaOrBoth = IniRead($includesIni, 'Options', 'NormalOrBetaOrBoth', 3)oÝ÷ ÚÚºÚ"µÍÛØ[  ÌÍÛÜX[Ü]SÜÝH[TXY
    ÌÍÚ[ÛYÒ[K  ÌÎNÓÜ[ÛÉÌÎNË   ÌÎNÓÜX[Ü]SÜÝ ÌÎNËJBNØÚ[ÙHÛHÝÈÜX[

On my system I ended up with Registry entries for 'Beta' but the beta directory no longer existed.

The Organizer would start, display a message box that the path was invalid (from: Func _saveIncludePathesToIni() and then abort.

Setting the default value $normalOrBetaOrBoth to Normal would help idiots like me that haven't been keeping up with system maintenance.

Thanks!

Bill

[foggw]

Regarding the $normalOrBetaOrBoth setting.

I just installed again on a newly built system with AutoIt 3.2.12.1 installed (never had beta).

Got a similar error this time showed \Include\ as the path in error.

In the installer program the FileInstall statements are fully pathed to a directory that will not exist on most systems.

I have found that prefixing the source file with "\." will perform the FileInstall from the current directory.

FileInstall(".\sourcefile.xxx", $DestLocation)

Thanks again.

Bill

[Xenobiologist]

Hi,

yeah thanks!

I already changed a lot in that area. Just two other things to go/fix and then I will post the next version.

Mega

[Zedna]

In the installer program the FileInstall statements are fully pathed to a directory that will not exist on most systems.

I have found that prefixing the source file with "\." will perform the FileInstall from the current directory.

FileInstall(".\sourcefile.xxx", $DestLocation)

Thanks for that tip!! It's very usefull.

I will make BugTrack report to include this tip into FileInstall helpfile documentation.

[Xenobiologist]

Hi,

new version. See first post!

Thanks!

Mega

[Xenobiologist]

Hi,

everything fine for those who tested the new version?

Thanks!

Mega

[engine]

Everything except this

Great UDF. Should be included with AutoIt.

Thanks.

[engine]

Also I have noticed it can only be run from the account I used to install it.

Installed it from both accounts and now it works. But should work for all accounts with just one install.

Edited July 11, 2008 by engine

[Xenobiologist]

Also I have noticed it can only be run from the account I used to install it.

Installed it from both accounts and now it works. But should work for all accounts with just one install.

Hi,

Scite puts its SciteUser.properties into user account folder. That is why, OI works with this user specific property file.

So this comes with Scite not with OI and IMO this behaviour is fine.

Mega

[ofLight]

Thanks for this Mega Works great, Incredible timesaver for me. muttley

[Tlem]

Thousand tanks Mega.

Greet addition for Scite4AutoIt (If jos read this, perhaps it will be a great idea to add it in future installation of Scite4AutoIt).

I created on the French forum a link towards this topic and towards the zip file. muttley

http://www.autoitscript.fr/forum/viewtopic.php?p=7358#p7358

Tanks again, again, again ...

[engine]

Hi,

Scite puts its SciteUser.properties into user account folder. That is why, OI works with this user specific property file.

So this comes with Scite not with OI and IMO this behaviour is fine.

Mega

I agree it is fine. However AutoIt and SciTE4AutoIt3 are installed globally. If this UDF is included it must be global too.

It's just my opinion.

Regards.

[Xenobiologist]

Thanks to all of you.

My french got a bit lost over the last 10 years, but I was able to understand your words! muttley

Topic : Include OI in Scite.

I guess this will never happen, cause the script has grown gradually and Jos will never support something like that.

But never say never. If he tolds me what to change for getting into it, I will do.

Maybe some day, Jos implements a link for those who want to try the script.

That would be nice.

Mega

P.S. : I'm still open for suggestions and improvements.

E.g. : I could create a new ini for all the words used in OI and then OI could be multilingual.

[Tlem]

E.g. : I could create a new ini for all the words used in OI and then OI could be multilingual.

Even if AutoIt and Scite4AutoIt is only in English, I find that it would really be a very good idea.

[Jos]

Topic : Include OI in Scite.

I guess this will never happen, cause the script has grown gradually and Jos will never support something like that.

But never say never. If he tolds me what to change for getting into it, I will do.

Maybe some day, Jos implements a link for those who want to try the script.

That would be nice.

Mega,

Not sure why you say that it will never happen. I remember you asked in the beginning of the development of your utility to have it included in the SciTE4AutoIt3 package and I am not sure what I exactly answered but don't think it was ready at that time.

I have nothing against including it in the SciTE4AutoIt3 installer when there is a benefit for a larger group of users of this utility.

I have included a new directive in the current Beta version of SciTE4AutoIt3 that will add all missing "standard constants" includes.

If your script does a better job, I could even replace that internal Func with calling your script.

I haven't looked at it for that last couple of months but will give it a spin again to see how things work and give some feedback.

Just some general question I have without having looked yet:

1. Does your script follow the exact standard for Include path search etc. I see you define "extra" includes in an INI? Are you also reading the same Registry entries as AutoIt3 does for finding extra includes?

2. Do you support a commandline option to tell it to use Production or Beta includes?

More to follow in the coming days.. Thanks

Jos muttley