SciTE v 3.20 Beta available

[Jos]

I wrote exactly what you want a while back... got no comments on it surprisingly. Hopefully it suits your purpose:

Nice feature and will be in the next release.

Thanks

[matwachich]

Hello! it's me again, with new suggestions! Hope you guys like them!

- Add to the context menu of a script (right click on the code): "Open Containing Folder" => open in explorer the folder containing the current script.

- Make the "Add Strem Comment" command adds the #cs and #ce as: lowercase, and in the line before, and the line after the selected area

- Add a command to convert spaces to tabs, and vice vers ca

- Just like the standard function that have calltips, it will be nice to add this feature for the current script functions: a kind of "on-the-fly function calltips", that will contain only the definition of the function, with it's parameters. Because when using a function of our script, it's not handy to be forced to search it's definition, to see it's parameters all the time!

- Last: i really don't like the context menu of a tab, it don't need to contain the entire Tools menu!

Thanks for reading me!

[Jos]

Hi. Earlier I hacked around with some lua (neat-o!) and I came up with some extra options for styling the calltip window. This isn't something that no one else could have done.

Add these to your SciTEUser.Properties

## CallTips
# Display the calltip above the function
calltips.set.above=1
# Set the fore and back color of the calltip window
style.au3.38=fore:#DADADA,back:#15191E
# Set the highlight color of the function argument
calltips.color.highlight=#5C81B3

Add this to your lua file. (Look to wraithdu's post here: )

expandcollapse popup

myCallTips = EventClass:new(Common)

function myCallTips:OnOpen(path)
    myCallTips:set_above()
    myCallTips:set_highlight_color()
    return true
end

--------------------------------------------------------------------------------
-- set_above()
-- Displays the calltip above the function.
--------------------------------------------------------------------------------
function myCallTips:set_above()
    local calltips_set_above = tonumber(props["calltips.set.above"])

    if ((calltips_set_above ~= 1) and (calltips_set_above ~= 0)) then
        calltips_set_above = 1
    end

    scite.SendEditor(SCI_CALLTIPSETPOSITION, calltips_set_above)
end

--------------------------------------------------------------------------------
-- set_highlight_color()
-- Set the color of the highlighted calltip property
--------------------------------------------------------------------------------
function myCallTips:set_highlight_color()
    local calltips_color_highlight = props["calltips.color.highlight"]

    if (calltips_color_highlight == '') then
        calltips_color_highlight = "#FF0000" -- dark blue default
    end

    calltips_color_highlight = myCallTips:BGR2Decimal(calltips_color_highlight)

    if (calltips_color_highlight == "Error") then
        return true
    end

    scite.SendEditor(SCI_CALLTIPSETFOREHLT, calltips_color_highlight)
end

--------------------------------------------------------------------------------
-- BGR2Decimal()
-- convert BGR to decimal, duh! (albeit in a hack and stab manner)
--------------------------------------------------------------------------------
function myCallTips:BGR2Decimal(BGR)
    if (BGR.len(BGR) ~= 7) then
        return "error"
    end

    BGR = BGR:gsub('#', '') -- remove hash
    BGR = BGR.reverse(BGR)
    BGR = "0x"..BGR

    return tonumber(BGR)
end

Don't think the calltips.set.above=0 will work as this is a bool and needs to be True or False.

What about doing it this way?:

function myCallTips:set_above()
    local calltips_set_above = tonumber(props["calltips.set.above"])

    if (calltips_set_above == 1) then
        scite.SendEditor(SCI_CALLTIPSETPOSITION, true)
    else
        scite.SendEditor(SCI_CALLTIPSETPOSITION, false)
    end
end

Edited February 5, 2012 by Jos

[Jos]

Hello! it's me again, with new suggestions! Hope you guys like them!

- Add to the context menu of a script (right click on the code): "Open Containing Folder" => open in explorer the folder containing the current script.

Ihave this on my own setup, just add this to your SciTEuser,properties and press Ctrl+E:

#x 40 Open Explorer in scriptdir $(FilePath)
command.40.*=Explorer.exe /e,/select,"$(FilePath)"
command.name.40.*=Open Explorer in Sourcedir
command.shortcut.40.*=Ctrl+E
command.subsystem.40.*=2
command.save.before.40.*=2
command.replace.selection.40.*=0
command.quiet.40.*=1

- Make the "Add Strem Comment" command adds the #cs and #ce as: lowercase, and in the line before, and the line after the selected area

Already available:Select range and hit Ctrl+Shift+Q

Hello! it's me again, with new suggestions! Hope you guys like them!

- Add a command to convert spaces to tabs, and vice vers ca

Already available: SciTE Options/Change Indentation Settings

- Just like the standard function that have calltips, it will be nice to add this feature for the current script functions: a kind of "on-the-fly function calltips", that will contain only the definition of the function, with it's parameters. Because when using a function of our script, it's not handy to be forced to search it's definition, to see it's parameters all the time!

You can define your own Calltips (See helpfile for explanation) but other than that don't see how we can easily do this.

- Last: i really don't like the context menu of a tab, it don't need to contain the entire Tools menu!

This is what comes with the Standard release of SciTE distributed by Neil which is what we use as a base source.

Jos

[jaberwacky]

Good eye. What's good for the goose is good for the gander.

[Melba23]

Jos,

How easy would it be to introduce separate files for user abbreviations in the same way you already have for user UDFs? Is it a simple matter of having separate files and adding some new "import properties" lines to au3.properties or would it entail a lot more?

I ask because having separate files makes "user UDF" management easy whereas the combined files render "user abbreviation" management a bit more tricky.

M23

[Jos]

Jos,

How easy would it be to introduce separate files for user abbreviations in the same way you already have for user UDFs? Is it a simple matter of having separate files and adding some new "import properties" lines to au3.properties or would it entail a lot more?

I ask because having separate files makes "user UDF" management easy whereas the combined files render "user abbreviation" management a bit more tricky.

M23

That should work fine as I have already separated the standard Scite4Autot3 Abbreviation into au3abbrev.properties and added this to abbrev.properties:

import au3abbrev

We could add a line for the user abbrev's to the abbrev.properties

import au3abbrev
import au3UserAbbrev

Edited February 5, 2012 by Jos

[wraithdu]

Are you sure this worked before? I just tried it in SciTE 2.28 released in the latest installer and the mouse doesn't mirror and bookmarks clicks don't do anything.

Researching this in Google only gave me a hit for Notepad++ till now.

Was this working for you in the 2.28 version included in the latest installer?

I could be very red faced now... I'll have to double check an old version of scite to be sure, but I use both editors so it's ENTIRELY possible I'm getting some features confused between the two. Doh. Edited February 5, 2012 by wraithdu

[Valik]

You can define your own Calltips (See helpfile for explanation) but other than that don't see how we can easily do this.

What, you don't have that? I do, noob. I've actually had it for years. It's part of something I was working on that I never finished. Maybe one day.

Edit: Oh, forgot to comment on the inline error thing. Yes, I expected it would involve spawning a new instance to sit around waiting for the parent to close. It's not all that elegant a solution but it works.

Edited February 5, 2012 by Valik

[matwachich]

Thanks for answering me Jos!

Open Folder - Thanks for the trick, i'll add it!

Block Comment - I Know that it's available, but for example: When i select code like this:

some code


[color=#ff0000]some code
some code[/color]

some code

Scite make this

some code


#CSsomecode
somecode#CS

somecode

This is why i made befor & after bold! Because i think it should be something like this

some code
#cs
some code
some code
#ce
some code

Indentation - OK

Tab Menu - So it's impossible to remove it???

Thanks!

[Jos]

I wrote exactly what you want a while back... got no comments on it surprisingly. Hopefully it suits your purpose:

Isn't this the same as Valik already indicated here?:

[wraithdu]

Not quite. The built-in implementation, unless it has changed since I tested it, is highly annoying:

[Valik]

I think "highly annoying" is a bit of a stretch. I'm okay with how it works myself. It works the same as it does in Visual Assist X for Visual Studio which I'm used to.

Edited February 6, 2012 by Valik
Missing word

[wraithdu]

I guess it's a personal preferences then, but I hate the fact it highlights EVERY word I click on every time I move the mouse. I much prefer the Notepad++ (and my function) behavior.

But the point back to Jos is yes, it is different behavior.

[Jos]

Ahh.. you don't like to auto select word feature that kicks in after a second.

Edited February 6, 2012 by Jos

[Jos]

What, you don't have that? I do, noob.

Noob... yeap ... thats me.

Guess you never shared that code with me and only wanted to keep it for yourself.

[Valik]

Noob... yeap ... thats me.

Guess you never shared that code with me and only wanted to keep it for yourself.

It's unfinished which is why I never shared it.

[BrewManNH]

I guess it's a personal preferences then, but I hate the fact it highlights EVERY word I click on every time I move the mouse. I much prefer the Notepad++ (and my function) behavior.

But the point back to Jos is yes, it is different behavior.

wraithdu wrote that allows you to toggle the highlighting on and off, although it doesn't allow you to only highlight it when the text is selected, it does allow you to only highlight it when you want to.

[Valik]

You just told the author of the code about his own code...

[BrewManNH]

I am NOT having a good month lately.