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

Overcoming Default Drag/Drop Deficiencies in the OS/2 Container Control

IP.com Disclosure Number: IPCOM000112202D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 89K

Publishing Venue

IBM

Related People

Johnson, KD: AUTHOR

Abstract

In the OS/2* 2.0, 2.1 Workplace Shell* environment, the accepted default behavior when dragging and dropping an icon (record) in a container is to MOVE the container icon. The user may override this default behavior by holding certain keys down during the time that the container record is being dragged - i.e. holding down the control key changes the default operation from a MOVE to a COPY, holding down the control and shift keys changes the default operation from a MOVE to a SHADOW COPY.

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

Overcoming Default Drag/Drop Deficiencies in the OS/2 Container Control

      In the OS/2* 2.0, 2.1 Workplace Shell* environment, the
accepted default behavior when dragging and dropping an icon (record)
in a container is to MOVE the container icon.  The user may override
this default behavior by holding certain keys down during the time
that the container record is being dragged - i.e. holding down the
control key changes the default operation from a MOVE to a COPY,
holding down the control and shift keys changes the default operation
from a MOVE to a SHADOW COPY.

      Although this default behavior works well in most cases, there
are times when a different default behavior is desired.  For example,
an icon might represent a template object that is used as a starting
point to create other like objects.  In this case, a default
operation of COPY rather than MOVE is desirable.

      The Workplace Shell provides for the type of template support
mentioned above via Workplace Shell methods.  However, there are many
applications that for various reasons will choose not to use the
Workplace Shell class libraries but will still want their icon to
appear as an object on the desktop that will be launchable via double
clicking and will want their program to exhibit many behaviors found
in the Workplace Shell.  They will use the Presentation Manager* or
Presentation Manager extension tools to provide this support.

      The Window Management System (WMS), a Presentation Manager
extension tool, allows for the application program to indicate the
default drag / drop operation for a container icon in several
different ways.  The default operation may be indicated at compile
time via a flat ascii file which adheres to certain WMS defined
syntax rules and is parsed via a WMS tag language compiler into files
that will be used at run time to initialize various WMS structures
including the container records.  The default operation for a
container record may also be set dynamically at run time with the
application filling in the appropriate information into the WMS
internal container record structures.

      The Presentation Manager drag/drop algorithm is primarily based
on three messages which are sent to the application program for
reaction.  These three messages correspond to different points within
the drag / drop operation and are al...