# Open #includes in User Defined folder

## Recommended Posts

How can I get the SciTe hotkey Alt+I to open includes in the folder(s) defined in the "User-defined libraries" registry key?

##### Share on other sites

The registry key is only for AutoIt, the openpath variable in your "User Options File" (from Options menu) controls the same thing for SciTE. See quote:

You have to add the UDFs to the variables:

openpath.$(au3)=$(autoit3dir)\include;D:\Dokumente\AutoIt3\UDF
openpath.beta.$(au3)=$(autoit3dir)\beta\include;D:\Dokumente\AutoIt3\UDF

Thanks!

## Create an account

Register a new account

• ### Similar Content

• By therks
Does SciTE have string or number ids for the recent file menu items?
I was hoping to add shortcuts (using the user.shortcuts properties) to the most recent item, but the documentation doesn't list any id's for those items (unless I overlooked?).
Also, did anyone else notice that the index listing for the SciTE doc doesn't work properly?
It appears it's linking to this: mk:@MSITStore:C:\Program%20Files\AutoIt3\SciTE\Scite4AutoIt3.chm::/SciTEDocumentation.html
When it should be this? mk:@MSITStore:C:\Program%20Files\AutoIt3\SciTE\Scite4AutoIt3.chm::/Scitedoc/SciTEDoc.html
• By 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

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

scitetoolbar.zip
• By Aguilucho
Greetings to the AutoIt community.
I hope that nobody considers my question insulting but I searched 'SciTEConfig.exe' and I did not find it anywhere;
although it is mentioned, it seems like a myth, I can not see if it exists.
Does not contain any .exe either but does have a 'SciteConfig.au3' which, I suppose, has replaced the .exe because on the internet I only find it as malware.
My problem is: My applications to unzip .zip archives, they can see what files SciTEConfig_Source.zip have but they can not unzip it: 'Unknown method' says WinRar.
I have downloaded it again, in case it had been damaged but the result is always the same.

My question is: Is the archive 'SciTEConfig_Source.zip' damaged or does it have any other method of compression?
I need it to learn how to configure SciTE (lite).
Thankful to the developers of AutoIt and to the community.
Regards

I'm trying to use Maps for the first time (Never knew they were available until I read through the release notes) but Scite keeps throwing an error on run about Variable subscript badly formatted.
I tried to run the script directly from AutoIT and it also threw an error.
I've got the latest 3.3.14.5 and just re-installed Scite.
Below is a quick sample that I put together that throws the error in Scite as well as if I run it with the AutoIT Run a script.
#include <GUIConstantsEx.au3> Local $mBug[] ;==> Variable subscript badly formatted$mBug.Width = 1100 $mBug.Height = 700$mBug.GUI = GUICreate("Defect Details", $mBug.Width,$mBug.Height) GUISetState(@SW_SHOW, $mBug.GUI) ;~$iW = 1100 ;~ $iH = 700 ;~$hGUI = GUICreate("Defect Details", $iW,$iH) ;~ GUISetState(@SW_SHOW, $hGUI) While 1 Switch GUIGetMsg() Case$GUI_EVENT_CLOSE Exit EndSwitch WEnd
I tried searching the forum for Maps and it's only talking about Beta which I don't have installed.

so, what am I doing wrong?

Thanks,
Mike
• By tremolux66
I've been experiencing an issue with #cs/#ce block comments and AutoIt code highlighting in ScITE. When I insert the comments-start line, the subsequent lines in the file become comment-colored (green) as expected. Much of the time, when I insert the #ce line, the lines following the comments-end revert to normal code highlighting as expected. But other times, the subsequent lines (to the end of the file) stay green until I save, close, and re-open the file. This seems to occur most often when I am using #cs/#ce to comment-out a section of code, but IIRC it can also occur in cases where I'm just inserting a large comment.
So far, I haven't noticed any pattern to this behavior. The only thing that I can think of is the way I'm entering the #cs & #ce lines when commenting-out code; I often do the following;
Insert the #cs line, something like: #cs ======== Explanation for commenting-out ======== Text below the line turns green Copy the entire #cs line Paste it after the code section (as #cs ...) Edit the pasted line to start with #ce instead of #cs The text below the #ce either reverts to normal ScITE/AutoIt highlighting OR remains green, in which case I have to close and reopen the file to restore normal highlighting. I'm using ScITE Version 3.6.0 (Aug  4 2015 17:34:27).
Any thoughts or suggestions?

×

• Wiki

• Back

• Git