boiler wrote: ↑
16 Jun 2020, 09:21
Sometimes when I arrow down through the auto-complete list then press Enter, it doesn't accept the Enter as having selected that item. The list disappears, the item isn't sent to my editor, and the Enter gets sent to the editor window to start a new line.
This is definitely unexpected behavior. How have you filled out your settings in the Settings dialog? A screenshot will suffice if you like.
EDIT: The method I'm using now to try and send text to the scintilla control is not ideal at all. I'm working with SendMessage() now to try and find a better method. I've had mixed results, though it mostly works on my system. Hopefully if I find a SendMessage() solution it will be more reliable on other systems.
It seems to be finicky about when auto-complete will automatically start when I start typing.
What's your PC specs? And what version of windows are you on? I'm on an Intel i7 processor, 2.5 GHz / 8 cores with 16GB of RAM. It's possible I need to find a more efficient method. I have the timer set to 100 ms, so if you type faster than that then you won't see autocomplete until you stop typing. I can probably make this a user setting. Search for SetTimer "LoadAutoComplete", -100
and keep the value below 0, but make it less than 100. It behaves acceptably on my PC. I don't usually feel like I need the auto-complete window to be "ever present" as i type, especially when I'm going fast and don't need any of the suggestions.
When I click on a calltip, it's bringing up an empty help window, not my v2 help file. Is that because I don't have v2 as my primary installation, so the only help file in my standard install location is for v1 (which has a different name)? It would be nice if this were configurable to point to a different location for the help file, especially since v2 isn't always the primary AHK installation.
The help file it searches for is actually in the script folder \Languages folder. Place and overwrite your desired help chm there. I can have the script check for an installation and use that CHM, that shouldn't be an issue.
The background color for the auto-complete box is white, so I'm getting yellow on white, which I can't see. If I change it to a darker font color, then I can't see it on the dark background of the calltip. Can the background for the auto-complete be selectable, or is the only solution to choose a light background for the calltip so that a dark font color works on both?
The background for the autocomplete is definitely supposed to be the same color as the call tips. I use a dark windows custom theme, so I'll disable that and test out auto-complete. I probably just missed something, or something unexpected may have broken in a111.
It would be nice to have it automatically show the calltip for an item when it's selected from the auto-complete box instead of then having to use the hotkey or use the mouse to double-click on it.
Very cool idea! I'll add that to the to-do list.
Could the various hotkeys be user-selectable? I realize I can change them in the script, but then those changes would be lost with updates.
This is a planned feature.
Thanks for your consideration. By the way, I'm using Notepad++ to test it out. I generally use VSCode, but obviously can't for this.
I've been looking for a way to interface this script with VSCode, but haven't been successful yet.
Thanks for the feedback!
EDIT: I've already fixed the background color for auto-complete, haven't pushed the updated yet though.