fix: use cwd option on executable-handler

[EduardoJM]

closes #16

as i commented in the issue, the OBS (and many other softwares) uses the current working directory (cwd) to find configuration and other files. Add cwd path as opening file options solve the problem.

[willianrod]

@EduardoJM Thanks for your contribution ;)

I just checked here and it's working as expected. I had an issue while opening CS:GO cs.exe but this happens because CS needs to open thought steam. I'm thinking a Steam integration where would be really easy to select steam game.

[willianrod]

Awesome. Good catch ;)

[EduardoJM]

I'm thinking a Steam integration where would be really easy to select steam game.

This is a really good. Do you know a way to do it?

[willianrod]

@EduardoJM Maybe using https://steamdb.info/ to do it. I'm working on refactoring all the handlers to be waaaay easier to develop new integrations, so I'm thinking on working on when the refactoring is completed.
I want to have the plugins implementation working before the hacktoberfest.

By the way, your PR will be merged this week, thanks again for the contribution. I'm organizing the project and making our goals more clear so more people can contribute

[EduardoJM]

This is really a good project and if your have more issues that is not blocked by the refactoring the handlers, i want to work on it.

[willianrod]

@EduardoJM have you worked with github actions? I really want to add CI/CD to build and release new app versions, because right now I'm doing it manually

[EduardoJM]

I worked with github actions to runs tests, to release packages to NPM/PyPI and to automatic deploy front-end's and back-end's in various providers. I can try to implement workflow to build and release the apps.

Maybe triggered by creating a new tag, and automatic create the release with the builded version?

[willianrod]

@EduardoJM thanks for your contribution ;)