SIZE Window Property (OpenInsight Specific)
At 26 MAY 1998 03:36:43PM Jeff Blinn wrote:
We've got 9 windows that were all copied from the same original window (MDI Children). We have a stored procedure to place the windows in the MDI client area. For 7 of the 9 windows, the program works fine. For the other 2 - it doesn't set/change the SIZE property of the window.
We've debugged to the point where we know the program is actually being called. When the SIZE property is 'set' - the left hand side returns the current value (as it should), but if we immediately inspect the SIZE property of the window (using the debugger) it has not been changed.
Is there something in the window properties that could prevent the size property from being set? Has anyone come across anything like this?
Thanks for the help,
Jeff
At 26 MAY 1998 11:31PM Don Bakke wrote:
Jeff,
Does it matter what order these windows are launched in the MDIFrame?
Is there a SIZE event associated with these windows?
dbakke@srpcs.com
At 27 MAY 1998 03:08AM Jeff Blinn wrote:
Does it matter what order these windows are launched in the MDIFrame?
The order doesn't matter. We've tested each window individually, and these two just won't accept the Set_Property command for some reason. As I mentioned, we can step through with the debugger, and as soon as the Set_Property command executes, we check the SIZE property for the window, and it is unchanged.
Is there a SIZE event associated with these windows?
No SIZE event defined on any of the windows.
At 27 MAY 1998 09:29AM Don Bakke wrote:
Hmmm, either I'm looking at your problem way too late in the evening or way too early in the morning or this really is a weird problem. I'm tempted to take the easy way out and say the form has been corrupted somehow, but I probably would experiment some more if I were in your shoes.
Just for laughs, what happens if you 1) launch the form by itself, that is, outside of an MDIFrame and 2) click on a temporary button on the form that changes the SIZE of the form (make sure this is new code and not your subroutine)?
If you are at all interested I'd be willing to test the form myself. Just send it to my below link.
dbakke@srpcs.com
At 27 MAY 1998 10:22AM Don Bakke wrote:
Jeff,
An afterthought…do you have any right or bottom anchored controls? I know that if one tries to make a window smaller and there are controls anchored then this will create some problems.
BTW, what exactly is your subroutine doing? That is, is it just re-positioning the window, making it larger, smaller, etc?
dbakke@srpcs.com
At 27 MAY 1998 05:59PM Jeff Blinn wrote:
Just for laughs, what happens if you 1) launch the form by itself, that is, outside of an MDIFrame and 2) click on a temporary button on the form that changes the SIZE of the form (make sure this is new code and not your subroutine)?
Since the window runs inside a MDI frame, it won't really work outside of that. We did try putting a button on the window, and have the same results.
However, we rebuilt one of the two forms, and now that one works. A new twist, is that the remaining one - works on one Win95 PC and not on another. I have no idea what's causing that - I've looked at basic configuration options, but I couldn't find anything. We're accessing the same network copy, the program works on all the other windows (just repositioning the window). I'm wondering if it might be a DLL or something that is different on my PC than the other? I don't really know which ones to look at . . .
I hate the thought of redoing the remaining window, since it has about 100 + controls on it.
At 29 MAY 1998 09:23AM Gene Gleyzer Revelation wrote:
Jeff,
Presentation Server may block the request of setting the form's SIZE property if the specified size comes into contradiction with auto-sized or anchored controls on the form. Let's say, for example, you have a control (could be hidden) with original][size=(100, 100, 80, 20) and it's set to autosize width. Presentation Server won't let you reduce the width of the form by more than 80 pixels, because it would not be able to satisfy the autosize request for this control. I believe that you have a situation similar to this on your form.
Gene
At 29 MAY 1998 12:38PM Jeff Blinn wrote:
Presentation Server may block the request of setting the form's SIZE property if the specified size comes into contradiction with auto-sized or anchored controls on the form. Let's say, for example, you have a control (could be hidden) with original][size=(100, 100, 80, 20) and it's set to autosize width. Presentation Server won't let you reduce the width of the form by more than 80 pixels, because it would not be able to satisfy the autosize request for this control. I believe that you have a situation similar to this on your form.
Gene,
The idea that the Set_Property command is being blocked sounds correct, although I'm not sure the reasoning holds up in this case. We are not resizing the window at all - just repositioning it.
Also, it now seems (as I mentioned in another post) that the problem is only occurring on one of our two development machines. Both are similar configuration (Win95, Compaqs, pentiums, etc.)
Are there any system level files I should look at that could impact the presentation manager? I'm thinking I may have a different version of some file - although the copy of OI we are running is off our network.
Thanks,
Jeff
At 29 MAY 1998 02:56PM Andrew P McAuley wrote:
How about rubber banding all the controls and pasting into a new window?
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 29 MAY 1998 06:30PM Jeff Blinn wrote:
The form in question here has a few buttons at the bottom of the screen which were anchored. By resizing the window a little bit, and giving them more 'breathing room' - the window now accepts the Set_Property/SIZE values for repositioning. And, it works on all PC's now.
Thanks for the help.