 | | Suggestion for interprocess communication
|
|
I talked to Anders Isakson about the drag & drop feature. Since he told me that nothing is fixed now, I would like to suggest another way of implementing the drag & drop feature: Since Windows has a real drag & drop mechanism, which is realy easy to (...) (25 years ago, 9-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: Suggestion for interprocess communication
|
|
Michael Lachmann skrev i meddelandet ... (...) 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... Most MFC solutions are *massive* (...) (25 years ago, 9-Feb-00, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | Re: Suggestion for interprocess communication
|
|
(...) 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. (...) Of course it's possible - nothing is impossible! If it's worth the effort is another question :-) (...) Ever tried (...) (25 years ago, 10-Feb-00, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | Re: Suggestion for interprocess communication
|
|
Michael Lachmann skrev i meddelandet ... (...) I'll simply ignore those facts :-) If someone is building with set pieces, they'd better keep to the pieces and colors, or get lost... Seriously, if we want that functionality, then I think the modeller (...) (25 years ago, 11-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: Suggestion for interprocess communication
|
|
(...) That's an item I was thinking about already ... will see whats possible ... (...) Sure, I know, but for me the plain api with its window messages is already similar to the difference between hardware and software of a computer :-) I mean I do (...) (25 years ago, 11-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: Suggestion for interprocess communication
|
|
Michael: (...) 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" (...) (25 years ago, 12-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: Suggestion for interprocess communication
|
|
(...) It's not Windows standard? I think it would be neat if I, for example, could use Notepad as a source and destination. (25 years ago, 13-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: Suggestion for interprocess communication
|
|
Larry Pieniazek skrev i meddelandet <38A60012.2FE46FAC@v...er.net>... (...) solution/suggestion? (...) A 'Windows Standard' doesn't exist - it's a moving target :-) (...) Notepad doesn't work as a drop target (or drag source), it's just a simple (...) (25 years ago, 13-Feb-00, to lugnet.cad.dev)
|
