Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SystemConsole (aka NetDriver) appears to have broke
See original GitHub issueI figured I’d write a Scenario to illustrate Application.UseSystemConsole = true;
I immediately discovered I had to change how Scenario.Init, .Setup, and .Run worked. Which I did.
Then I couldn’t figure out why I was getting weird behavior and crashes.
So I modified demo.c to Application.UseSystemConsole = true; and ran it.
Crashed on startup.
I don’t have time to look at this now, but from what I can see nobody’s been testing SystemConsole for a while and it’s quite broken…
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Of course we are talking about the same thing. But at the time I tested NetMainLoop, it was not and is not as developed as WindowsDriver and CursesDriver, so as I couldn’t get it to work properly, I gave up and never looked at it again. This observation of yours, perhaps will enliven some work on it, who knows, if it is worth it.
I’m trying to get a list of bugs that must be fixed for 1.0. I don’t think anyone uses SystemConsole and thus would recommend we don’t mark this as 1.0. Any objections?