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
termbox demos don't run within ConsoleZ #58
Comments
Will take a look. Don't expect me to do it soon. All windows issues are resolved somewhat slower than others, simply because normally I don't work on a windows machine and right now I don't even have a Go setup there. But within a next week I'll take a look at ConsoleZ. |
No rush, just wanted you to be aware. I've forked the repo and will attempt to create a minimal test that fails, along with some logging to file since the terminal vanishes. |
I confirm the bug. Indeed things like Far Manager work fine under ConsoleZ, but termbox apps fail. Will look into it. |
I solved the problem. Basically the issue was with termbox-go creating a separate console screen buffer for itself. From what I see in other apps such as Far Manager and Emacs, they use existing buffer, but save and then restore some of its modes and parameters (such as cursor properties). So, I decided to redo all the windows initialization code to match these popular apps. However there are some things to check before I can commit the changes. Will commit the fix a bit later today. |
Should work now, please take a look. |
Seems to OK now. Thanks! |
I'm on Windows and am investigating termbox-go for a project. The demos run fine with a normal cmd.exe command prompt window, but don't work when the windows are within a tabbed console environment like ConsoleZ. Things work for a second, then appear to hang, and finally crash with the window tab going away and often a memory access error popup. I've never seen any go errors/panics.
This could be a ConsoleZ thing, but I've been running it for quite a while with other terminal applications and things have been OK.
The text was updated successfully, but these errors were encountered: