| preventing command-line users from accidentally accessing objects that you need to protect for some reason. • on — Handles are always visible when HandleVisibility is on. • callback — Setting HandleVisibility to callback causes handles to be visible from within callback routines or functions invoked by callback routines, but not from within functions invoked from the command line. This provides a means to protect GUIs from command-line users, while allowing callback routines to have access to object handles. • off — Setting HandleVisibility to off makes handles invisible at all times. This might be necessary when a callback invokes a function that might potentially damage the GUI (such as evaluating a user-typed string) and so temporarily hides its own handles during the execution of that function. Functions Affected by Handle Visibility When a handle is not visible in its parent's list of children, it cannot be returned by functions that obtain handles by searching the object hierarchy or querying handle properties. This includes get, findobj, gca, gcf, gco, newplot, cla, clf ,and close. Properties Affected by Handle Visibility When a handle's visibility is restricted using callback or off,the object's handle does not appear in its parent's Children property, figures do not appear in the root's CurrentFigure property, objects do not appear in the root's CallbackObject property or in the figure's CurrentObject property, and axes do not appear in their parent's CurrentAxes property. Overriding Handle Visibility You can set the root ShowHiddenHandles property to on to make all handles visible regardless oftheir HandleVisibility |