-------- David W. Jones quoted Jonathan as saying: -------------
Once I get all that straightened out, the Windows code (32-bit) will be a whole new learning experience. Some due to idiosyncrasies mandated by MS. Others due to different variable sizes and pointer sizes. Jonathan, I'm willing to do any regression testing of SDL Fractint you would like done under Win10. I do not have Linux here.
- Hal Lane ######################## # hallane@earthlink.net ######################## -----Original Message----- From: Fractint <fractint-bounces@mailman.xmission.com> On Behalf Of david Sent: Thursday, May 10, 2018 5:51 AM To: Fractint and General Fractals Discussion <fractint@mailman.xmission.com> Subject: Re: [Fractint] Status of SDL XFractint? On 05/09/2018 10:23 AM, Jonathan Osuch wrote:
David,
Greetings, Saint Jonathan!
Just wondering. Haven't seen anything since 12/26/2017. Still alive and progressing?
Yes, but slowly. Still working with the Linux version (64-bit). I have the fast mandelbrot code working, but if you have it as the default fractal when you start Fractint, it crashes.
Something not being initialized properly before it starts processing the formula? I use another program, Hugin, that used to crash on opening a project if the option to use an optional element of one window - but only if you were using the OpenGL side of it. The team finally figured out that the program was trying to use OpenGL before initializing OpenGL, but only when it tried to render that particular element.
It will also crash with key strokes (but not consistently).
Hmm. I could guess a lot of things but I'm no programmer, so they'd only be generalities you've already looked at.
I have also been working on the fast formula parser, but it currently crashes before an image gets generated.
Ouch. But it appears that the Fractint formula parser is the thorniest nest of thorns in Fractint, yes?
There are several problems that I don't yet have a handle on.
The syntax between MASM (old) and NASM (new) is different enough (and similar enough to be confusing) that it isn't always obvious how to change the code. NASM doesn't always seem to function as I would expect.
The interface between the 64-bit C code and the 64-bit assembly is not defined as well as it could be in the NASM documentation.
Well, let us know when you have another release to test!
Once I get all that straightened out, the Windows code (32-bit) will be a whole new learning experience. Some due to idiosyncrasies mandated by MS. Others due to different variable sizes and pointer sizes.
Can't test that unless it's something that would run under Windows XP or WINE. Don't think I could prevail upon my wife to let me use the Windows 10 side of her laptop (she runs Linux instead) enough to do any real testing. Thanks for your work, looking forward to updates! -- David W. Jones gnome@hawaii.rr.com authenticity, honesty, community http://dancingtreefrog.com _______________________________________________ Fractint mailing list Fractint@mailman.xmission.com https://mailman.xmission.com/cgi-bin/mailman/listinfo/fractint --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus