Browse Prior Art Database

Dynamic Determination of Officevision/2 Protected Template

IP.com Disclosure Number: IPCOM000120802D
Original Publication Date: 1991-Jun-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 56K

Publishing Venue

IBM

Related People

Bell, LK: AUTHOR [+3]

Abstract

This article describes a method for an OfficeVision*/2 (OV/2) object to find out whether it is in a protected state since it can be used for both system-shipped templates and non-system shipped templates. If system-shipped templates do not permanently disable the discard menu item in the New Icons Folder, they require a way to find out whether they are currently in a protected state.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 56% of the total text.

Dynamic Determination of Officevision/2 Protected Template

      This article describes a method for an OfficeVision*/2
(OV/2) object to find out whether it is in a protected state since it
can be used for both system-shipped templates and non-system shipped
templates.  If system-shipped templates do not permanently disable
the discard menu item in the New Icons Folder, they require a way to
find out whether they are currently in a protected state.

      OV/2 system-shipped applications are not allowed to be
discarded by the average user.  The system administrator may have a
need, however, to delete a system-shipped class (in case of
registration error) and re-register the class.  As a result,
system-shipped templates should not permanently disable the discard
menu item in the New Icons Folder. Also, some OV/2 applications do
not need their own icon procedure for use with their template object.
New Icons Folder provides a default icon procedure which can be used
with both OV/2 system-shipped templates and with non-system-shipped
templates.  Therefore, the New Icons Folder default icon procedure
should not permanently disable the discard menu item.

      OV/2 will set a "protected" template bit in its template
information structure when an application is registered as a
system-shipped application.  It will then provide an API to query
whether a template is protected or not.  The API is called by an icon
procedure, passing in a class name and a template na...