On Tuesday, 8 de February de 2011 00:44:48 Arno Rehn wrote: > On Monday 07 February 2011 23:25:02 Thiago Macieira wrote: > > On Monday, 7 de February de 2011 10:05:39 Aaron J. Seigo wrote: > > > On Monday, February 7, 2011, Arno Rehn wrote: > > > > shame if that feature went away I think. And I find it hard to > > > > imagine how many QFiles you would need to create to actually > > > > notice the drop in performance. > > > > > > as i said, talk with Qt devs. it's apparently enough of a pain that > > > there is a desire to get rid of the file engines in their current > > > form. mobile makes this particularly an issue from what i > > > understand. > > > > Applications that instantiate file engines (beyond the default ones from > > Qt -- the FS one and the Resources one) may suffer performance penalty > > from 4.8 onwards. > > > > Applications that don't do that will instead see performance > > improvements > > in accessing the filesystem. > > If this only applies to the actual file engines, my code snippet shouldn't > be affected by this. It only creates a handler, which returns the usual FS > file engine. No custom file engine here.
Then it will still create a performance impediment.
You must not add a handler if you want it to be faster. You must let QFile
open the file directly.
Adding a search path, however, is ok.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
