EricofSD opened this issue on May 24, 2003 ยท 29 posts
EricofSD posted Sat, 24 May 2003 at 2:34 PM
CL did this before with the interface. It was SR1.2 or something like that. They accidently released one of the programmer's preferences on screen resolution rather than the default one. There was a brief thread in there about it and a fix the next day. Why did they make the same mistake again and why is it taking so long to fix it? And I'm on a 2.1 athelon with 1g ram and ATI 8500DV with an ASUS A7M266 board. As for the work around, what if I get all screwed up and have to go back to factory state to fix it like has happened before here? That means I have to go to high resolution where I can't see anything, move it around, yada yada? CL should just fix the damn thing so that we don't have this problem. Its not an odd "gotcha" for the programmers, its a known procedure for them and just sloppy work that they don't want to fix.