SciTE hotkeys & manipulation

[JackDinn]

Hi,

Iv just done a little ConsoleWrite() replacement that suites my purposes (i know there's a few already, but where's the fun in that ).

I was just wondering how i would go about adding a hotkey for it that will write the line _Debug() and also fill it with the text that the cursor is currently in or selected (just like Alt+D does for ConsoleWrite() ) ?

I have had a good look through all the SciTE options / properties / abbreviations and found a few entries that mention the hot keys but i cant see how to extract the info i need.

If i could just find how the Alt+D works and where its all setup i might be able to see what i need but all i can find is this in the au3.Properties

# 25 Add a Console msg for debugging

command.name.25.$(au3)=Debug to Console

command.subsystem.25.$(au3)=3

command.25.$(au3)=InvokeTool AutoItTools.DebugConsoleWriteAdd

command.shortcut.25.$(au3)=Alt+D

command.save.before.25.$(au3)=2

But this really dont tell me much.

I did find this thread but Jos said "All Options can be found in file IFaceTable.cxx which I have attached." but i cant see this IFaceTable.cxx

Thx.

Edited May 7, 2011 by JackDinn

[BrewManNH]

Look in the file called AutoItTools.lua, that's where the code for that is.

[Jos]

The SciTE4Autoit3 Helpfile explains what these config lines mean.

What exactly do you want to change/do?

Jos

[JackDinn]

Ahh, many thx, should be able to work with that (hopefully, lol)

will the .LUA file be overwritten if i ever update SciTE ?or am i supposed to make a "User" .lua file somewhere ?

Edited May 7, 2011 by JackDinn

[JackDinn]

excellent , works beautify

thx for the pointer BrewManNH, that was all i needed.

[BrewManNH]

I would suppose that it will be over written if you ever update the software. You can always make a back-up of it though. Or make your own .lua file and have it loaded at startup, the startup lua files are called from SciteStartup.lua.

[JackDinn]

Im wondering why when i use my little debug() func on my current script project to view the main array it colours some of the console output red ?

It dont do it if i test it on a quick test script.

The output is only generated by a normal ConsoleWrite :- ConsoleWrite("Array =: " & $text & " :=" & @CRLF & $output & @CRLF).

This has got me thinking , i would like some red parts but how do i control which parts of the output are coloured red ?

[Jos]

This is from the FAQ:

How do I get SciTE to understand the error messages from my compiler?

The set of error message formats is embedded in the Scintilla and SciTE code. To add support for another compiler, you will need to add a new style to scintilla/include/Scintilla.iface after the other SCE_ERR_* values, run HFacer.py, edit RecogniseErrorListLine in scintilla/src/LexOthers.cxx to recognise the error message, and edit DecodeMessage in scite/src/SciTEBuffers.cxx to extract the file name and line number.

So when you want to understand how SciTE recognises errors then that is where you can find the details.

You can also play with the start characters of the outputlines by using on of these: + - ! >

Jos

[JackDinn]

phew , that quote went straight over my head , lol, i shall have a play with the first characters.

It just looked odd because which line is coloured is random, there's no difference between each line. I would be happy to just remove the red colouring all together, i thought it might have something to do with the fact that the output was still flowing whilst the script was continuing past the debug but iv tried sleeping while the console buffer is still writing the output but makes no difference.

Looks like its to much for me to understand , I will prob just have to leave it as it is.

Thx anyhow