Closed kotenok2000 closed 8 months ago
This is intended and expected behavior, because many users who don't know how to use their OS (just like you) accidentally disabled output of logs to console by selecting one character, and complained that ASF is "stuck". If you would have a slightest idea how to use your OS - you would know that to select text you don't need quick edit mode! Just look:
And you don't even need to use menu like I did for demonstration, there is a convenient shortcut Ctrl+M (didn't fit to recording, and I'm to lazy to re-take it). That's exactly how I made a second selection in the recording.
Also, wow! instead of just typing it you scroll the windows and copy&paste it? Wow. Pro tip - there is a link to UI in ASF folder (you can even see in my recording, it's in the bottom), and since you seem to run asf manually - you can as well just double-click it. Even faster than typing, not to mention faster than copy&pasting.
As @Rudokhvist stated above, that's intended behaviour, and not something I'm willing to change, as quick edit mode in Microsoft stupidity has the capability to entirely freeze the process, without poor user even knowing that such thing has happened. ASF doesn't forbid you from manually re-enabling quick edit mode if you understand this limitation, on top of the fact you don't even need it like stated above, but even if you did, you can already do that. The default option ASF ships with isn't going to change though.
Checklist
ASF version
Latest stable release
ASF variant
win-x64
Bug description
When i try to copy webui endpoint urs i can't do it.
ASF forcefully unsets QuickEdit mode in console
It disables both wheel scrolling and ability to highlight text in window
Expected behavior
ASF doesn't unset QuickEdit mode
Actual behavior
ASF unsets QuickEdit mode in both windows terminal and classic console window.
Steps to reproduce
Possible reason/solution
No response
Can you help us with this bug report?
Yes, I can code the solution myself and send a pull request
Full log.txt recorded during reproducing the problem
Global ASF.json config file
BotName.json config of all affected bot instances
Additional info
No response