0
  • I start a visual studio project with debugging.
  • The console pops up, and I often accidently highlight something, which causes execution to pause until I unhighlight it ... I don't want it to pause ever unless I've set appropriate breakpoints.

I've tried looking around at the various options, but nothing seemed appropriate.

Jonathan
  • 2,778
  • 13
  • 23
  • This question is probably more suitable for Superuser as it is about Windows console behavior… – Alexei Levenkov Dec 13 '22 at 18:37
  • I'm not even sure how to even phrase the question, so it's a windows thing not a visual studio thing? – Jonathan Dec 13 '22 at 19:32
  • I found my answer @AlexeiLevenkov https://superuser.com/questions/1442941/windows-10-console-stops-running-if-i-click-in-the-console-window – Jonathan Dec 13 '22 at 19:43
  • In Windows, the console has 'QuickEditMode' enabled. You should turn this off. How to turn it off programmatically: https://stackoverflow.com/a/53391837/6725889 – Dang-gun Roleeyas Dec 14 '22 at 01:20

1 Answers1

0

This superuser response answers the question.

https://superuser.com/questions/1442941/windows-10-console-stops-running-if-i-click-in-the-console-window

Basically a change in behaviour since windows 10 where QuickEdit was enabled by default, so highlighting the console would cause the console to stop printing and pause the program. By disabling QuickEdit it will not longer pause.

Jonathan
  • 2,778
  • 13
  • 23
  • Hi, glad to know you've found the solution to resolve this issue! You can click '✔' to accept your answer. See [can I answer my own question..](https://stackoverflow.com/help/self-answer), Just a reminder :) It will also help others to solve the similar issue. – Jingmiao Xu-MSFT Dec 19 '22 at 04:12