SciTE v 3.20 Beta available

[Jos]

@Valik... seen this post or did it get lost in the other updates?

Looks like we need to change the warning and error messages to lowercase to make it work.

Just update the outputpane messages to lowercase and double click them again... they change then to the correct color.

Did a quick update of the au3check and that looks better. uploaded a copy to the SciTE beta directory (not updated the version yet)

Need to check for a better way to clear the errors because clearing all bookmarks is not a real good option.

.. and this reset does work for getting the Annotations cleared for this function:

SendSciTE_Command($My_Hwnd, $SciTE_hwnd, "extender:dostring scite.SendEditor(SCI_ANNOTATIONCLEARALL)")

This is much better that removing all BookMarks.

Edited January 25, 2012 by Jos

[Jos]

Just uploaded an updated SciTE3.02 beta that will chomp the error further up to the second ":" in stead of the first only.

This changes the Error Annotation from:

"DevelopmentAutoIt3programstesttest3.au3"(2,9) : warning: $var: possibly used before declaration.

to

warning: $var: possibly used before declaration.

This is how it looks now when a Error or Warning is DoubleClicked:

Also added the updated AutoIt3Wrapper to Clear the Errors before each run of au3check.

Edited January 25, 2012 by Jos

[guinness]

I just updated the files in the SciTE 3.02 folder but can't seem to replicate the new addition as above, I'm using Windows 7 x64.

[Melba23]

Jos,

Nor I - Vista x32.

M23

[Jos]

Have you added the lines shown earlier in the thread to your Sciteuser.properties?

error.inline=1
style.error.1=fore:#FF0000,back:#FFFF00
style.error.2=fore:FFFFFF,back:#FF0000

Edit: And copy the latest au3check.exe from the Beta directory as well.

Edited January 25, 2012 by Jos

[guinness]

Sorry Jos. Now it works.

[Melba23]

Jos,

Me too - thanks.

M23

[BrewManNH]

That in-line error message is very handy.

[Jos]

Made another update to AutoIt3Wrapper which now will do an F4 in case Errors/Warnings are detected.

This will automatically show the annotations and jump to the first one.

Next F4 will go to the next error and Shift+F4 to the previous error.

[Jos]

Updated the Beta to v3.03 rc released today by Neil.

[wraithdu]

I'm really digging the inline errors I found a bug though. I can no longer click in the gray area just to the right of the line numbers (where the mouse cursor changes to a mirrored version) to insert a bookmark. It just highlights the line now and moves the cursor to the next line. Maybe this is an option now? Ctrl-F2 still works to insert bookmarks though.

[Valik]

Jos, I've finally got around to messing with inline errors and integrating the stuff into my AutoIt3Wrapper equivalent. Nice work so far. I have a suggestion for you to improve things slightly. Instead of clearing annotations before Au3Check is started I recommend the following logic after it's already run:

; Send the command for SciTE to display the inline errors.  The delay is to ensure SciTE processes the command.
Sleep(100)
If $nExitCode Then
    SendSciTE_Command($hParent, $hScite, "menucommand:306") ; IDM_NEXTMSG
Else
    SendSciTE_Command($hParent, $hScite, "extender:dostring scite.SendEditor(SCI_ANNOTATIONCLEARALL)")
EndIf

This gives a much more polished effect. It eliminates the flicker caused by the annotations being cleared and then re-added. It's also safe to do it this way since if the script is fixed then it will still clear the errors and if the script still has problems then the call to IDM_NEXTMSG which update the annotations including remove those that don't apply and adding any new ones. And, of course, for errors that haven't changed they stay the same with no flicker. All-in-all a small but very nice change from a presentation standpoint.

I just have one question. Now I just need to figure out how to get the IDM_NEXTMSG to stick. With output.scroll=1 the IDM_NEXTMSG happens before the last line of output (The exit code as returned by the wrapper script) so SciTE re-scrolls to the end. I think it would be better if it was left on the first error because that is also where the editor has jumped to. Not a big deal but the current behavior feels a bit wrong to me.

[matwachich]

I have a small suggestion if you permit me:

It would be nice if there was a feature that i learned to really appreciate in Programmer's Notepad:

- When you select a text in the editor, all other (visible) instances of that text are highlighted.

PS: I'm actually working on a Project Manager for Scite, you can follow my work here

Edited February 1, 2012 by matwachich

[jaberwacky]

@matwachich Refer to this thread:

[matwachich]

Great thanks man!

[wraithdu]

I have a small suggestion if you permit me:

It would be nice if there was a feature that i learned to really appreciate in Programmer's Notepad:

- When you select a text in the editor, all other (visible) instances of that text are highlighted.

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

Edited February 1, 2012 by wraithdu

[matwachich]

It's exactly what i need! thanks

[jaberwacky]

I wrote exactly what you want a while back...

Sweet! Just one thing though. The highlight doesn't go away when I unselect. Did I modify my LUA startup correctly?

expandcollapse popup

--------------------------------------------------------------------------------
-- SciTE startup script.
--------------------------------------------------------------------------------

-- A table listing all loaded files.
LoadLuaFileList = { }

--------------------------------------------------------------------------------
-- LoadLuaFile(file, directory)
--
-- Helper function for easily loading Lua files.
--
-- Parameters:
--    file - The name of a Lua file to load.
--    directory - If specified, file is looked for in that directory.  By default,
--         this directory is $(SciTEDefaultHome)Lua.
--------------------------------------------------------------------------------
function LoadLuaFile(file, directory)
    if directory == nil then
        directory = props["SciteDefaultHome"] .. "Lua"
    end
    table.insert(LoadLuaFileList, directory .. file)
    dofile(directory .. file)
end    -- LoadLuaFile()

-- Load all the Lua files.
LoadLuaFile("Class.lua")    -- Always load first.
LoadLuaFile("Common.lua")    -- Always load second.
LoadLuaFile("AutoItPixmap.lua")
LoadLuaFile("AutoHScroll.lua")
LoadLuaFile("AutoItAutoComplete.lua")
LoadLuaFile("LoadSession.lua")
LoadLuaFile("AutoItIndentFix.lua")
LoadLuaFile("EdgeMode.lua")
LoadLuaFile("SmartAutoCompleteHide.lua")
LoadLuaFile("Tools.lua")
LoadLuaFile("AutoItTools.lua")
LoadLuaFile("AutoItGotoDefinition.lua")

-- Start up the events (Calls OnStartup()).
EventClass:BeginEvents()

MyTools = EventClass:new(Common)

function MyTools:OnStartup()
    -- class property to hold active marker state so we only update when necessary
    self.bMarkersActive = false
    -- class property to indicate programatic marker clearing and avoid double UI update
    self.lastSelText = ""
    -- initialize missing props
    if props['highlight.sel.text'] ~= '0' and props['highlight.sel.text'] ~= '1' then
        props['highlight.sel.text'] = '1'
    end
    if props['highlight.whole.word'] ~= '0' and props['highlight.whole.word'] ~= '1' then
        props['highlight.whole.word'] = '1'
    end
    if props['highlight.min.length'] == '' then
        props['highlight.min.length'] = '2'
    end
end

function MyTools:OnUpdateUI()
    if props['highlight.sel.text'] == '1' then
        local selText = editor:GetSelText()
        -- check if selection has changed, update accordingly
        if selText == self.lastSelText then
            return false
        else
            self.lastSelText = selText
        end
        --print('update')
        local selStart = editor.SelectionStart
        local selEnd = editor.SelectionEnd
        -- check if selected text is an allowed word
        if selStart ~= selEnd and self:IsWord(selText) then
            -- check for word boundaries at ends of selection
            if props['highlight.whole.word'] == '0' or (not self:IsWord(string.char(editor.CharAt[selStart-1])) and not self:IsWord(string.char(editor.CharAt[selEnd]))) then
                self:markOccurrences(selText)
            else
                self:clearOccurrences()
            end
        else
            self:clearOccurrences()
        end
    end

    return false
end

function MyTools:IsWord(word)
    if props['highlight.whole.word'] == '1' then
        -- look for anything not allowed
        local find = string.find(word, '[^%a%d_$#@.]')
        if find == nil then
            return true
        else
            return false
        end
    else
        -- return true if selection length is >= highlight.min.length and no new lines
        local find = string.find(word, '[rn]')
        if find == nil and string.len(word) >= tonumber(props['highlight.min.length']) then
            return true
        else
            return false
        end
    end
end

function MyTools:clearOccurrences()
    if self.bMarkersActive then
        --print('clearing')
        scite.SendEditor(SCI_INDICATORCLEARRANGE, 0, editor.Length)
        self.bMarkersActive = false
    end
end

function MyTools:markOccurrences(selText)
    self:clearOccurrences()
    -- set flag markers are active
    self.bMarkersActive = true
    -- set indicator style
    local curIndic = 0
    scite.SendEditor(SCI_SETINDICATORCURRENT, curIndic)
    scite.SendEditor(SCI_INDICSETALPHA, curIndic, 255)
    scite.SendEditor(SCI_INDICSETUNDER, curIndic, true)
    scite.SendEditor(SCI_INDICSETSTYLE, curIndic, INDIC_ROUNDBOX)
    scite.SendEditor(SCI_INDICSETFORE, curIndic, 0xFFF55D)
    -- set search flags
    --local flags = SCFIND_WHOLEWORD
    local flags = 0
    -- find each occurrence of the word and set the indicator range
    local s,e = editor:findtext(selText, flags, 0)
    while s do
        scite.SendEditor(SCI_INDICATORFILLRANGE, s, e - s)
        s,e = editor:findtext(selText, flags, e+1)
    end
end

[Jos]

Jos, I've finally got around to messing with inline errors and integrating the stuff into my AutoIt3Wrapper equivalent. Nice work so far. I have a suggestion for you to improve things slightly. Instead of clearing annotations before Au3Check is started I recommend the following logic after it's already run:

; Send the command for SciTE to display the inline errors.  The delay is to ensure SciTE processes the command.
Sleep(100)
If $nExitCode Then
    SendSciTE_Command($hParent, $hScite, "menucommand:306") ; IDM_NEXTMSG
Else
    SendSciTE_Command($hParent, $hScite, "extender:dostring scite.SendEditor(SCI_ANNOTATIONCLEARALL)")
EndIf

This gives a much more polished effect. It eliminates the flicker caused by the annotations being cleared and then re-added. It's also safe to do it this way since if the script is fixed then it will still clear the errors and if the script still has problems then the call to IDM_NEXTMSG which update the annotations including remove those that don't apply and adding any new ones. And, of course, for errors that haven't changed they stay the same with no flicker. All-in-all a small but very nice change from a presentation standpoint.

I just have one question. Now I just need to figure out how to get the IDM_NEXTMSG to stick. With output.scroll=1 the IDM_NEXTMSG happens before the last line of output (The exit code as returned by the wrapper script) so SciTE re-scrolls to the end. I think it would be better if it was left on the first error because that is also where the editor has jumped to. Not a big deal but the current behavior feels a bit wrong to me.

looks like a good suggestion and will have a play with it and IDM_NEXTMSG that next week.

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

looking at this thread again it seems i totally missed it. Will have a look also next week to incorporate when i like it.

[wraithdu]

Sweet! Just one thing though. The highlight doesn't go away when I unselect. Did I modify my LUA startup correctly?

Eek, no. I didn't specify how to do that exactly...

Create a new LUA file somewhere on your computer. I keep mine in a location outside the Scite install so it is not touched by the installer/uninstaller. Then add the line to load it into SciTEStartup.lua:

-- ....

LoadLuaFile("AutoItTools.lua")
LoadLuaFile("AutoItGotoDefinition.lua")
-- your file here
LoadLuaFile("MyTools.lua", "C:somepathtofile")

You can change the indicator style in the markOccurrences function.

Then add the control properties to your SciTEUser.properties file.

Edited February 1, 2012 by wraithdu