-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Audiotext.app in the downloaded folder #14
Comments
Hello. I just updated the project today and I haven't had the time yet to generate the executable file for macOS yet. I'll update this issue as soon as I upload it. Thanks for the feedback! |
OK sounds good! Thanks for the update! Looking forward to trying this ou! |
Hi @HenestrosaDev is this available now? |
Hi. Not yet, but I haven't forgotten about it. The last time I tried to generate the |
Looking forward to it!
…On Tue, Jul 16, 2024 at 10:19 PM HenestrosaDev ***@***.***> wrote:
Hi @HenestrosaDev <https://github.com/HenestrosaDev> is this available
now?
Hi. Not yet, but I haven't forgotten about it. The last time I tried to
generate the .app file, I ran into some errors generating the file that I
haven't looked into deeply yet. I'll update this issue as well as the
latest release with the file when I manage to generate it.
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMSQ2BH6QGYNPNT2AUOTSPLZMWE45AVCNFSM6AAAAABG4EZMJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZRHA2DKMZUGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This looks great! Excited to try it! I have downloaded the lastest 2.2 version and unzipped this on my Mac.
The instructions on the main page say:
"Open the audiotext folder and double-click the Audiotext executable file (.exe for Windows and .app for macOS)."
However these is no "Audiotext" Folder within the "v2.2.0" zip file when unzipped.
I did find in the root of that folder Audiotext.exe but not Audiotext.app
Thank you!!
The text was updated successfully, but these errors were encountered: