Skip to content
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

Great software, but #7

Open
SC20K opened this issue Nov 27, 2024 · 4 comments
Open

Great software, but #7

SC20K opened this issue Nov 27, 2024 · 4 comments
Assignees

Comments

@SC20K
Copy link

SC20K commented Nov 27, 2024

Its better to use universal path, i need to change location on different PCs
all works great thx

@mousedoc
Copy link
Owner

// INFO : Nox should be installed in D-drive
ExecuteLine(@"d:");
ExecuteLine(@"cd D:\Program Files\Nox\bin\");

So you want me to write down the information below that section?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or Other registry key

@mousedoc mousedoc self-assigned this Nov 29, 2024
@SC20K
Copy link
Author

SC20K commented Nov 29, 2024

// INFO : Nox should be installed in D-drive
ExecuteLine(@"d:");
ExecuteLine(@"cd D:\Program Files\Nox\bin\");

So you want me to write down the information below that section?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or Other registry key

I can imagine two situations where adb is used. The first is when you use the standard adb, which is installed with Android Studio or manually. It is located in the appdata folder, and variables are configured for it, indicating the path to adb.exe . That is why you can use adb from any directory using the command line.
The second situation is when you use noxadb. By default, no variable is created for it in the Windows system. To use noxadb, you either need to create a variable in the "Windows Environment Variables" or open the console in the /bin folder of the nox emulator.
In general, I propose to improve the program so that when it starts, it is suggested to use either adb from the appdata folder or noxadb. If the path to one of these programs is not found, the executable file should inform the user about how to solve the problem.
In addition, if the ports of the second or more devices start with 62025, you can set a variable with this value and increase it from 62025+1 to n, where n is the number of devices that the user enters when asked "How many devices do you want to use?". This will eliminate all the disadvantages of using the software so that people do not have to rewrite it for themselves every time. For example, I had nox specified in the user path on disk z.
I'm not calling you to action, just offering a convenient improvement so as not to force people to rebuild the program every time.
Thanks again for the software, it helped me a lot! :)

내가 사용하는 두 가지 상황을 상상할 수 있습니다. 첫 번째는 안드로이드 스튜디오 또는 수동으로 설치되는 표준 애드비를 사용할 때입니다. 이 폴더는 응용 프로그램 데이터 폴더에 있으며 변수를 구성하여 경로를 나타냅니다.엑스 따라서 명령줄을 사용하여 모든 디렉터리에서 애드비를 사용할 수 있습니다.
두 번째 상황은 노크사드를 사용할 때입니다. 기본적으로 윈도우 시스템에서는 변수가 만들어지지 않습니다. 이 경우 환경 변수를 변경하거나 콘솔을 열어야 합니다.
이 응용 프로그램은 당신이 당신의 안드로이드 전화 또는 타블렛에서 사용할 수 있습니다. 이 프로그램 중 하나에 대한 경로를 찾을 수없는 경우 실행 파일은 문제를 해결하는 방법에 대해 사용자에게 알려야합니다.
또한 두 번째 이상의 장치의 포트가 62025 로 시작하는 경우 이 값을 가진 변수를 설정하고 62025+1 에서 엔으로 늘릴 수 있습니다.". 이렇게 하면 소프트웨어를 사용하는 모든 단점을 제거하여 사람들이 매번 소프트웨어를 다시 작성하지 않아도 됩니다. 예를 들어,나는 디스크 지의 사용자 경로에 지정된 녹스가 있었다.
저는 여러분을 행동으로 부르지 않고,사람들이 매번 프로그램을 재건하도록 강요하지 않도록 편리한 개선을 제안합니다.
덕분에 다시 소프트웨어,그것은 나에게 많은 도움이! :)

@mousedoc
Copy link
Owner

mousedoc commented Dec 2, 2024

*I am not good at English, so this was written using Google Translator.

Thank you for the great suggestion.

I remember there was a case where Nox App Player did not recognize if adb was used, so I was forced to use nox_adb.

I'd like to reflect your request, but it's been so long since I made it that I can't...

It would be good if you could submit a Pull Request. Is that possible?

I will build and release it.

@SC20K
Copy link
Author

SC20K commented Dec 5, 2024

*I am not good at English, so this was written using Google Translator.

Thank you for the great suggestion.

I remember there was a case where Nox App Player did not recognize if adb was used, so I was forced to use nox_adb.

I'd like to reflect your request, but it's been so long since I made it that I can't...

It would be good if you could submit a Pull Request. Is that possible?

I will build and release it.

I have only basic knowledge of the c language, I'm afraid I can't handle this kind of work with the file system and the windows terminal in c#.
About the problem with nox and standard adb. I was able to solve it by running android studio, when we connect the nox emulator to adb, android studio stabilizes the connection itself and the device appears in the connected ones. It's enough to just keep android studio open. I am writing this because I think someone will be able to solve their problem just after the problem that you have already solved with searching for the device name. Have a nice day, thanks again for the software!

나는 파일 시스템 및 윈도우 터미널과 함께 이런 종류의 작업을 처리 할 수 없습니다.
에 대한 문제. 안드로이드 스튜디오는 연결 자체를 안정화하고 장치가 연결된 것들에 나타납니다. 그것은 단지 오픈 안드로이드 스튜디오를 유지하기에 충분하다. 나는 누군가가 당신이 이미 장치 이름을 검색하여 해결 한 문제 후에 문제를 해결할 수있을 것이라고 생각하기 때문에 이것을 쓰고 있습니다. 좋은 하루 되세요,소프트웨어에 대한 다시 한번 감사!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants