C# 클래스 SIL.FieldWorks.Common.Framework.DetailControls.ViewSlice

Somehow a slice (I think one that has never scrolled to become visible?) can get an OnLoad message for its view in the course of deleting it from the parent controls collection. This can be bad (at best it's a waste of time to do the Layout in the OnLoad, but it can be actively harmful if the object the view is displaying has been deleted). So suppress it.

Some 'unreal' slices can become 'real' (ready to actually display) without actually replacing themselves with a different object. Such slices override this method to do whatever is needed and then answer true. If a slice answers false to IsRealSlice, this is tried, and if it returns false, then BecomeReal is called.

The height that the slice would ideally be to accommodate the rootsite.

Executes in two distinct scenarios. 1. If disposing is true, the method has been called directly or indirectly by a user's code via the Dispose method. Both managed and unmanaged resources can be disposed. 2. If disposing is false, the method has been called by the runtime from inside the finalizer and you should not reference (access) other managed objects, as they already have been garbage collected. Only unmanaged resources can be disposed.

If any exceptions are thrown, that is fine. If the method is being done in a finalizer, it will be ignored. If it is thrown by client code calling Dispose, it needs to be handled by fixing the bug. If subclasses override this method, they should call the base implementation.