View Single Post
Copernicus's Avatar
Posts: 1,986 | Thanked: 7,698 times | Joined on Dec 2010 @ Dayton, Ohio
#982
Originally Posted by Estel View Post
Especially, the part about "syncing with flash" creeps me - big "no" for additional flash wear, where it isn't required (why Qt must be so lame in breaking so simple things?!).
I probably shouldn't be complaining about how Qt does its job. I think that Qt in fact does its best to minimize accessing persistent storage; I'm not entirely sure how often it syncs the in-memory representation of the settings with that on the disc (or flash in this case), but I know they avoid doing so when they can. Of course, what I really should do is to stop relying on QSettings as a crutch, and only store those values when I know the program is about to end. (Which, I guess, runs the risk of losing the data if the program exits in an unexpected manner, but that's probably a worthwhile tradeoff...)

It may also be a development trap - now you minimize damage to acceptable level, in a week you will add something to program, and chain reaction will make performance bad again, requiring minimizing damage again...
Indeed! But really, this is the fun part; I've always thought that finding ways to accomplish a given goal with fewer instructions is probably the most enjoyable part of coding...
 

The Following 3 Users Say Thank You to Copernicus For This Useful Post: