Hi Armin,

The _SCREEN instance, for me, is just the other Win-task, and so you CAN make it active while your modal form is running in the other task. I am not 100 % sure of this, because I can only look at our own app(s) running, surely not showing _SCREEN at all. In fact, I had to explicitly get rid of it, which brought some anomalies. Difficult to test in the production environment as well, because the behaviour is slightly different there.

But do you really need it ? Why build your app on (the virtual) top of _SCREEN ? So instead of _SCREEN as the basis, just have another form and have _SCREEN.Visible = .F. Now have all other forms "in" your new top-form. I wouldn't use a FormSet; too much weird stuff in there.

You'd be missing the dropdowns (and further menu-possibilities) in the top-bar; just make your own class for that.

But obviously it may be a hard thing to do with an up and running app.

Regards,
Peter



>Hi Peter,
>
>thanks for your reply!
>
>>I am almost sure that I miss your point somewhere. "VFP Main Window" ? Do you mean the _SCREEN instance ?
>
>Yes, the _SCREEN.
>
>>Anyway, when I look at my own app and a modal form popping up, I really can't do anything with all other windows. Not my "Main Window" (sure not being _SCREEN), not any other forms, nothing. It just hasn't control at all.
>>In fact I'd say it's kinda other way around : when a modal form is active, no other events at other forms will fire, whereas in the normal Windows environment it could. Just have an app active and mouseover the IE buttons. They "move", right ? Well, my emulated same button behaviour won't on a form that's inactive while the modal form is.
>But I suppose you talk about the _SCREEN instance. I'd never show that from within an app ...
>
>I'm talking about having a modal VFP form displayed in front of _SCREEN. Open the Options dialog in Word/Excel/Outlook for example. You'll see, that Word's main window is totally blocked. You can't size or move it while the Options dialog is displayed. Nothing will happen, regardless where you click on the application's main window.
>
>To see the behaviour in VFP, you can do the following:
>
>

>x = CREATEOBJECT("form")
>x.Show(1)
>

>
>Now doubleclick on the title bar of the _SCREEN or maximize/minimize the _SCREEN. This works, but I'm wondering, if I could do away with that behaviour ...
>
>Armin