Subject:
|
Re: Suggestion for interprocess communication
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Thu, 10 Feb 2000 14:35:07 GMT
|
Viewed:
|
807 times
|
| |
|
|
In lugnet.cad.dev, Michael Lachmann writes:
> In lugnet.cad.dev, Anders Isaksson writes:
> >
> > Sigh, I suppose it makes sense, using 'real' drag & drop, although I'm not
> > very keen on adding a ton of OLE into my program. Nor to think about
> > developing time...
>
> I agree that it is more effort for none MFC applications.
Yeah, well. I'm using Borland Delphi, and I suppose there are easy support for
D&D there too, although I've never used it.
> Another one is, that it will never be possible for MLCad to send such a
> message to another window, since it cannot disdinguish when it should use
> Messages and when it should use OLE.
Of course it's possible - nothing is impossible! If it's worth the effort is
another question :-)
> The advantage of MFC by the way, is that developing applications like MLCad is
> much easier and powerfull than any other way ...
Ever tried Delphi? :-))
> And I know what I'm talking about since I wrote plain (none MFC) Applications
> long time before, and the time you win when using MFC can be used for cool
> features ...
There's no denying that!
I'm sorry if I sounded a bit 'unresponsive' (tired, got a cold). I realize
you're right, we should probably use the builtin Windows D&D (Our programs are
not easily ported to unix/Linux anyway).
I think that we should use plain CF_TEXT as the clipboard format, as every
program handling text can paste it too.
But we do need some kind of protocol - LDList will want to know if a drop was
accepted/used, to be able to keep piece counts correct (Is this already
inherent in Win D&D?).
OK, back to the manuals, I'll try to read up on D&D in Delphi...
--
Anders Isaksson
BlockCAD: http://user.tninet.se/~hbh828t/proglego.htm
|
|
Message has 2 Replies:
 | | 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 (...) (25 years ago, 10-Feb-00, to lugnet.cad.dev)
| | | Re: Suggestion for interprocess communication
|
| Another thing which comes into my mind now .... If LDList is managing the sets with it's parts, then it would not only have to know that someone is dragging a part away from it, but also if someone is changing the part color in a CAD program, if the (...) (25 years ago, 11-Feb-00, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: Suggestion for interprocess communication
|
| (...) I agree that it is more effort for none MFC applications. (...) Not realy, since if you want to make sure your program is working on all computers no matter whats installed you have to make a static build, which means your application get (...) (25 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
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
