On Sun, Mar 3, 2019 at 10:56 PM Elvis Stansvik <elvst...@gmail.com> wrote:
> There should be no such delay in QFutureWatcher. I've never seen that, > and I've used QtConcurrent::run/mapped + QFutureWatcher quite a lot. > > I would investigate that before making my own mechanism. > I am on macos, on which OS are you doing it? I had the same issue for FileSystemWatcher, where on windows it was immediate and it was implemented on macos via polling. I was thinking that it may be the same issue for QFutureWatcher. However, if we exclude QFutureWatcher, is this approach good? could it be simplified? Also how would it be so different with a QFutureWatcher, it removes one class TaskNotifier, but the rest stays the same, do you see another way to make a action asynchrone? Best regards, Sylvain
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
