![Wink ;)](./images/smilies/icon_e_wink.gif)
Ive heard of NVIDIA stories having some issues with SciTE+DirectX, anyway cheers!
![Smile :)](./images/smilies/icon_e_smile.gif)
fincs: This problem still occurs if the SciTE window is unresponsive while starting up, which can happen if it is re-opening files via the network. I would suggest using SendMessage() via DllCall and waiting until the window responds - or indefinitely. The SendMessage command's built-in timeout will only make things worse in this case. (I'm referring to the SendMessage which gives x its value.)Grendahl wrote:
I open Help > Help, click on the Index tab & start typing a keyword. After typing one or two letters, the CHM window stops responding to message events (the CHM thread hangs), and it is necessary to close SciTE in order to recover from it. Alternatively, placing the cursor in the middle of a keyword and open the help file sometimes causes the same effect. This behaviour happens randomly and sometimes it behaves correctly. Opening the CHM outside SciTE never fails. Deleting the .chw file makes no difference.lexikos wrote:What are you saying it does?
Will fix.lexikos wrote:When I upgrade-install SciTE, there are three options that can't be turned off:
(...)
When the installer closed, the Program Compatibility Assistant came up. You need to add a manifest resource specifying Vista and 7 as supportedOS. See AutoHotkey.exe.manifest for an example.
How can I tell apart custom modification from a corrupted registry setting?lexikos wrote:My settings for the edit verb are not the default set by SciTE and I do not want them overwritten.
This shouldn't have happened if you had previously installed S4AHK without desktop shortcuts (maybe you had deleted it manually) - the setting is supposed to be saved to the registry.lexikos wrote:I do not want a Desktop shortcut and did not have one before.
Code: Select all
RegRead, defEdit, HKLM, Software\SciTE4AutoHotkey, InstallDefEditor
RegRead, defSS, HKLM, Software\SciTE4AutoHotkey, InstallDefSS
RegRead, defDS, HKLM, Software\SciTE4AutoHotkey, InstallDefDS
;...
RegWrite, REG_DWORD, HKLM, Software\SciTE4AutoHotkey, InstallDefEditor, %bDefaultEditor%
RegWrite, REG_DWORD, HKLM, Software\SciTE4AutoHotkey, InstallDefSS, %bStartShortcuts%
RegWrite, REG_DWORD, HKLM, Software\SciTE4AutoHotkey, InstallDefDS, %bDesktopShortcuts%
Why would it be corrupted? Why would you need to detect it? Just allow the user to choose.fincs wrote:How can I tell apart custom modification from a corrupted registry setting?
That's a matter of opinion - why would I want that setting saved in the registry? If I deleted the shortcut, I obviously don't want it. In any case, the installer should not disable the checkbox unless it's actually going to do nothing either way (i.e. because the shortcut's already there and won't be removed if you untick the box).[...] the setting is supposed to be saved to the registry.
I see now that F1 is the accelerator associated with Help -> Help so it probably doesn't matter whether you use the keyboard or menu.I open Help > Help
I tested for a while on Windows 7 and XP, and couldn't fault it.This behaviour happens randomly and sometimes it behaves correctly.
Code: Select all
---------------------------
Toolbar.ahk
---------------------------
Error: "2" is not a valid key name.
Line#
263: Menu,ToolMenu,Add,Check for updates...,check4updates
266: GroupAdd,SciTE4AutoHotkey,ahk_id %scitehwnd%
267: GroupAdd,SciTE4AutoHotkey,ahk_id %hwndgui%
270: dbg_active := false
273: Hotkey,IfWinActive,ahk_id %scitehwnd%
274: Loop,%ntools%
275: if Tools[A_Index].Hotkey != ""
---> 276: Hotkey,Tools[A_Index].Hotkey,ToolHotkeyHandler
279: InitComInterface()
282: Director_Init()
285: AhkDir := DirectorReady ? CoI_ResolveProp("", "AutoHotkeyDir") : (SciTEDir "\..")
286: if DirectorReady && !IsPortable
287: {
289: temp := Util_GetAhkPath()
290: if temp
The current thread will exit.
---------------------------
OK
---------------------------
wow.. didn't know thatjoedf wrote:Use tillagoto!
Just select the function then, Middle click instead!
It will go directly to the function definition.
I have set it up for HTML, perl, python, powershell and sql. You need to add some lines to your user properties (Options, Open user properties). These are the lines I added:scott123 wrote:My apologies if this has already been discussed, but, rather than work with multiple editors for different languages, I'd like to use Scite4Autohotkey for everything, especially for html. For instance, I took html.properties from the most recent Scite release and placed it in the main folder, but it doesn't seem to show up in the languages. How do I add languages?
Code: Select all
# Import settings / properties (*** IMPORTANT- files are expected in this folder)
import D:\Dougal\Documents\AutoHotkey\SciTE\ExtraProperties\perl
import D:\Dougal\Documents\AutoHotkey\SciTE\ExtraProperties\python
import D:\Dougal\Documents\AutoHotkey\SciTE\ExtraProperties\powershell
import D:\Dougal\Documents\AutoHotkey\SciTE\ExtraProperties\sql
import D:\Dougal\Documents\AutoHotkey\SciTE\ExtraProperties\html
# Define the Lexer menu,
# Each item contains three parts: menu string | file extension | key
# The only keys allowed currently are based on F-keys and alphabetic keys and look like # [Ctrl+][Shift+][Fn|a] such as F12 or Ctrl+Shift+D.
# A '&' may be placed before a letter to be used as an accelerator. This does not work on GTK+.
#~ Defines the entries in the Language menu and the file extensions they map to. Each menu item is defined by 3 elements, language name, extension and an optional keyboard equivalent. Each element is terminated by '|'. For example:
#~ H&ypertext|html|F12|
# language
menu.language=\
&AutoHotkey|ahk||\
&Lua|lua||\
&INI and property files|ini||\
&BASH|sh||\
&Powershell|ps1||\
&SQL|sql||\
$(ext.menu.language)\
$(user.menu.language)
Yep, that is the one. I did make some tweaks, couldn't help myself.joedf wrote:So you mean this style?
https://github.com/joedf/PlasticCodeWra ... properties
Did you try to replace all the ahk1 with *?
Code: Select all
34 font.normal=font:Bitstream Vera Sans Mono,size:10 <>
35 #font.normal=font:DejaVu Sans Mono,size:10 34 font.normal=font:DejaVu Sans Mono,size:10
36 normal=$(font.normal),fore:#F8F8F8 35 style.ahk1.0=$(font.normal),fore:#F8F8F8
37 style.ahk1.0=$(normal)
------------------------------------------------------------------------
------------------------------------------------------------------------
57 comment=fore:#1E9AE0,italics <> 55 style.ahk1.1=fore:#1E9AE0,italics
58 style.ahk1.1=$(comment)
------------------------------------------------------------------------
------------------------------------------------------------------------
75 operator=fore:#FFAA00 <> 72 style.ahk1.4=fore:#FFAA00
76 style.ahk1.4=$(operator)
------------------------------------------------------------------------
------------------------------------------------------------------------
82 string=fore:#55E439 <> 78 style.ahk1.6=fore:#55E439
83 style.ahk1.6=$(string)
------------------------------------------------------------------------
------------------------------------------------------------------------
86 number=fore:#FF3A83 <> 81 style.ahk1.7=fore:#FF3A83
87 style.ahk1.7=$(number)
------------------------------------------------------------------------
------------------------------------------------------------------------
93 variable=fore:#FB9A4B <> 87 style.ahk1.9=fore:#FB9A4B
94 style.ahk1.9=$(variable)
------------------------------------------------------------------------
------------------------------------------------------------------------
100 keyword=fore:#FFAA00,italics <> 93 style.ahk1.11=fore:#FFAA00,italics
101 style.ahk1.11=$(keyword)
------------------------------------------------------------------------
------------------------------------------------------------------------
104 command=fore:#EB939A <> 96 style.ahk1.12=fore:#EB939A
105 style.ahk1.12=$(command)
------------------------------------------------------------------------
------------------------------------------------------------------------
129 error=fore:#EF2929 <>
130 style.ahk1.20=$(error) 120 style.ahk1.20=fore:#EF2929
------------------------------------------------------------------------
------------------------------------------------------------------------
134 # Brace highlight +-
135 style.*.34=fore:#00FFFF,bold
136 # Brace incomplete highlight
137 style.*.35=fore:#FFFF00,bold
------------------------------------------------------------------------
Code: Select all
# Bash styles
# The bash styles are set to lots of different foreground and background colours as an
# aid to debugging SciTE's Bash lexer - not because this is a good way to display Bash.
style.bash.32=fore:#F8F8F8,back:#0B161D,$(font.normal)
# White space
style.bash.0=$(normal)
# fore:#808080,$(font.base)
# Error
style.bash.1=$(error)
# Comment
style.bash.2=$(comment)
# style.bash.2=$(colour.code.comment.box),$(font.code.comment.box)
# Number
style.bash.3=$(number)
# Keyword
style.bash.4=$(command)
# Double quoted string
style.bash.5=$(colour.string),$(font.monospace)
# Single quoted string
style.bash.6=$(colour.char),$(font.monospace)
# Operators
style.bash.7=$(operator)
# Identifiers (functions, etc.)
style.bash.8=$(variable)
# Scalars: $var
style.bash.9=$(variable)
# Parameter expansion: ${var}
style.bash.10=fore:#000000,back:#FFFFFF
# Back Ticks
style.bash.11=fore:#FFFF00,back:#004040
# Here-doc (delimiter)
style.bash.12=fore:#000000,back:#DDD0DD
# Here-doc (single quoted, q)
style.bash.13=fore:#7F007F,back:#DDD0DD,eolfilled,notbold
# Braces are only matched in operator style
braces.bash.style=7
Users browsing this forum: No registered users and 17 guests