Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WAIT and modal forms

Status
Not open for further replies.

mpgalvin

Programmer
Feb 5, 2001
119
IE
We're writing a VFP app to replace a 2.6 version (yeah, don't get me started!), and one of the more annoying problems I've come across is that if a WAIT WINDOW is used, it appears on the main form (the first form opened). Now, we have Modal forms opening on top of that modal form, and if a WAIT is activated, it causes some problems, the upshot being that I have to minimize a form that is not minimized, but is not visible either, then maximize it again. Huh?

I've managed to get rid of a lot of the 2.6 WAITs using messageboxes and a status bar, but I'm concerned about things like read-only grids (used big time). If the user attempts to type directly into one, they get a system-generated WAIT ("this control is read-only") which causes the same problems as before.

Is there anyway of making sure the WAIT window appears in the active form?
 
mpgalvin

You could try repositioning the WAIT WINDOWs with AT nRow, nColumn, which might enable them to be seen.

Alternatively, you could add TIMEOUT to the MESSAGEBOX()s, see FAQ184-451, which simulates WAIT WIND TIMEOUT n

Chris :)
 
Thanks, Chris, but the problem is not that the wait window can't be seen, but that it "demands" to be seen. If the current form obscures it, it dumps it out of the way.

Changing the wait to a messagebox is not a solution either, because the most of the waits I'm left with are system-generated (as in "the control is read only", "the field is invalid", etc)
 
the problem is not that the wait window can't be seen, but that it "demands" to be seen

Thats what a WAIT WINDOW is for.

Read about SET NOTIFY OFF. Jon Hawkins

The World Is Headed For Mutiny,
When All We Want Is Unity. - Creed
 
mpgalvin

Sorry - misunderstood your post.

How about a transparent .shpControl over the grid, listbox or other areas, leaving the scroll bars visible, but denying access to the cells/lists etc?

Chris :)
 
Unfortunately (again!) I need to be able to access the information in the grid - it's company policy to allow a user to edit a line (ie., bring up a container with all the relevant info, not edit it in-situ) by double clicking, or by selecting and pressing "edit". Either way, I can't disallow access to the grid.

Having said that, SET NOTIFY OFF seems to get rid of the "control is read-only" messages, which is good. F1 says it gets rid of *certain* messages - I don't suppose there's a FAQ of what messages it doesn't turn off
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top