Replies: 3 comments 1 reply
-
i'm not sure i understand how qt's event loop would conflict with notcurses? can you explain your reasoning? |
Beta Was this translation helpful? Give feedback.
-
I don't think there's any conflict between notcurses and Qt or any other event loop for that matter. (I managed to get it to work rather nicely with libuv anyway) To handle input, you can poll the file descriptor And as far as multithreading goes, afaik basically any notcurses function can be called from any thread, as long as only one thread does so at once. |
Beta Was this translation helpful? Give feedback.
-
I'm new to notcurses (so maybe I misunderstood), but I thought notcurses needs to own the main eventloop to handle background tasks. But my Qt apps require Qt own the main event loop (for timers, IPC, signals, etc . I thought that only one eventloop can exist per thread. (since it will never give control to the other event loop when idle). But maybe I've got that wrong.... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am building a Qt5 app, which uses timers and other event driven classes - and therefore need to use Qt's event loop. This would seem to conflict with NotCurses.
Has anyone integrated notcurses with Qt? Or even better, created a wrapper? I'm wondering if I could put notcurses into its own thread...but then still creates and event loop conflict.
Beta Was this translation helpful? Give feedback.
All reactions