You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Correct me if I'm wrong, but it seems that you can't enable mouse support when using views.Application? If I make a simple program with my own screen and event loop, I can receive mouse events perfectly fine... However this example using views.Application will not give the expected output:
The "Key Event" panic can hit as expected when typing, but the "Mouse Event" cannot be hit by clicking/scrolling. Also screen.HasMouse() is still returning true anyway
Does screen.EnableMouse() need to be called after screen initialization? That's how I was using it in my other tests where I didn't use views.Application.
If that is the case, then it seems that there's the issue that initializing the screen before passing it to Application.SetScreen() seems to break the application, since it also attempts to initialize the screen:
Correct me if I'm wrong, but it seems that you can't enable mouse support when using
views.Application
? If I make a simple program with my own screen and event loop, I can receive mouse events perfectly fine... However this example usingviews.Application
will not give the expected output:The "Key Event" panic can hit as expected when typing, but the "Mouse Event" cannot be hit by clicking/scrolling. Also
screen.HasMouse()
is still returningtrue
anywayDoes
screen.EnableMouse()
need to be called after screen initialization? That's how I was using it in my other tests where I didn't useviews.Application
.If that is the case, then it seems that there's the issue that initializing the screen before passing it to
Application.SetScreen()
seems to break the application, since it also attempts to initialize the screen:tcell/views/app.go
Line 128 in 761abf6
The text was updated successfully, but these errors were encountered: