I note that when I change the MQ2HUD.ini file on disk it changes the display immediately. This implies that the program is hitting the disk every time it redisplays. The vast majority of the time, of course, this is unnecessary.
I'm not a C++ programmer, but couldn't there be a test of a global variable to see if this initialization is necessary? Or maybe do it once on initialization? Testing a boolean variable has got to be more efficient, each time thru, than reading a file and reparsing the entire display.
If you want to redisplay w/ the new parm in the file, it is easy enough to hit F11.
Just trying to save the much needed cpu cycles, yaknow?
I'm not a C++ programmer, but couldn't there be a test of a global variable to see if this initialization is necessary? Or maybe do it once on initialization? Testing a boolean variable has got to be more efficient, each time thru, than reading a file and reparsing the entire display.
If you want to redisplay w/ the new parm in the file, it is easy enough to hit F11.
Just trying to save the much needed cpu cycles, yaknow?