Closed Zarthus closed 1 month ago
I'd say the changes to the API are done for now. At least I don't have any other ideas on how to improve it. I'd like to add basic libei support to give people an incentive to switch to the new version. Other than that, there aren't any other plans. This is just a hobby project and I don't earn any money from it so I don't have a proper release schedule.
Yeah that's okay :) I just saw the RCs hanging around and was wondering if they were just loosely hanging around or of there was overarching goal needed to be complete (or testing done on it)
I was hoping to get some feedback on the changed API. So far nobody has complained, so I guess it is fine
I liked the overall changes. Converting my project from 0.1 to 0.2-rc2 was relatively simple with the instructions in the docs, the only thing I needed to strictly reason about was enigo::Direction::*
- for most things the conversion was intuitive, for somethings like key_down
-> Direction::Press
it took a second of reasoning about it, but it only took one iteration of testing before functionality was 100% identical to the 0.1 revision.
That's not necessarily a complaint. Just my experience. Overall I like the changes.
Thank you for the feedback. I am glad you mostly like them.
If you can think of a better name, let me know. I am always open for suggestions
I published the new version. The experimental features still have a lot of bugs, but I can improve them in the next minor versions.
Describe your Question
There doesn't seem to be an issue to track the work on 0.2 or a future release,
Presently, there is a release of 0.2-rc1 and 0.2-rc2 that have been out for a while.
My overall question is - how are we doing on a release? It seems like a lot of work is being done, and the API has changed since 0.1 and 0.2-rc2. Do we expect more changes from rc2 (which has been a while ago) or is it considered pretty stable?
Describe your Goal
This issue could function as documentation on the current state of an upcoming release.