Sender | Message | Time |
---|---|---|
19 Sep 2023 | ||
Bawdy Ink Slinger joined the room. | 20:23:39 | |
2 Oct 2023 | ||
@temp4096:matrix.org joined the room. | 14:02:21 | |
3 Oct 2023 | ||
@temp4096:matrix.org left the room. | 09:51:16 | |
8 Oct 2023 | ||
drmfinlay (Dane Finlay) | Hello all, A new release candidate for Dragonfly version 1.0.0 is now available. It contains a number of bug fixes and other improvements. Please see the changelog for the full list of changes: https://dragonfly.readthedocs.io/en/latest/changelog.html You can install this version by running the following command:
The previous release name for this library, dragonfly2, may be used instead. I would like to state here that Dragonfly version 1.0.0 proper will (probably) be the next and final version of this library. | 10:24:45 |
LexiconCode | @drmfinlay (Dane Finlay) have you considered posting on the repository to advertise posting looking for a new maintainer. That way you can pass on the torch if there's an interested party. | 16:24:17 |
9 Oct 2023 | ||
drmfinlay (Dane Finlay) | Well, it is my hope that Dragonfly won't need to be updated after version 1.0.0. The library doesn't need any more features and doesn't need to support any more platforms or speech recognition engines. It should be basically complete at that point. That is the ideal, any way. I'm still happy to fix bugs that pop up, improve the documentation, and help users with questions or problems. So, I should clarify that version 1.0.0 will probably be the last major/minor update. There may still be patch updates, e.g. version 1.0.1. | 07:18:31 |
heaven886 joined the room. | 16:41:56 | |
1 Nov 2023 | ||
77 capr joined the room. | 04:01:52 | |
8 Nov 2023 | ||
alexboche (Alex Boche) | Redacted or Malformed Event | 21:50:36 |
11 Nov 2023 | ||
Light_Fiber joined the room. | 15:32:59 | |
Light_Fiber changed their display name from light_fiber to Light_Fiber. | 20:21:50 | |
Light_Fiber | Greetings. I need to use Parsec for work, and I have been noticing various issues with it and Dragonfly. On Windows, Dragonfly uses SendInput to simulate input events. But it looks like Parsec just doesn't seem to recognize SendInput at all. I also tried with AutoHockey which uses SendInput and had the same problem. I'm currently using Dragonfly 0.35, but it seems like the current source code has support for routing the input events through Natlink. I would like to try this as a workaround but I'm not quite sure how to do that. The readme on the repository says that Dragonfly can be downloaded from the releases page, but there are no releases. Is the only option then to clone the repository? | 21:12:46 |
Light_Fiber | * Greetings. I need to use Parsec for work, and I have been noticing various issues with it and Dragonfly. On Windows, Dragonfly uses SendInput to simulate input events. But it looks like Parsec just doesn't seem to recognize SendInput at all. I also tried with AutoHotkey which uses SendInput and had the same problem. I'm currently using Dragonfly 0.35, but it seems like the current source code has support for routing the input events through Natlink. I would like to try this as a workaround but I'm not quite sure how to do that. The readme on the repository says that Dragonfly can be downloaded from the releases page, but there are no releases. Is the only option then to clone the repository? | 21:13:12 |
LexiconCode | Light_Fiber: you go into the release section of pypi for the dragonfly2. There are pre-releases that don't show up under the latest release. 'pip install dragonfly2==1.0.0rc2' | 23:42:23 |
Light_Fiber | Oh, so will that upgrade my current install or do I need to uninstall first? | 23:44:42 |
LexiconCode | You can try to invoke input events for keyboard and mouse but I imagine you'll have the same type of problem as described https://github.com/dictation-toolbox/natlink/issues/176 ''' from dragonfly.actions.mouse import ButtonEvent ButtonEvent.try_natlink = True ''' | 23:45:03 |
Light_Fiber | Isn't that only an issue with Dragon NaturallySpeaking 16? I'm still on 15. | 23:46:07 |
12 Nov 2023 | ||
drmfinlay (Dane Finlay) | Hello Light_Fiber , It is indeed possible to route input events through Natlink with Dragonfly. Downloading the repository is unnecessary; this feature is available in the release candidate for version 1.0.0. The project README and documentation are both less than clear on this. My apologies. I'll update both shortly. The feature should work on DNS 15. There are some caveats, however. They are mentioned in the latest documentation: https://dragonfly2.readthedocs.io/en/latest/actions.html. | 00:42:57 |
drmfinlay (Dane Finlay) | * Hello Light_Fiber , It is indeed possible to route input events through Natlink with Dragonfly. Downloading the repository is unnecessary; this feature is available in the release candidate for version 1.0.0. The project README and documentation are both less than clear on this. My apologies. I'll update them shortly. The feature should work on DNS 15. There are some caveats, however. They are mentioned in the latest documentation: https://dragonfly2.readthedocs.io/en/latest/actions.html. | 00:44:56 |
drmfinlay (Dane Finlay) | * Hello Light_Fiber , It is indeed possible to route input events through Natlink with Dragonfly. Downloading the repository is unnecessary; this feature is available in the release candidates for version 1.0.0. The project README and documentation are both less than clear on this. My apologies. I'll update them shortly. The feature should work on DNS 15. There are some caveats, however. They are mentioned in the latest documentation: https://dragonfly2.readthedocs.io/en/latest/actions.html. | 00:46:25 |
Light_Fiber | In reply to @danesprite-5a669b15d73408ce4f89a273:gitter.imThank you. If you are going to update documentation, I should point out that the installation instructions specify dragonfly, rather than dragonfly2. | 01:45:06 |
drmfinlay (Dane Finlay) | You're welcome. Yes, the dragonfly vs dragonfly2 package names are confusing. I'll make this clearer, too. | 04:32:49 |
Light_Fiber | Sounds good. | 15:34:19 |
Light_Fiber | Okay, here is the report for my experiment with Dragonfly 1.0.0 rc2 with Keyboard.try_natlink = True and Parsec. Unfortunately, it seems that routing the input through Natlink still does not produce any input in Parsec. This was surprising to me, considering saying "press key_name" does work correctly in Parsec (with the exception of the Windows key, at least). So it seems that playEvents does not use the same input mechanism as the "press key_name" command does. As mentioned in the caveats, modifiers do not always work as expected, making this limited in usefulness anyway. | 17:33:34 |
13 Nov 2023 | ||
drmfinlay (Dane Finlay) | Hmm. Thank you for this information. I've never used Parsec, but it seems to be one of those difficult programs that doesn't respond to certain types of simulated input. You wrote earlier that AutoHotKey (AHK) didn't work either. It does however have several modes for sending keystrokes. Perhaps you could try the AHK | 00:15:58 |
Light_Fiber | That's an interesting idea. Through my work I'm trying to get Parsec to support SendInput, but it can't hurt to try this as well, as a potential workaround. | 00:19:03 |
drmfinlay (Dane Finlay) | Well, whatever works, right? | 00:43:15 |
drmfinlay (Dane Finlay) | It might just be an administrative access issue. You could try loading your Natlink/Dragonfly command modules with Python running in elevated mode (as administrator). | 00:45:36 |
Light_Fiber | It is possible. I don't think I have tried testing with another elevated program. But they didn't come out and say that that was the issue, so I can't be quite sure. | 01:34:48 |
drmfinlay (Dane Finlay) | Okay then. If you'd like to try anyway, I can walk you through loading your command modules with administrative access. This is another thing that needs to be better documented, but it is not too difficult. | 03:38:49 |