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

Enhancing Drag/Drop Granularity for Move and Copy Support in the OS/2 Container

IP.com Disclosure Number: IPCOM000113533D
Original Publication Date: 1994-Sep-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 119K

Publishing Venue

IBM

Related People

Johnson, KD: AUTHOR [+3]

Abstract

In the OS/2* 2.X environment, the current paradigm concerning the decision of whether one container record can be dropped on top of another container record is consistent through both the move and the copy operations. In other words, if the target record will accept the drop of a container record that is moved to the target, the target container record will also accept a container record that is copied to the target.

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

Enhancing Drag/Drop Granularity for Move and Copy Support in the
OS/2 Container

      In the OS/2* 2.X environment, the current paradigm concerning
the decision of whether one container record can be dropped on top of
another container record is consistent through both the move and the
copy operations.  In other words, if the target record will accept
the drop of a container record that is moved to the target, the
target container record will also accept a container record that is
copied to the target.

      However, some applications might want to have more granularity
of drag/drop control.  This granularity of control might be extended
to cover several move/copy situations.  Control could be provided for
both the target container record and the source container record.  A
source container record could be designated as a move only record or
as a copy only record.  Similarly, a target container record could be
designated to only accept the drop of a source container record that
is moved or to only accept the drop of a source container record that
is copied.

      This disclosure describes a solution implemented by the Window
Management System (a Presentation Manager* extension tool) which
allows the above described drag / drop extensions thereby greatly
enhancing the drag / drop capabilities of an application.

      The Window Management System (WMS) Presentation Manager based
solution allows for the application program to indicate the move /
copy rules in several different ways.  They 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 rules may also be
set dynamically at run time with the application filling in the
appropriate information into the WMS internal container record
structures.

      No matter which of the methods described above are used, the
result is that WMS internal flags are set which can restrict the
move/copy operations of a container record in either the case when
that record is the target of a drag/drop or when that record is the
source of a drag/drop.  When the container record is the source of
the drag/drop operation, the two flags that can be set are:

1.  This record can be moved but can not be copied.
2.  This record can be copied but can not be moved.

      When the container record is the target of the drag/drop
operation, the two flags that can be set are:

1.  This record will not allow the drop of a moved container record.
2.  This record will not allow the drop of a copied container record.

      When no flags are set, operations proceed according to the
normal paradigm of drag/drop operations.

      The Presentation Manager drag / drop algorithm is primarily
based on three messages which are sent to the application program for
reaction.  These thr...