It's getting busy! I did set up a little forum to try and split up this massive thread... at some point I'll see if people are willing to participate over there on the auspex.ca website. But at the moment it's still too basic for real people to use.

I deleted the Window commands, but interestingly with Auspex running AutoScriptWriter misses all those So, it'd be nice to be able to pause Auspex whilst doing such things then kick it off again (rather than quitting and restarting).

One other small thing... does the context menu from the Tray not work when the window is open??

It's getting busy! I did set up a little forum to try and split up this massive thread... at some point I'll see if people are willing to participate over there on the auspex.ca website. But at the moment it's still too basic for real people to use.

it doesnt seem to work with GridMove, no matter which setting I choose under exception...I only use the keyboard shortcuts for Gridmove - Win+G shows grid, then number key selects 'area'With Auspex running, and Grdimove in 'Block' / 'Compatability Mode' or 'Allow' mode, the Win+G combo doesnt work (the grid shows, but the start menu pops up and takes focus so I cant resize window).

Fixed in the next build (i.e. 58 or greater) which I shall release later in the week. A good catch, which has helped me further improve the program's compatibility with other applications.

I deleted the Window commands, but interestingly with Auspex running AutoScriptWriter misses all those So, it'd be nice to be able to pause Auspex whilst doing such things then kick it off again (rather than quitting and restarting).

One other small thing... does the context menu from the Tray not work when the window is open??

Woof. Are things improved if you set Auspex to ignore AHK? I'm actually not surprised there may be funnies going on there - both programs install a keyboard hook and intercept keystrokes between the keyboard and the screen.

No, it would appear the context menu is disabled when Auspex is not minimized. Can probably do something about that.

* When the tree list is refreshed, expanded nodes stay expanded * Numeric keypad keys 1 through 9 now trigger the appropriate Completion when it's popped-up * It's, again, a little faster and smoother * Stats will now tell you how many keystrokes you have saved, ever

Bug Fixes

* About screen shows the correct build information * Improved keyboard handling during very fast key action, such as rapid key repeat * ESC now only closes the Completion or Paste popup when they are showing, and does not pass the keystroke to the underlying application (which, in some cases such as Skype, closed the app window)

I've been getting this (because I didn't read carefully and so was using the regular number keys, not the numeric keypad. (see attachment in previous post)but after that, using the keypad '2' to select option 2 in the above produced (don't laugh) "comakerputeputeputer"

I've been getting this (because I didn't read carefully and so was using the regular number keys, not the numeric keypad. (see attachment in previous post)but after that, using the keypad '2' to select option 2 in the above produced (don't laugh) "comakerputeputeputer"

No, it doesn't.The same thing happens if I use exclusively the numpad keys.Using the completions in the image above, in a fresh run of Auspex, and adding a few spaces and a newline between each, gives:

com[tab] = companiescom[2] = companieputer

I've just this moment realized that this is happening in the Boxer text editor, in which everything that misbehaved elsewhere used to behave properly.The issue above doesn't occur in — wait for it… wait for it… Kedit!!It's fine in notepad.Okay, got it. I've had Boxer's autocomplete function enabled, which hasn't clashed previously with Auspex.The new number choices are being grabbed by Boxer, not Auspex.Turned off Boxer's autocomplete.Take another antacid and see me again in a week.No need for an English/Auspex — Auspex/English dictionary after all.

Okay, got it. I've had Boxer's autocomplete function enabled, which hasn't clashed previously with Auspex.The new number choices are being grabbed by Boxer, not Auspex.Turned off Boxer's autocomplete.Take another antacid and see me again in a week.No need for an English/Auspex — Auspex/English dictionary after all.

Ah ha! Whew. I wish it were possible to detect that sort of thing and back off, but I cannot find anything that will tell Auspex that there's already completion functionality in place. I suppose I could make the numpad a switchable feature. If that's of interest, plonk it in redmine for me and I'll be delighted to take care of it.

Next, I'll try and finish the search thingummy, and also the fuzzy feature.

I've been getting this (because I didn't read carefully and so was using the regular number keys, not the numeric keypad. (see attachment in previous post)but after that, using the keypad '2' to select option 2 in the above produced (don't laugh) "comakerputeputeputer"

Ok my 'tagline' did sound a bit pretentious - the thing that triggered the comment is my wife. She's a journo and has been helping me do a bit of testing. I discovered that she's set up a whole bunch of replacements to insert special characters into her documents that would normally have to be fetched from charmap. (e.g. she types 'quid' to get £, 'sayo' to get さよなら。 etc.) When I expressed delight at her genius idea, she just looked at me as if I were a bit dim, and suggested I make the tea.

I've been getting this (because I didn't read carefully and so was using the regular number keys, not the numeric keypad. (see attachment in previous post)but after that, using the keypad '2' to select option 2 in the above produced (don't laugh) "comakerputeputeputer"