Quote:
Originally Posted by
Saffith
ZC doesn't use polygon3d. The others might be relevant, but we haven't had any problems with them that I'm aware of.
I belive that it does...now. It's probably one of the things that I added, and Gleeok already added the ZASM-end stuff for all the drawing functions, unless this change has nothing to do with the polygon3d drawing primitive.
Quote:
It just sets a variable that users can check if they're interested. It doesn't do anything on its own.
Quote:
They did integrate AllegroGL, which would be nice to have, assuming it will just work without additional effort. Gleeok attempted to integrate it before, and that didn't go well at all.
They seem to have done a fair number of tweaks to do with gfx libs. I'm hoping that between those, and the input vchanges, some of our longstanding bugs may have been resolved. I'm not in deep enough to know precisely what's causing them.
Quote:
Fullscreen doesn't work on Mac, anyway, and that's not changing soon.
What is the present reason for that, though?
Quote:
No, that's a minor input issue. Might cause you to open a menu accidentally, but that's about it.
I noticed a group of fixes relating to input. Had you ever worked out exactly what causes loss of input, and what causes random input when ZC is defocused on Windows with alt+tab (and only alt+tab does this)?
Quote:
It might help with Allegro itself, but there are other libraries that are still stuck in 32-bit, so that doesn't do us any good.
Probably true. Grayswandir has been trying to compile on his Linux system, and he's had no success at all, even when he forces a 32b compilation, so these changes might resolve that.
Quote:
Eh. It could, in theory, but no one uses OSS anymore, and I don't think anyone's ever gotten it to use an external MIDI driver successfully.
I'm more interested in expanding the nsf formats that we can use. The expanded chipset types, don't work at present, and I've never looked at what we use for that. Adding .sid support would also be nice, for that matter.
Quote:
You can check
the commit log. They really didn't leave out anything interesting.
I'll do that, but only the forum posts, and any usenet stuff, might have everything. As I don't know exactly what causes each issue that we have at present, i just think it prudent to update, and rule out that the allegro changes may have fixed things, before making hacks around the bugs.
Quote:
Compilation stuff doesn't really matter. We don't have problems with that. Anything to do with the console driver on Linux or the GDI driver on Windows isn't relevant.
It does, when gcc won't compile due to kernel issues when compiling ag 4.2. Feel free to ask Grayswandir about those; and as I'll likely end up doing the OSX builds in the future, I would like to have as much of the resolved OSX issues, well, resolved before I need to drink meself into oblivion, trying to figure out why things don't work.
Quote:
There's no chance of a PSP port in the foreseeable future.
Do we use external binaries with no source, that we can't compile on other arcitectures? Really, what is the main limiting factor with this one? Input differences? System resources?
I don't even own a PSP, but if it was possible to compile a PSP-specific ZC build, even a 'light' version, I might consider working on it. I do have enough on the plate for the present though.
Quote:
Hard to say. I'm not unwilling to give it a try, but it doesn't look to me like a high priority, and it's more than just a few minutes of work even if everything goes smoothly.
If you feel up to it. I had it on my agenda for a while, so I will eventually get around to it, once I finish the zscript, and lexer stuff that I'm working on at present. If all goes well, I may have added case-switch; but I anticipate quirks. Comment blocks, likewise may be viable now, but I won't know until I test them, and I need to marge some of my changes with what Gleeok has done, and see if all is right in the world.