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
Have you considered to add multiple ncurses screen/window/panel support to the lib? Or is there some reason just not doing that? It's great so far, but it would be nice to have also pop-up windows, pop-up-menus and dialogs. Seems that now it's using the root main window (stdscr) for everything.
Maybe some RootWindow class using stdscr when initializing the app, and then maybe some central widget is given to the root which is actually a sub window for stdscr, and that handles widget childs as now. If you want a pop-up, insert a widget to the root or some other high level widget and the pop-up will be on top on everything below the pop-up widget? It might need some major refactoring, though.
-Matti
The text was updated successfully, but these errors were encountered:
I've thought about how to do this a few times, so it might happen at some point. It could probably be built without modifying the layout system, just generalizing the current single screen to multiple screens/windows that work the same as the current main window. The newer version of the library no longer relies on ncurses, so that windowing logic would need to be built into TermOx.
Hi,
Have you considered to add multiple ncurses screen/window/panel support to the lib? Or is there some reason just not doing that? It's great so far, but it would be nice to have also pop-up windows, pop-up-menus and dialogs. Seems that now it's using the root main window (stdscr) for everything.
Maybe some RootWindow class using stdscr when initializing the app, and then maybe some central widget is given to the root which is actually a sub window for stdscr, and that handles widget childs as now. If you want a pop-up, insert a widget to the root or some other high level widget and the pop-up will be on top on everything below the pop-up widget? It might need some major refactoring, though.
-Matti
The text was updated successfully, but these errors were encountered: