quoting:
I know waht you feel, I find this all the time you simply add a small addition (like glClear) and then nothing works. Sometimes you can then remove that line you added, recompile and find it still doesn’t work!
Sorry no answers
hello. well, it could very well be a non-opengl related issue, althogether. It might be something seriously wrong with some other part of your code thats effects are trickling down. Now, I know that sounds very x-filesish and freaky, but it IS possible. an example, if you will. consider the code fragment:
int i, arr[10], j;
for(i=0; i<=10; i++) arr[i]=0;
now, the bug is that it should be i<10, not i<=10. but, this code might work in this case because its setting the array to 0, but then stomping all over the j value (because the int decl is placing 12 integers onto the stack, and although arr[0]=arr[0], its very likely that &(arr[-1])==&i and &(arr[10])==&j). but this WILL compile and it will more than likely run without side-effects. but, suppose you come back a millenia later, and change the decl so the code now reads:
int j, arr[10], i;
for(i=0; i<=10; i++) arr[i]=0;
you’ll likely find that your code hangs at the for loop. (see… arr+10=&i… which is the loop counter=)
my point is: by changing some other part of the code, you’ll find that your errornous code ELSEWEHRE in the program will start behaving differently.
but, this isn’t to say that glClear is buggy, but that if you start changing your code, the memory alignment might be screwed up in JUST the unfortnate case to start screwing around with working parts of yor program. windows isn’t the most protected o/s in the known market, after all. true, it seems more unlikely given that glClear lives in a DLL somewhere, but… its POSSIBLE.
cheers,
John