Simizfo
Any plans for "Debug Mode"?
Hi there.
I'm considering that if some users uses WSATools with any experience with ADB, they can just check if there's any errors or not. Something from the ADB commandline output can be also appreciated if you're planning to do that.
Debugging can be used for adb, as I didn't see any command prompt stuffs from WsaClient.exe.
Just a suggestion. You can add it if you want.
This is a good suggestion!
Will definitely think about this and add it at some point 👍
If anyone wants to partecipate in this discussion, I'm leaving this issue open until it's implemented
Debugging can be triggered after start install - by making a button called "Log" / "Debug" after clicking "install". Something similar to what installation packages uses - notably NSIS, where a log will be shown below the progress bar.
Turning on is optional, so you don't have to force open it. Plus, it's more better for error stuffs where you can tell the user who submitted the issue to copy the log.
Exporting the log to a text file is also highly appreciated.
This is almost exactly what I thought it would look like!
The only difference being that my "log" would appear on a separate window, much like Rufus does
Not quite sure about UWP restrictions, but I think they could allow a second window to pop-up or something like that.
Anyways, the separate window thing is a good idea, since I used Rufus before, made bootable disks, and always used the log window to troubleshoot errors or something like that. Need to ask, can ADB enable something like "verbose" debugging? All I can see on the command prompt stuff is like:
Performing streamed install
Done
By the way, if you're planning to implement this, you can "tag" the app names in the logs (not sure how to say that). Examples include:
[xcopy] Dec 29 2021 09:45:00 Copying files
[adb] Dec 29 2021 09:45:12 Performing Streamed Install
which follows the formula of [(process name)] (time) (command output?)
UWP allows for multiple windows, yes
ADB verbosity needs to be checked, I have no idea to be honest. Tagging lines will be important!
If you're implementing dates please add European format support somehow!
(Today is 04/01/2022 for example)
Or just use the system date...
If you're implementing dates please add European format support somehow!
(Today is 04/01/2022 for example)
Or just use the system date...
Or even better, just use what the system shows. (that one time at the bottom-right corner), which, in batch, you can output this kind of time with echo %date:~4,11%. (You can arrange the 4 and 11 to a more suitable amount?)
If you're implementing dates please add European format support somehow!
(Today is 04/01/2022 for example)
Or just use the system date...
Or even better, just use what the system shows. (that one time at the bottom-right corner), which, in batch, you can output this kind of time with
echo %date:~4,11%. (You can arrange the4and11to a more suitable amount?)
That's what I meant with
System date