SciTE Toolbar

[BrewManNH]

I was looking for a toolbar modification for SciTE and I was checking various versions of SciTE that were available on the internet. They all had some problems for how I wanted to use the editor, so I looked here to see if there were any toolbar modifications for Scite. I found one very old script by YogiBear (Volly) from 2006 that looked promising, though there were issues with it. I decided to see what I could do to modify this script, and make some improvements to it if possible. This script is the result of that work.

It's not perfect and definitely could use some tweaking, but I thought that it had matured enough, and was mostly stable enough to release the updated version.

Changelog:

Version 2.0.1

Minor update to remove all the old Obfuscator directives and replaced them with #Au3Stripper directives instead. I also corrected a minor bug that only showed up for me on one computer I tried this on, and caused the tool bar to crash for others as well.

SciTE toolbar version 2.0

• Changed the settings values to use constants instead of 'magic numbers'
• The icons on the toolbar weren't lining up with the separator characters or with the toolbar GUI because they weren't set with the resize setting for the icons, only for the separators.
• Changed to using arrays for everything, it makes it a lot easier to loop through the controls
• Added a line to use an alternate path to the SciTE program, so you can start it using, for example, the portable version instead of installed version for those that don't install AutoIt and/or SciTE4AutoIt3. It will accept a commmand line parameter that points to the SciTE executable.
• Removed a lot of Global variables by moving the GUI creation and monitoring to the Main function and passing variables from it.
• I embedded the icon files into the script so that there isn't a separate download of the icon files used here. Saves download time and makes the package smaller.
• Modification of tools is easier because the icon names, tooltip text, and SciTE command codes are saved in the INI file upon first start up. These can be modified after the script has been run once, even after it's been compiled, by changing the ini file information, you can modify this script to automate it, or you can change it manually in any text editor.
• The icon files are now using, in just my opinion, better looking icons, after all it's been 7 years and icon files have matured.
• I have included a file with all of the constants that SciTE uses for its menu commands which comes from the SciTE source file "scite.h", so you can use this file to help you modify the commands that the toolbar works with, by figuring out what each of these values represent in SciTE.

The core of the script is pretty much the same, I've just fixed a couple of issues that it had, tweaked a few things, added some new functionality and "prettied" it up a bit.

If anyone has any suggestions as to improvements, bugs/bugfixes, etc. please let me know.

 

scitetoolbar.zip

Edited April 2, 2018 by BrewManNH
Inserted zip file of script

[guinness]

Certainly tidier, but CPU usage is a constant 5-6%.

[BrewManNH]

I have tried everything I could think of to get it to go lower, but it won't go below 5% for some reason.

EDIT: Seems like, but I'm not positive, that it might be related to using ProcessExists to monitor for SciTE.

Edited April 1, 2013 by BrewManNH

[guinness]

Strange, because in SciTE Jump when it's docked to SciTE I monitor SciTE's position and I don't have the same problem.

[BrewManNH]

Simple quick fix once I thought about it some more.

Change this line in the Main() function:

If Not ProcessExists("Scite.exe") Then ExitLoop

To this:

If Not WinGetHandle("[class:SciTEWindow]") Then ExitLoop

Some functionality, different CPU load.

Script will be updated once I get home.

[guinness]

I didn't pay attention, I've experienced a CPU increase before using ProcessExists.

[BrewManNH]

I've updated the download link above. The latest version has the change I posted above.

[wraithdu]

I think you can get fancy about it too by opening a process handle then using GetExitCodeProcess to see if it is still running (check for return STILL_ACTIVE). I go that route when using CreateProcess directly since I already have the handle. And yes, ProcessExists is expensive. If I had to guess, it pulls a list of all running processes (PSAPI or Toolhelp32) and compares names / PIDs. If it uses PSAPI then it needs an additional function call to get the process name.

You might still be able to use ProcessExists if you use it with a PID directly instead of a name. Not sure if that would be less expensive or not, but might be worth a try.

[TheSaint]

Very good.

You must have missed my old one - Toolbar For Any.

Made primarily for SciTE, but can be used for other programs too.

It has many nifty features, and I still use it every day, and don't know how productive I'd be without it, it just saves so much fussing.

Never tested the CPU load.

[BrewManNH]

I saw that ToolBarForAny, it's really nice, but this one had source code available, and allowed me to play with it.

It was more of a learning experience to try out some new programming techniques I've learned, better coding practices etc. Plus it allowed me to modify things to more of my likes.

This script is great for using as a base for something more extensive, such as making it easier to configure than hacking around in INI files to change the tools it connects to, different icon files, different commands that can be added that run external processes (like TBFA does).

[guinness]

Never tested the CPU load.

I believe I did and if I remember it was the same issue.

[Melba23]

BrewManNH,

Thanks for the ProcessExists warning - a very handy tip.

M23

[BrewManNH]

Took a little bit of script breakage to find out where the CPU load was coming from, just started commenting out sections until the load dropped.

[TheSaint]

I saw that ToolBarForAny, it's really nice, but this one had source code available, and allowed me to play with it.

I'm always open to sharing code with those in the MVP group ... so long as they don't judge me too harshly.

That said, at the very least, my code would need upgrading to a current AutoIt version.

Of course, as with all my programs, they have gone through updates beyond what is publicly available at the forum.

I don't doubt that yours is much better in many areas beyond my skill level, especially with memory footprint.

That said, mine has many redeeming features not usually found in others here ... but I think one needs to use it for a while to really appreciate the full extent of that. My recommendation, would be to incorporate those into what you've done ... in fact, my Toolbar came into being (like so many of my programs), because of features I thought should be in others, but weren't ... fine as they were.

[guinness]

That said, at the very least, my code would need upgrading to a current AutoIt version.

As I demonstrated, if you using just native functions it's highly unlikely that anything major will need updating, I mean I updated your script in 10 seconds.

[TheSaint]

That was a far simpler affair that script, and I don't approach any of my bigger programs for updating, unless I've got the time and desire to troubleshoot anything that may get broken. I've known from past experience, what a pain it is when you troubleshoot these things, usually rewriting blocks of code ... and that was just for minor point changes, nothing like the jump that 3.2.4.12 (?) was or the even huger leap of 3.3.0.0 and later. Functions get a change of parameters sometimes, not just a name change, and sometimes the parameters work differently.

So for me, it's all a matter of need, and I would only really be updating to please others, not myself, as they all currently work fine for me.

However, I have no beef about someone else attempting it.

I code for myself, but keep others in mind, and that's why I'm open to sharing ... providing they realize that it is just sharing, and not a commitment of any sort.

[Bert]

Nice someone picked up where I left off with this.

Excellent work! 

+1

[BrewManNH]

I updated the download in the first post, minor bug fix and code clean up.

[Bert]

I just downloaded the update and ran it. NICE WORK!!!

edit: I updated the original thread to tell people to come to this thread.

Edited September 2, 2014 by MBALZESHARI

[Monooboe]

Hi BrewManNH,

The link is no longer working.

I have tried Bert  Scite Toolbar and I like it.   I would like to use your updated version.  

Can anyone  upload it for me?  

thank you