Script Editor weirdness on NT 4.0

[Mark F]

I just downloaded the latest Girder (3.2.5pre11) from the download page onto a system running NT 4.0. The OK and Cancel buttons are not visible in the script editor window. The window looks truncated on the right and bottom and neither button can be seen.

This occurs when I use the script button in Girder or my plugin to invoke the script editor window. I have not tried the script editor window on NT 4.0 before now. Sorry. :(

[Ron]

Don't you just love when windows is compatible with it selfs. What happens when you resize the window ?

[Mark F]

The window gets bigger or smaller. ;)

The buttons are still not visible and the right and bottom are still cropped.

[Ron]

LOL!!! ( = Laughing out Loud )


Okay, ahum... so I take it the buttons move along with the window resizing just outside of the visible area.

[Ron]

To find out what is going on here, I've made a little demo app that does nothing except for layout of a button and a text field. Please give it a test and report back if everything is visible and moving around correctly.

http://www.girder.nl/temp/movin.zip

[Mark F]

Yes, they are outside the visible window.

The fields in the window appear to have hard 3-d edges and an extra (almost) group box effect around them. I don't see the edges nor the group box effect on the right or bottom. The fields are terminated by the sizeable edge of the window. Does this make sense?

Sorry, it is hard to describe other than to say "It is wrong!!!!" :D

EDIT: I'm a bit slow and we cross-posted. I'll try the app.

[Mark F]

No border on the right and bottom of the text field and no button anywhere.

[Ron]

*grumbl*,.. okay I've gotta run now, but I know how to fix it...

[Mark F]

I need to test this at home (on Win '98) but on NT 4.0 once I have opened the script editor from the Girder tab, my "device configuration" window takes a LONG time to open. The Windows CreateDialogIndirect() function for the dialog stalls for a VERY long time.

If I don't open the script editor window OR I open it on my new dialog's thread of execution, this is NOT a problem.

I noticed this statement in the girder.h file:

typedef PCHAR (WINAPI *t_open_script_editor) (HWND window, PCHAR script); // call from its own thread. free return pchar with gir_free.

Does the script button on the Girder tab create a new thread for the script editor to run on?

Very weird. :o

[Ron]

:(

There is just 1 difference between the "state window", "command capture window" and the "script editor". So what is happening here is another mistery. This difference is the alignment of controls,.. maybe that is causing it....

[Ron]

please give pre 12 a try.