Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

Can't select new image to grab palette from.

1 replies · 842 views · Started 06 October 2007

This is actually most likely rather version un-specific. I'm in 626 though, trying to grab the Cset from an image I'd just ripped, and I find myself unable to select another picture to grab from. There is no visible File or Open button to choose another image from. Either that, or the actual ripping screen is influenced by the lack of color from the image, and none is visible. Even changing images to grab from in the Tiles Pages leaves us with the same image to rip from in the Palettes area with no method of changing images.

... or at least no obvious one. I'm going to try pressing "p" in the main ZQuest area.

EDIT: Nope. Same image; no way to change it to another image that I know of.

EDIT2: Ah, see, what's happening here, is that the entire File Button (Among the other buttons.) are being made invisible by the palette that's being ripped. Its color scheme is seeping into the GUI's, and making it invisible against the background.

The image is attached. See if you get a black screen with dark orange frames when ripping a Palette/Cset into the Main Palettes area.

(BTW, Props to you if you know where the image is from.)

I don't really see a good way to fix this. It's a limitation of using 256 colors and the Windows-like interface. Originally, the ZQuest GUI used 2 colors for the elements, so, when loading a picture, the gui used the lightest and darkest colors for the foreground and background. Now, it's having to try to pick out 6 colors and it doesn't do a very good job when there are so few to choose from.

I think any attempt to compensate for the palette issue (by moving colors around and consolidating them to free up gui colors) might result in the inability to rip palettes the way you want, due to the colors not being in the same place they are in the original image.

If/when ZC/ZQ moves to 15/16/24-bit mode, then this won't be a problem.

If no other developer objects, I'll classify this as "limitation/not a bug".