how 2 start?

Question

how 2 start?

Closed this issue 2 months ago · 9 comments

Deleted user commented 3 months ago

Answer 1 · 2024-05-23T13:01:25.000Z

edited constants.py

Fixed :)

Answer 2 · 2024-05-23T13:09:56.000Z

are these just unimplemented or smth

Answer 3 · 2024-05-24T20:11:23.000Z

Thanks for reporting. All the commands listed with help are implemented.

I updated the module to v0.0.4 on PyPI and fixed the bugs you've encountered above. If you reinstall the module in v0.0.4, all the issues should be resolved:

$ pip uninstall amiya -y 
$ pip install amiya==0.0.4

Once the installation is completed, run

$ amiya

And then follow this to add an application:

Quotes around the path don't matter. Not including the quotes will work as well.

To list all the apps added, run show-apps.

To delete an app that you don't want, run remove-app:

Unfortunately, the module is still in development so there will be bugs here and there. I'll add some documentation for this module sometime soon.

Please let me know if you need help or are encountering another bug (sorry in advance lol). I'm more than happy to help

Answer 4 · 2024-05-25T05:41:01.000Z

very nice, thx

btw, how 2 save recording?

i saw tkinter in the automation recorder but no gui shows up

Answer 5 · 2024-05-25T05:53:13.000Z

tried to not touch anything and got this even if the app launches

Answer 6 · 2024-05-25T18:45:07.000Z

That's strange. When running record-auto, the application should first start and then prompt you that the recording has started.
However, it seems that the module stopped after it tried to start the application.

Can you show me the output of running

$ amiya dev --isadmin

and then

$ amiya record-auto

I'll also leave some simple doc for these commands below.

To record an automation "sequence" of actions, run:

$ record-auto

Then follow the promoted steps to start a recording. Once the recording starts, a small window on the screen should pop up, indicating that the recording has started.

The recording will capture key clicks and mouse clicks. I'm still working on capturing a combination of multiple keys so only single clicks are supported at the moment

Once you are ready to stop the recording, click the "stop recording" button on the pop-up window. It will automatically save the recording.

To run the recording, run:

$ run-auto

OR

$ record-auto <app_tag> <sequence_name>

The optional arguments can be pulled up using run-auto --help. Those options are sometimes useful.

The module is smart enough to identify the application's window and ensure that the application is always focused during the run (or else it would stop automatically to ensure it's running on a different application).

The window size of the application also doesn't matter. It's capable of calculating the position of the mouse clicks even if the size of the window changes.

About the error where the app starts but shows that the application failed to start, I'll take a look at that today.

Right now, the module has a timeout of 30 seconds to check if the app started successfully. If the app's process doesn't initialize in that timeframe, it'll think that the app didn't start successfully.

Answer 7 · 2024-05-25T18:46:52.000Z

Also, if you have discord, I can add you there to help more efficiently.

Answer 8 · 2024-05-26T05:43:26.000Z

my discord is hcommak, ill record some tests in a few hrs

Answer 9 · 2024-05-31T04:04:12.000Z

Sorry, just saw your message over discord and replied to you there. Let me know if you need any other help or have any other suggestions.

I'm currently working on ver0.0.5 so if there's anything you'd like me to add, I'm more than happy to push them out in this upcoming version.