Jonathan wrote:
I'm using the float-only version of Xfractint, which has been indented. However, Xfractint has had the problem for quite a while.
I don't know if this is good news or bad news. I grabbed the latest float-only source, dumped unpacked in in a clean directory in the current Mandrake, type "make", and ran it with boundary tracing. I couldn't debug your problem ... because there was no problerm to debug. Boundary tracing works perfectly for me. As an ironic side note - it has been a long time since I have tried boundary tracing, and it is no fun at all any more. My computer is too fast! :-) The fun in boundary tracing is watching it work. On my (not really the state of the art) 650 mhz computer, the default Mandelbrot renders almost instantly. I had to bump up the resolution quite a bit to see that I was really using boundary tracing. I wish I could see the problem, because it looks to me like it is easy to debug. I checked that the enum values North, East, South, West had the correct values of 0, 1, 2, 3, and checked that the macros were working. I'd just instrument the code each time the coming_from variable is set, and stop in the debugger the first time it is out of range. Then check the values used to calculate it. Alas, I can't see the problem, so I can't fix it. Maybe I need to try on my laptop? What machine are you running on? Perhaps the video driver is making it hard for Xfractint to recover pixels from the screen. Tim