Both the New Quest Window and the Initialization Data window are a bit screwy in Large Mode.

Furthermore, the cancel button in Initialization seems to be broken in Large Mode.
A couple windows are screwy in Large Mode.
Did someone fix this? 'Cause I'm not seeing it in the current build... (Guess It's time for a new one then)
Uh... no! It's still happening in 1182!
Both dialogs confirmed buggy in 1182, the "Cancel" button on the Initialization Data dialog doesn't work either.
I see it in Wine, but not native Linux builds. This happens in 1170, but not 1164. I don't see anything obvious between those two that would explain this.
Aaah that's just fantastic. Everything was going so smooth too. :\ ..I'll see if I can't track down the problem.
If it had to do with anything, it would have to do with these lines in zq_custom.cpp:
d[0].w = int(d[0].w*RESIZE_AMT);
d[0].h = int(d[0].h*RESIZE_AMT);RESIZE_AMT is 1.5.Is there any reason why this would work on some systems but not others?
Maybe try casting the w and h variables to doubles right before the multiplication.
That doesn't seem to be the problem, and also doesn't explain why the cancel button doesn't work. Strange, I can see this bug in a release build but not debug. Hmm....
[edit] -Also; All the bounding lines seem to be wrong in the init data dialog tabs, and 'cancel' works in some of them, but not all in windows.
Possibly related, there's an issue with small mode at scale 2 or above:

Again, only in Windows builds starting from 1170.
So what we've found out is that prior to 1170 we had a stupid Windows palette grab crash bug, and now 1170 and up magically fixes that but causes this. ...Uh huh..
Could it all be because of the new allegro42.dll? There doesn't seem to be anything in ZC's code that would explain it, after all. But then, this thing is kind of held together with duct tape...
Yeah, and we're running out of duct too. More duct tape! 😛
Actually the MinGW dll and MSVC dll aren't too compatible which is why I had to swap them. I did actually double check the compiler settings and even recompiled it, which did nothing. Like I said debug is fine, but if something major like a dll was broken why only the init dialog in large mode and the progress dialog in small with scale -2? I'm having trouble making any sense of this.
Ah, right, you switched compilers. More likely that, then. Actually, I tried copying in the one from build 743, the last build DarkDragon published, and that didn't change anything.
Have you checked that the width and height getting passed to jwin_draw_frame() are correct? The frame code is pretty straightforward, so if it's getting the right inputs, I would think it has to be something to do with Allegro.
... That's probably a stupid question, but, hell, I have no idea what's wrong with it.
The jwin_draw_frame() are always 256 w, 19 h for the init data dialog, so I'm assuming that code only draws the top part of the frame. It works fine with a debug build, so tracing is about the only thing I can do to get any info. Problem is (If you hadn't noticed already) I hate dealing with the zc/allegro GUI so I'm not very good with any of that code. :P
Please someone tell me it's gone now and no other bugs magically appeared. 😞
Dialogs appear fixed.
Yup! The dialog boxes are back to normal again!:thumbsup: