 | | Re: Suggestion for MLCad Plug-Ins —Steve Bliss
| | | | (...) I like that idea. (...) Yep. The idea is for LDAO to be both a source and sink for dragged parts. (...) Two approaches: 1. Allow multiple formats for the string being passed in the WM_COPYDATA message. One format is the one you're already (...) (25 years ago, 2-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
| | | | | | | | | | Re: Suggestion for MLCad Plug-Ins —Anders Isaksson
| | | | | Steve Bliss skrev i meddelandet ... (...) (where's the second approach?) (...) information. (...) Of course! Why didn't *I* think of that? (message type 2) (...) as (...) parts, (...) One long string with line separators? Or a multi-message approach (...) (25 years ago, 2-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
| | | | | | | | | | | | L-CAD Parts Messages (was: Suggestion for ML-CAD Plug-Ins) —Steve Bliss
| | | | | | (...) The second approach went beyond the event horizon. (...) One long message with line separators. As long as WM_COPYDATA permits, assuming WM_COPYDATA specifies a limit. <reads doc> Yeah, there's a limit. We can only have 2^32 bytes in the (...) (25 years ago, 4-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
| | | | | | | | | | | | | Reading Part-Lists (was: Suggestion for MLCad Plug-Ins) —Steve Bliss
| | | | | (...) Hmm. Keep a list of field names in a text file. This list maps the field names in various inventory lists to the actual field names. Ex: Part,Part PartID,Part PartNo,Part Name,Name Desc,Name Color,Color Colour,Color Quantity,Quantity (...) (25 years ago, 4-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
| | | | | | | | | | | | Re: Reading Part-Lists (was: Suggestion for MLCad Plug-Ins) —Anders Isaksson
| | | | | Steve Bliss skrev i meddelandet ... (...) Well, I supposed I asked for it :-)) -- Anders Isaksson, Sweden BlockCAD: (2 URLs) (25 years ago, 4-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
| | | | | | |
