![]() to run a blocking function in a separate thread. For such a concurrency, there are better options e.g. However, I doubt that such a fiddling would be still necessary in Qt. This page is powered by a knowledgeable community that helps you make an informed decision. 'Scripting' is the primary reason people pick TinTin over the competition. (This was important for the situation where UI events were approaching in high frequency concurrently with the other event source.) TinTin , Mudlet, and MUSHclient are probably your best bets out of the 8 options considered. The most intricate thing was to achieve somehow a load balancing as I tried to distribute the available time equally between the UI and the processing of the other event source. Alternatively, timers can fire indefinitely. ![]() This is useful if you only need to do the timed event once. 10:30 a.m.) Timers can be once-off, which means they fire once and then delete themselves. every 10 seconds) or things that happen at a particular time (eg. Thus, the call of the poll function suspended itself the process until either an event came in or the timeout was reached. Timers let you set up periodic events (eg. ![]() Thereby, the polling function provided itself a time-out option. I intended to combine the UI event loop with polling "events" from a different source (and lacking any idea about a better alternative). I once used such an idle event in the past (before I started to use Qt). Thus, I expect the queue permanently filled with timeout and paint events (for update of qLblI) until the application exits. This means that a timeout event is appended to the event queue. The interval 0 makes the timer immediately due. QObject::connect(
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |