Where is @ScriptLineNumber

[zeenmakr]

I'm getting tired of typing this out and want to shorten it to something like @SLN but dont know which include file it is in. Could someone help point out, Thanks

https://www.autoitscript.com/autoit3/docs/macros.htm

[Jos]

This is an internal Keyword, so you can't change that, but just install the Full version of SciTE4Autoit3 and you will have an easy AutoComplete function!  

[Musashi]

6 hours ago, zeenmakr said:

I'm getting tired of typing this out and want to shorten it to something like @SLN but dont know which include file it is in.

AFAIK , the macros are not declared in one of the open standard UDF's.

I would add a new abbreviation to the SciTE editor.

=> Open au3.keywords.abbreviations.properties ---> add sln

==> Search for au3abbrev.properties (better : au3UserAbbrev.properties (create one, if it doesn't exist))

--> add :

sln=@ScriptLineNumber |

You can do this within the SciTE editor itself (-> Options) :

[mLipok]

1 hour ago, Jos said:

This is an internal Keyword, so you can't change that, but just install the Full version of SciTE4Autoit3 and you will have an easy AutoComplete function!  

Also configurable abbreviation and I think that  you can have a shortcut sln > @ScriptLineNumber

 

[careca]

Go to sctite and in tools>scite config>other tools>run abrev manager>create

 

Alternatively:

If you dont have these filenames showing up in the options drop down menu:

au3UserAbbrev.properties

au3.keywords.user.abbreviations.properties

you can create them in: C:\Users\%userprofile%\AppData\Local\AutoIt v3\SciTE

then inside au3.keywords.user.abbreviations.properties you can have something like:

au3.keywords.userabbrev=sln

And inside au3UserAbbrev.properties:

sln=@ScriptLineNumber

After creating the abreviations you can save these files so you dont have to create again in case you format the pc or something.

Edited May 31, 2020 by careca

[Musashi]

 

32 minutes ago, mLipok said:

Also configurable abbreviation and I think that  you can have a shortcut sln > @ScriptLineNumber

That's what I already suggested above and it works, or am I missing something ?

[careca]

Totaly missed your post, what a waste of time.

[Musashi]

24 minutes ago, careca said:

Totaly missed your post, what a waste of time.

I don't think it was a complete waste of time. There are different ways to get to the goal. Your post contains some information that might help @zeenmakr in case he does not understand my description. According to the motto, double works better .

[mLipok]

3 hours ago, careca said:

Totaly missed your post, what a waste of time.

any activities which engage your brain is not waste of time.

 

EDIT: btw. I missed too.

 

Edited May 31, 2020 by mLipok

[careca]

4 hours ago, Musashi said:

Your post contains some information that might help @zeenmakr in case he does not understand my description.

Looking back I did mention one thing extra: abrev manager

 

Edited May 31, 2020 by careca

[argumentum]

ConsoleWrite(sln() & @CRLF)
ConsoleWrite(sln() & @CRLF)
ConsoleWrite(sln() & @CRLF)
Func sln($sln = @ScriptLineNumber)
    Return $sln
EndFunc

 

[HurleyShanabarger]

2 minutes ago, argumentum said:

ConsoleWrite(sln() & @CRLF)
ConsoleWrite(sln() & @CRLF)
ConsoleWrite(sln() & @CRLF)
Func sln($sln = @ScriptLineNumber)
    Return $sln
EndFunc

 

I like this, but even less typing:

 

sln()
sln()

Func sln($sln = @ScriptLineNumber)
    ConsoleWrite($sln & @CRLF)
    Return $sln
EndFunc

sln()

 

[argumentum]

14 hours ago, zeenmakr said:

tired of typing this out and want to shorten it to something like @SLN

..and that is why I did the way I did @HurleyShanabarger 

[zeenmakr]

Thanks all, this is alot of new infos and opening up new doors. the function trick is neat to tidy up the code and sure am going to abuse the macro method.

tried to edit au3.keywords.user.abbreviations.properties in np++ but file size is 0kb, open ok in SciTE but can't save unless run as admin. does au3.keywords.user.abbreviations.properties get generated on the spot? then where is the text stored?

[zeenmakr]

19 hours ago, Jos said:

This is an internal Keyword, so you can't change that, but just install the Full version of SciTE4Autoit3 and you will have an easy AutoComplete function!  

What is the different between this Full version vs the standard one came with autoit installer? and should i copy and overwrite the standard one or use it as a portable?

[Jos]

The advantages are "A lot" and just use the installer when you have used the AutoIt3 installer as well.

6 hours ago, zeenmakr said:

tried to edit au3.keywords.user.abbreviations.properties in np++ but file size is 0kb, open ok in SciTE but can't save unless run as admin. does au3.keywords.user.abbreviations.properties get generated on the spot? then where is the text stored?

Install the Full version first and then start trying all of this, because else you will get issues like this!  

Jos

 

Edited June 1, 2020 by Jos

[Musashi]

5 hours ago, zeenmakr said:

What is the different between this Full version vs the standard one came with autoit installer? and should i copy and overwrite the standard one or use it as a portable?

1. Full Version of SciTE :

The download page simply says : AutoIt Script Editor (Customised version of SciTE with lots of additional coding tools for AutoIt) - Installer containing SciTE and all configuration files plus utilities

I would definitely prefer the Full Version, because it provides many new features. Just Download and install it (you can probably use the Portable Version, but I haven't done that yet)

 

6 hours ago, zeenmakr said:

then where is the text stored?

2. Add an abbreviation (my way ) :

Open the SciTE-Editor (Full Version). Here again the proceeding (open spoiler with graphic)

Spoiler

-> Click on Options

-> Choose Open au3.keywords.abbreviations.properties ==> add sln -> Save

-> Choose Open au3UserAbbrev.properties ==> add (and save after) :

sln=@ScriptLineNumber |

Of course you can also use the Abbreviation Manager (see posting by @careca ) if you feel more comfortable with it - that's a matter of personal preference. Once you understand how the abbreviations work, you can integrate e.g. entire structures. This can save a lot of unnecessary typework.

Edited June 1, 2020 by Musashi
typo

[rudi]

Very interesting, at least for me: I would have expected, that this would return *ALWAYS* "4", as the function's optional parameter is set to @ScriptLineNumber at line #4 at the first line opening the function block.

 

Looks like this "pre-fillment" of optional parameters is done at the line *CALLING* the function?

 

 

[careca]

This makes sense to me. I wouldn't have it any other way.

[HurleyShanabarger]

I am using this with @error:
 

#NoTrayIcon
#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
    #Tidy_Parameters=/reel /sf /ri
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

#Region Variables/Opt
    Global Const $DEBUG = True
#EndRegion Variables/Opt

#Region Main
    _Main()

    Func _Main()
        SetError(0xDEAD)
        _LogError()
    EndFunc   ;==>_Main
#EndRegion Main

#Region Functions
    Func _LogError($p_iERR = @error, $p_iSLN = @ScriptLineNumber)
        If Not $p_iERR Then Return
        If Not $DEBUG Then Return
        ConsoleWrite("Error: 0x" & Hex($p_iERR, 4) & " @SLN " & $p_iSLN & @CRLF)
    EndFunc   ;==>_LogError
#EndRegion Functions