They took a copy of last VU’s code..berfore fixes were applied, and started to program new VU code to it..This explains why ALL the bugs fixed in the previous VU were not incorperated into this one. I image they have taken a copy of this VU as it is right now and are starting to code next VU changes. Then after they have all these constantly recurring bugs fixed in this VU, they will return as soon as they post next one. Because the fixes they eventually apply to this VU wont have been applied to the one they are working with for 7.9
I was thinkin the exact same thing. Kind of like if you write a paper and save it then spell check it then close without saving. Then you go back and add to it but all the spelling mistakes are back. Or maybe thats just a stupid explanation.
You are probably not wrong, when a software product is released it is locked down and coding begins on the next update. There can however be an overlap between old source code that is being updated in the new release that is no longer compatible with the previous relese so it then becomes necessary to update the old versions and the new versions simultanously. What often happens is that a quick fix will be applied to the old version and, as is human, is forgotten to be applied to the version in developmet. Its a common oversight in the software business.
