Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Automatic Notebook Tab Dimension Algorithm

IP.com Disclosure Number: IPCOM000115538D
Original Publication Date: 1995-May-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 50K

Publishing Venue

IBM

Related People

Morgan, SA: AUTHOR [+2]

Abstract

In OS/2* 2.X, the Presentation Manager Notebook control allows for the specification of tabs. A tab can exist on any page made part of a notebook. The tab can display either text or a bitmap. The Notebook control provides a default size for the tab dimension. All tabs have the same dimensions. The default tab dimension is seldom the dimension required for proper representation of the tab information.

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

Automatic Notebook Tab Dimension Algorithm

      In OS/2* 2.X, the Presentation Manager Notebook control allows
for the specification of tabs.  A tab can exist on any page made part
of a notebook.  The tab can display either text or a bitmap.  The
Notebook control provides a default size for the tab dimension.  All
tabs have the same dimensions.  The default tab dimension is seldom
the dimension required for proper representation of the tab
information.

      Therefore, the Notebook control provides a BKM_SETDIMENSIONS
message for altering the tab dimensions.  With this facility, you can
alter the dimensions to be suitable to the application needs.  The
problem is how to determine what the suitable amount is.  This is
important in the face of changing tab text either due to application
design or language translation.

      The common solution is to set the tab dimension to be a little
bit bigger than what is needed given the current design and
translation.  This extra space will be available in case of a future
change that requires more space.  Since this is an estimate, it is
possible that the estimate is incorrect.  Therefore, clipped
information exists when the estimate is too small and unnecessary
white space is present when the estimate is too large.  Although this
just tweaks one line of code, this extra step can be costly as it
results in a code change if the information changes.  Information is
often kept separate and under the control of...