Hello all:

I'm getting different results with the same code between 16 and 32 bit, wondering if anyone has seen similar…

In 16 we're opening a series of children into a frame, with each child opening maximized and locked into the frame. We then have code to page back-and-forth between each child. Works great.

In 32, exact same code, only the *last* child opens maximized and locked into the frame, all the previous children seem to open as if they are 'tiled'. Here's a snippet of the code:

* page_list and activechildren are previously defined

Loop

Remove Sheet From Page_List At Col Setting Flag

While Len(Sheet)

 Child=Start_Mdichild(Sheet,Ctrlentid,'','','',MAXIMIZED$,'')

End

Repeat

Was=Set_Property(Ctrlentid, 'MDIACTIVE' ,activechildren)

If I rem out the last WAS statement I can verify that the last child opened maximized.)

Any ideas on this? Thanks much,

Mike O.

Mike,

In 32, exact same code, only the *last* child opens maximized and locked into the frame, all the previous children seem to open as if they are 'tiled'. Here's a snippet of the code: …

There seems to be a slight a fault with your reasoning, or your description of what happens. You seem to say the first child opens tiled, then the next child opens tiled, etc, and in the final instance of the loop the last child opens maximized. But unless you've omitted something significant from your code snippet, the circumstances are exactly the same in each instance of the loop. There's nothing different with the last instance. There's nothing to tell the bug it's time to open maximized instead of tiled.

I think each child must open maximized, and that the change to tiled happens afterwards. Either each new call to Start_MDIChild causes the previous child to tile, or the tiling happens some time after the loop.

What's in that activechildren array of yours?

- Oystein -

Hi

We had this problem as well. We got round it by setting the maximised proprty for the windows in the forma designer.

Works fine now but took us a couple of days to find out

Oystein and Michael, thank you for your responses. Michael, you nailed it, that solved the problem. Means going back and recompiling dozens of forms, but hey… anything else you came across along those lines?

Oystein, you were also correct; the children *were* maximizing as they opened individually - but setting the first one active is what triggered the tiling.

Thanks again,

Mike

View this thread on the forum...