home *** CD-ROM | disk | FTP | other *** search
- **********************************************************************
- * DISCLAIMER OF WARRANTIES: *
- * *
- * The following enclosed code is sample code created by IBM *
- * Corporation. This sample code is not part of any standard IBM *
- * product and is provided to you solely for the purpose of assisting *
- * you in the development of your applications. The code is provided *
- * "AS IS", without warranty of any kind. IBM shall not be liable *
- * for any damages arising out of your use of the sample code, even *
- * if they have been advised of the possibility of such damages *
- * *
- **********************************************************************
-
- Direct Manipulation Sample 4
-
- DESCRIPTION:
- The Direct Manipulation Sample 4
- demonstrates dragging container objects
- across applications running in separate
- processes (ie. separate executables). By
- starting the sample application twice, you
- can drag and drop objects to these
- separately running applications. Classed
- used include IDMCnrItem,
- IDMSourceOperation, IDMTargetOperation,
- IDMTargetDropEvent, IDMItemProviderFor,
- IDMHandler, IContainerControl, and
- IContainerObject.
-
- CONCEPT/FEATURE:
- Sample program for demonstrates direct
- manipulation between two container controls
- in the separate processes.
-
- HOW TO BUILD THE PROJECT FROM THE COMMAND LINE:
- From within the directory containing the sample, simply type:
- NMAKE
-
- HOW TO BUILD THE PROJECT FROM WITHIN THE WORKFRAME ENVIRONMENT:
- Refer to the standard Workframe BUILD instructions
-
- HOW TO RUN THE PROJECT FROM THE COMMAND LINE:
- From within the directory containing the sample, start the
- executable twice by typing:
- START DRAG4
- DRAG4
-
- HOW TO RUN THE PROJECT FROM WITHIN THE WORKFRAME ENVIRONMENT:
- Refer to the standard Workframe RUN instructions
-
- SPECIAL NOTES:
- If the sample fails to execute or
- abnormally ends, you can get
- more information about the failure
- by turning on the ICLUI trace.
- This is done by setting the
- environment variable ICLUI_TRACE
- as follows:
-
- set ICLUI_TRACE=ON
- set ICLUI_TRACETO=STDERR
-
- ICLUI_TRACETO controls where
- the trace information is reported.
- With tracing turned on, ICLUI
- exception text will be written to a
- standard error file. For example:
-
- sample >sample.out 2>&1
-
- The exception data is now in the file
- 'sample.out'.
-
- ADDITIONAL HARDWARE/SOFTWARE REQUIREMENTS:
- None
-
- VISUALAGE FOR C++ SAMPLES INFORMATION:
- A complete listing of samples shipped with the VisualAge for C++
- product can be found in the online GUIDE TO SAMPLES. To access
- this notebook, simply:
-
- - Open the VISUALAGE FOR C++ program group in the Program
- Manager window, then
- - Open the GUIDE TO SAMPLES notebook in the program group.
-
-