Users of the Traffic and Parking Analyser may wish to update Development Release 3.2.01(b), which I have just uploaded to http://stuff4fs.com. It fixes the Traffic and Parking Analyser parking type counters which were not being initialized when a new airport was selected. This was a "Day 1" problem. It also fixes a problem which prevented selection of an add-on airport for analysis when that airport was in a \scenery folder with other airports.
It's unfortunate these issues weren't noted prior to general release. They would have been evident in several earlier development releases and, had they been reported earlier, would have been fixed in the general release.
It seems each new general release prompts a flurry of local testing activity by users. There seems to be a phobia about using development releases other than by those who first experience the difficulty fixed by the development release. Development releases should not be viewed as experimental. They are seldom that. They should, instead, be viewed as candidates for general release and, while not always the case, usually, are as stable as the preceding general release.
When a bug is reported and isolated - whether in a development release or a general release - it is usually fixed in a development release within 24 hours. So, if you use development releases, you get almost immediate support. If you use only general releases, it may be weeks before a bug fix is available because I only make general releases after a period of stability of the last development release. Any bug that is discovered in a general release could have been found in a development release - and fixed earlier - prior to the general release.
You can be advised of development releases as they occur by checking the Check for Updates at Startup - Development Releases item in Options menu. Whether or not you install them is up to you. I would hope that a few more of you power-users would do so.
Don
It's unfortunate these issues weren't noted prior to general release. They would have been evident in several earlier development releases and, had they been reported earlier, would have been fixed in the general release.
It seems each new general release prompts a flurry of local testing activity by users. There seems to be a phobia about using development releases other than by those who first experience the difficulty fixed by the development release. Development releases should not be viewed as experimental. They are seldom that. They should, instead, be viewed as candidates for general release and, while not always the case, usually, are as stable as the preceding general release.
When a bug is reported and isolated - whether in a development release or a general release - it is usually fixed in a development release within 24 hours. So, if you use development releases, you get almost immediate support. If you use only general releases, it may be weeks before a bug fix is available because I only make general releases after a period of stability of the last development release. Any bug that is discovered in a general release could have been found in a development release - and fixed earlier - prior to the general release.
You can be advised of development releases as they occur by checking the Check for Updates at Startup - Development Releases item in Options menu. Whether or not you install them is up to you. I would hope that a few more of you power-users would do so.
Don