is it possible to suspend explorer.exe processes as ZC launches?

[Nicholas Steel]

I giggled a little at that snippet. Can you perhaps log the results of the code snippet? Anyways I've noticed something for Zquest, the entire screen is either tinted white with the default DLL or entirely tinted pink by your modified DLL. The tint goes away after the initial dialog box but dialog box title bars are still rainbow coloured. Zelda-w.exe hasn't changed.

Image 1 = original DLL with faded white tint over the whole screen. Phone camera kinda sucks and our proper camera is worse but probably because it is flat ._.

Image 2 = Modified DLL with pink tint.


Zquest is in fullscreen mode as it is only fullscreen modes for Zelda-w and Zquest that are affected. I doubt many use Zquest in Fullscreen though.

[Saffith]

I giggled a little at that snippet. Can you perhaps log the results of the code snippet?

Eh, no good. It just responds with WM_NO_U, and handling that creates an infinite loop.


I think I've been going about this completely the wrong way... I don't think it'll work quite right, but what does this one do? http://www.mediafire.com/?ainkz4mzkmy (It might just hang the game, so be ready for that.)

The problem with the new quest dialog may be unrelated. There seems to be an uninitialized bitmap being used there.

[Nicholas Steel]

That fixes the new quest dialog screen tint but title bars still have a rainbow colour. It has no effect on ZC.

[Saffith]

This one looks promising: http://www.mediafire.com/?2tofynee0t3

If it screws up again, not counting ZQ's new quest dialog, post allegro.log afterward.
Even if it does work, it's overkill and should be whittled down, but that's not a big deal.

[Nicholas Steel]

FUCK YES! That solves the colour problems in full screen modes!

I'll do a bit more in depth testing (aka: extended play session) but it looks very promising.



edit: maybe get Freedom's attention

[Gleeok]

Cool. :)

Just curious what the deciding code was.

[Saffith]

Turns out a lot of the information out there about this problem only applies to GDI applications. Apparently, this is all it needs:

      case WM_QUERYNEWPALETTE:
      case WM_PALETTECHANGED:
         if ((HWND)wparam != wnd && gfx_directx_primary_surface) {
            IDirectDrawSurface2_SetPalette(gfx_directx_primary_surface->id, ddpalette);
            InvalidateRect(wnd, NULL, 1);
         }
         return 1;

One more file to try, with all the seemingly unnecessary stuff removed. If you can confirm that this one works, I think we're done here.
http://www.mediafire.com/?3fz2aymigon

[Nicholas Steel]

Yep, that works still :) no more additional logging to allegro.log either (which is intended, I know).

[Saffith]

All right, I went ahead and committed it. Hopefully, that's the end of that. Thanks for being patient with me here.

[Nicholas Steel]

It probably would have been worked out quicker if we had used MSN >.> though I have no clue how long it takes to compile Allegro.dll