As a tester myself, I have to agree with James here. The font color problem is really one that Abacus needs to address somehow. The dev team cannot try to anticipate what a 3rd party developer may try to do, nor is it really there job to try. This is a scenario where Abacus should contact MS directly to try and find a solution. If Abacus just simply blames MS, then it's out of line in my opinion. It's kind of like complaining to GM because the stereo you bought from a third party supplier only works with 6 volt reverse polarity vehicles <g>.Maybe I stated it a bit offensively, for which I apologize. I had mentioned to them that the two add-ons would benefit from a modification letting the user set the font-colour (and thinking of it now, perhaps even the font itself) to eliminate confusion. They said they had spent about two months on the problem, and that their best ability to determine why the colour seemed to be locked was that it was an integral part of the programming. They were not really blaming MS, although I am not sure if they have contacted MS for a work-around either.
I just said that I would check and see if there any thoughts by the folks who had been part of the beta-test (and had been posted on the topic during the test phase). In the event it had been mentioned, there might be a way to point them in their fixing it.
Sure, they need to probably contact MS (and probably would be better, as they have a history of providing 3rd party addons), but I thought I would help out if I could.
"TD - Virtual FAA investigators are on line 2, AGAIN!!!
Printer-friendly
version of this topic
Bookmark this topic
(Registered users only)
FSFORUM
![[Guest]](http://www.flightadventures.com/Forum/htdocs/dcforum/Images/key-s.gif)
![[Sysop]](http://www.flightadventures.com/Forum/htdocs/dcforum/Images/3bar.gif)
![[Admin]](http://www.flightadventures.com/Forum/htdocs/dcforum/Images/4bar.gif)