Screen Freeze Problem

[Phil Rolf]

I have shortened the number of Cases in the script below, there should be 12. However, the problem is with the ui_freeze() function. Preceding this code is an xdialog box where FORMSEL is filled in with a value. The script changes to a new form, BUT on the form that is opened, the standard A5 tool bar is gone and the Min, Max, and window close (X) icons do not work. If I go back and remove the ui_freeze() functions everything is fine. What I am trying to do is prevent the screen repaintings during the transition from one form to the other.

'Execute inline Xbasic code.
if varc_result="Cancel"
end
end if

'Close current form or browse window.
DIM mode as c
mode = parentform.mode_get()
'If the form is in Enter or Change mode, first save the changes before closing the form
if mode = "ENTER" .or. mode = "CHANGE" then
parentform.commit()
'Check to see if the record was successfully saved
if parentform.mode_get()"VIEW" then
ui_msg_box("Unable to save your changes","Please correct and save, or discard your changes", UI_STOP_SYMBOL)
end if
end if
'Close the form
parentform.close()
ui_freeze(.T.)
select
case formsel="Availability Sheet"
:form.view("Availsheet")
:availsheet.maximize()

case formsel="fields"
:form.view("field num ms")
:field num ms.maximize()

case formsel="scheduling"
:form.view("schdlink ms")
:schdlink ms.maximize()

end select

ui_freeze(.f.)

[Jim Chapman]

RE: Screen Freeze Problem

Hello Philip,

Quickly viewing your code it appears that the script is being run from the context of the parentform. If so your parentform.close() statement should be the last command in the script. The script is being run in the memory space context of the parentform. Consequently, closing the form is closing the context of the script. The parentform.close() should be the last statement of the script. I don't think you need the ui_freeze()statements. Try this, get rid of the ui_freeze() statements, put the parentform.close() as the last statement of the script. Then change the case statement options from:

case formsel="Availability Sheet"
:form.view("Availsheet")
:availsheet.maximize()

To something like this:

case formsel="Availability Sheet"
:form.load("Availsheet")
:availsheet.maximize()
:availsheet.show()
:availsheet.activate()

As an aside, I would rather use pointer syntax such as:

case formsel="Availability Sheet"
vFrm = :form.load("Availsheet")
vFrm.maximize()
vFrm.show()
vFrm.activate()

This will prevent a problem if there is another instance of the form open. also less typeing :-)

Good luck,
Jim

[Phil Rolf]

RE: Screen Freeze Problem

Jim,
I tried your ideas and YES I do keep the tool bar etc, However, you can see all the transitions of the screen changes. That is what I am trying to eliminate. Any other suggestions?

Thanks

[Jim Chapman]

RE: Screen Freeze Problem

Hello Philip,

>>However, you can see all the transitions of the screen changes

[Phil Rolf]

RE: Screen Freeze Problem

Yes, I am using the form.load but you will see the screens change sizes, flickers etc. That is why I was using the Freeze function. I want to do some more experiment to see if it is a particular type of form that is the problem such as a single table vs a form attached to a set.

The Freeze command does as it is suppose with the exception of repainting the tool bar and the window functions not working.