MobileRead Forums - View Single Post - Help—Sigil 2.02 blocking external macros (autohotkey)

hayaku · 11-14-2023, 08:18 AM

Hello all!

Been using and loving Sigil for quite some years now.

I have quite an extensive set of custom AHK (autohotkey) macros which I run through Windows.

These allows me to use all manner of custom characters—for example, using [Ctrl + foo] or [Ctrl + Alt + bar] combinations—which I find extremely useful for things like en-dashes, [–] em-dashes [—], scientific symbols, and other things which I frequently use when I write.

For some reason, his functionality has been completely disabled when I upgraded from Sigil ~1.6 to 2.02 last night.

I have gone into settings and deleted all competing [Ctrl + foo] hotkeys, but it seems that simply having the program open and in focus takes complete control over the [Ctrl] key, in addition to the [Alt] and [Shift] keys. AHK never receives the commands in the first place due to Sigil 2.02.

Any idea what is up with this? Perhaps this is a bug, or a disable-able feature in preferences?

Much thanks!

11-14-2023, 08:18 AM	#1
hayaku Member Posts: 13 Karma: 10 Join Date: Nov 2023 Device: Kindle	Help—Sigil 2.02 blocking external macros (autohotkey) Hello all! Been using and loving Sigil for quite some years now. I have quite an extensive set of custom AHK (autohotkey) macros which I run through Windows. These allows me to use all manner of custom characters—for example, using [Ctrl + foo] or [Ctrl + Alt + bar] combinations—which I find extremely useful for things like en-dashes, [–] em-dashes [—], scientific symbols, and other things which I frequently use when I write. For some reason, his functionality has been completely disabled when I upgraded from Sigil ~1.6 to 2.02 last night. I have gone into settings and deleted all competing [Ctrl + foo] hotkeys, but it seems that simply having the program open and in focus takes complete control over the [Ctrl] key, in addition to the [Alt] and [Shift] keys. AHK never receives the commands in the first place due to Sigil 2.02. Any idea what is up with this? Perhaps this is a bug, or a disable-able feature in preferences? Much thanks!