ifstream crashes ui?
-
wrote on 23 May 2016, 19:02 last edited by
so do I just need to put this code into another thread and it wont lock up the UI?
https://gyazo.com/3c21a23cfe27f289b30aa35905ff749b QT
https://gyazo.com/7e5ffdd79d369009075a70af4247a7f2 VS2013 -
so do I just need to put this code into another thread and it wont lock up the UI?
https://gyazo.com/3c21a23cfe27f289b30aa35905ff749b QT
https://gyazo.com/7e5ffdd79d369009075a70af4247a7f2 VS2013wrote on 23 May 2016, 19:07 last edited by@timmie124 said:
so do I just need to put this code into another thread
That would be the easiest solution, yes. But you could also use a timer and look for new lines in the file every few milliseconds.
-
@timmie124 said:
so do I just need to put this code into another thread
That would be the easiest solution, yes. But you could also use a timer and look for new lines in the file every few milliseconds.
wrote on 23 May 2016, 19:08 last edited by@Wieland I'll give it a shot thank you!
-
wrote on 23 May 2016, 19:09 last edited by
@timmie124 :-)
-
wrote on 23 May 2016, 19:50 last edited by
Mayby just
QApplication::processEvents()? -
wrote on 23 May 2016, 20:26 last edited by
@michelson Yeah but then usage on one CPU core will stay at 100%.
-
Hi,
To add to @Wieland the QSocketNotifier class might be of interest for your use case.
-
wrote on 23 May 2016, 22:28 last edited by
I'd suggest QFileSystemWatcher too.
-
Hi,
To add to @Wieland the QSocketNotifier class might be of interest for your use case.
I'm with @SGaist,
QSocketNotifieris appropriate for such things.QFileSystemWatcherwill watch for changes in attributes or directory structure, but I don't believe it actually notifies on content changes, but I might be wrong. -
I'm with @SGaist,
QSocketNotifieris appropriate for such things.QFileSystemWatcherwill watch for changes in attributes or directory structure, but I don't believe it actually notifies on content changes, but I might be wrong.wrote on 23 May 2016, 23:40 last edited by@kshegunov said:
QFileSystemWatcher will watch for changes in attributes or directory structure, but I don't believe it actually notifies on content changes, but I might be wrong.
QFileSystemWatcher::fileChanged says:
This signal is emitted when the file at the specified path is modified, renamed or removed from disk.
It does detect file content changes on Windows (using FindFirstChangeNotification and friends) and on Linux (using inotify). It also has OSX and BSD implementations too, but I haven't looked into how they work.
QSocketNotifiermight be the better option, but I'd certainly consider both. It would be an interesting exercise to put together a minimal example of both options to compare their subtleties :)Cheers.
-
@kshegunov said:
QFileSystemWatcher will watch for changes in attributes or directory structure, but I don't believe it actually notifies on content changes, but I might be wrong.
QFileSystemWatcher::fileChanged says:
This signal is emitted when the file at the specified path is modified, renamed or removed from disk.
It does detect file content changes on Windows (using FindFirstChangeNotification and friends) and on Linux (using inotify). It also has OSX and BSD implementations too, but I haven't looked into how they work.
QSocketNotifiermight be the better option, but I'd certainly consider both. It would be an interesting exercise to put together a minimal example of both options to compare their subtleties :)Cheers.
It does detect file content changes on Windows (using FindFirstChangeNotification and friends)
Well, MSDN doesn't mention a notification for the file being written as far as I could see, beside perhaps the size change or the last write time attribute. I don't know how responsive those are, but I suppose
QFileSystemWatcheris a fair try.It would be an interesting exercise to put together a minimal example of both options to compare their subtleties
Indeed.
14/15