Emmitt: So was this still something that has to be done for every single form? I don't have any multiple-monitor clients yet, so it looks like I'll add this to my list (along with Windows 7 upgrades) of things I'm not looking forward to!
Karen > That was the key to my solution. Set the menu forms to ALPHABLEND = > 'TRUE', > set the value to 0. In the on-after-start eep, test the screen size; if > the > horizontal is >1400, do some quick math and center the form on the right > monitor. Here's the key: as Mike noted, all child objects should center > themselves on that form. Problem is, from the menu form we do an EDIT > USING > with a background form; the OAS for this form actually runs the > application > code. Now, if the main menu form is not on center of the monitor, this > background form will come up centered on that monitor anyway (as Doug > noted.) So I need to center my menu forms on the monitor, and all will be > well. To avoid a flash on the left monitor, the ALPHABLENDVALUE is > defaulted to 0, and when I've issued the PROPERTY RBASE_FORM LEFT command > I > immediately PROPERTY RBASE_FORM ALPHABLENDVALUE '255'. No flash/flicker. > > Doug: I'm not anywhere near ready to do as you suggest and store the > user's > coordinates in a table; besides, there are multiple databases involved. > Oh, > the headaches! (Okay, it could be done with one table and SATTACHes from > the other databases ... still ...) > > Emmitt Dove
