1. Can you give me an example why you would need to nest a frozen control?

2. Can you not just have an option to freeze all controls on a WINDOW, do what you need to, then unfreeze the WINDOW?

3. What’s the difference between LAZYDISPLAY and FREEZE? Wouldn’t LAZYDISPLAY do the same thing?

I think what’s needed is some sort of FreezeManager extension that can be
added to a window or a report.

FreezeManager CLASS,TYPE
Control_Q queue,private
FEQ long
state long
end
Init procedure()
Refresh procedure()
ice procedure(long singlecontrol)
ice procedure(long startcontrol, long endcontrol)
thaw procedure(long singlecontrol)
thaw procedure(long startcontrol, long endcontrol)
END

Internally there would be a private queue of control equates and states,
together with Init and Refresh methods.

Init would build the queue by looping through the controls and adding an
entry for each ‘freezable’ control.

Refresh would update this queue (so that any destroyed / created controls
could be catered for)

You’d also have overloaded ICE and THAW procedures to freeze / unfreeze a
single or a range of controls based on the passed in FEQs

I can just about see the point of being able to freeze an already frozen
control and the nesting.
A third party template may need to freeze a range of controls whilst it does
it’s thing without having to know the current state of the control or
whether another template is also freezing.
The class above would need modification to cope with this.

It would undoubtably be preferable for SV to put this in place themselves
and make the functionality available to endusers/template designers etc

Graham