I don't think it's a good idea to try to fix QStorageInfo. The main argument is that QStorageInfo is a monitor+info provider, but monitor should depend on a DBus in Linux; however info provider doesn't require that. Also, monitor requires internal thread on Mac. My point is that in many cases, when you doesn't need monitor itself, it's too heavy to create such a huge object just to receive volume info.
That's why i separated my solution into 2 different classes; so QtDriveInfo doesn't require external dependencies, like DBus. Next, QStorageInfo notification doesn't work for MingGW and Windows CE. Also QStorageInfo doesn't have internal caching. Иван Комиссаров 01.03.2013, в 12:51, Laszlo Papp <lp...@kde.org> написал(а): > On Fri, Mar 1, 2013 at 8:42 AM, André Somers <an...@familiesomers.nl> wrote: > Wasn't there already similar functionality in QtMobility? > QSystemStorageInfo seems to provide similar functionality? Or did all > that get scrapped in Qt 5? > > Ah, you are both right: > http://qt.gitorious.org/qt/qtsystems/blobs/master/src/systeminfo/qstorageinfo.h > > I just tried to build QtSystems against Qt5 (dev), but I am getting build > issues. See the details below. I believe those are fixable, so perhaps Ivan > should check if something is missing? Any plans to bring this back for Qt 5.2 > or later? > > Actually, since it is not yet released with Qt5, even API issues can be fixed > in there. > > Laszlo
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
