make playEvents obsolete for Dragon16

[quintijn]

Nobody seems to be able to implement natlink.playEvents into python. Let us declare this function obsolete with Dragon 16.

[drmfinlay]

This makes sense given that you want to release a new version soon. I'll have another go at writing a Python version of `playEvents' (re: #176, #196 assigned to me) or fixing the C++ code sometime in the future. I figured focusing on issue #198 was a better use of my time.

…

On Tue, 30 Jul 2024 05:34:40 -0700 Quintijn Hoogenboom ***@***.***> wrote: Nobody seems to be able to implement natlink.playEvents into python. Let us declare this function obsolete with Dragon 16. -- Reply to this email directly or view it on GitHub: #200 You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[quintijn]

Let us keep this issue open and close #196 (and #176 was already closed).

[drmfinlay]

Now that I have Dragon 16 I am able to reproduce the ESP error with playEvents() and playString(). Strangely, Dragon does type the specified keys, but only after clicking "Retry" or "Abort" on the dialog box that appears. This is when I use these functions from a separate python.exe process.

I'll have a look into this further sometime. The installer issues are more pressing for the moment, of course.

[drmfinlay]

Quintijn, I believe that both of the above functions could be fixed by using execScript() internally. Shouldn't be too difficult.

[quintijn]

Hi Dane, I agree that fixing playEvents would be a good thing, although not extremely important.

About playString: as it is now a python function intercepts this function in {natlink}\pythonsrc\natlink_init_.py around line 77.

Without hook (the additional parameter): do a normal sendkeys (and yes, we need the dtactions module as well. Dragonfly does the same somewhere I think).

With a hook, interpret as "sendsystemkeys" and invoke via natlink.execScript. All the other hooks (capitalizing a word for example) can be dismissed.

This way, playString is available with a few changes (ignoring most hooks).

But when you want to get rid of this python interception trick, all has to be done in C++. That is outside my scope...

Quintijn

[drmfinlay]

Thank you for the above information, Quintijn. I think that moving the natlink\__init__.py code into the C++ layer is probably not worth it, especially if the in-process mode is removed.

In any case, Aaron has managed to fix the ESP error with these functions in PR #225. The fix is imperfect though.