To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 4021
4020  |  4022
Subject: 
Re: Suggestion for interprocess communication
Newsgroups: 
lugnet.cad.dev
Date: 
Sat, 12 Feb 2000 15:07:52 GMT
Viewed: 
902 times
  
Michael:

The source of the drag & drop operation (that one where you start the drag ..)
calls a function which returns the result of the drag&drop operation, which is
returned from the drop-target application.
It can be one of (not exactly the MS defs.) NONE ... nothing done
COPY ... drop target copied the data
MOVE ... drop target moved data (normaly not used between seperate apps).
The program could return whatever it likes of theese codes.

Suggestion: NONE means target did not except the operation, COPY or MOVE means
done.

What about using MOVE when running in "set mode"?

Since other programs accepting plain text data most likely
use COPY, LDList will know whether to subtract the part from
the collection.

When just running in "unlimited building mode" COPY should
be used.

Play well,

Jacob

------------------------------------------------------------
--  E-mail:               sparre@cats.nbi.dk              --
--  Web...:     <URL: http://hugin.ldraw.org/LEGO/ >      --
------------------------------------------------------------



Message is in Reply To:
  Re: Suggestion for interprocess communication
 
(...) Yes, :-(((( (...) No problem :-) Hope you feel weel again soon ... (...) The only problem is if there are apps accepting CF_TEXT but doesn't know about LEGO at all, you will loose a part :-( Private formats which are registers with just one (...) (24 years ago, 10-Feb-00, to lugnet.cad.dev)

11 Messages in This Thread:



Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR