 | | Re: Suggestion for MLCad Plug-Ins —Tim Courtney
|
| | | (...) [snip] (...) Love the idea! I think something like this is just what we need to be able to consolidate cad utilities into one easy to use interface. For example, there could be L2P and L3P plugins written so you can access them from MLCad in a (...) (25 years ago, 7-Jan-00, to lugnet.cad.mlcad)
|
| | | |
| | | | | Re: Suggestion for MLCad Plug-Ins —Michael Lachmann
|
| | | | I'm happy to hear the general agreement for plug-ins. I agree defining a standard, valid for other programs too, would be the best scenario. The idea to choin the plug-in into the rendering pipe-line is a good idea, but has to be well defined. I (...) (25 years ago, 7-Jan-00, to lugnet.cad.mlcad)
|
| | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Jack Gregory
|
| | | | Michael Lachmann <m.lachmann@xpoint.at> wrote in message news:FnyBpI.5HD@lugnet.com... (...) In my other life, I write what is essentially a plug-in for mechanical CAD systems. I also use plug-ins in other applications, like PageMaker. The common (...) (25 years ago, 7-Jan-00, to lugnet.cad.mlcad)
|
| | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Michael Lachmann
|
| | | | Sorry for the delayed reply. I agree that plug-ins should have more functionallity than just playing the roole of a format converter. What I could imagine is chaining the plug-in into the read processing of a dat/mpd file, that allowing the plug-in (...) (25 years ago, 12-Jan-00, to lugnet.cad.mlcad)
|
| | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Steve Bliss
|
| | | | (...) A 'hoser' plugin would be awesome for bendable pieces! Steve (25 years ago, 12-Jan-00, to lugnet.cad.mlcad)
|
| | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Steve Hodge
|
| | | | (...) into (...) How about this: a plugin that can restrict the parts available when building a model to a particular set, and keeps track of how many piece of each part are left. Bascially mimicing the way models are made from real sets. I think (...) (25 years ago, 26-Jan-00, to lugnet.cad.mlcad)
|
| | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Steve Bliss
|
| | | | (...) That would be a cool thing, but I don't think it would make sense as a plug-in. There's been discussion of having a protocol for dragging parts between L-CAD applications, it would be cool to have an "LD Palette" program which displayed all (...) (25 years ago, 26-Jan-00, to lugnet.cad.mlcad)
|
| | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Steve Hodge
|
| | | | | (...) a (...) in. (...) Yeah, it would be better if it was supported by MLCAD, either directly or via the drag and drop protocol or something similar. I was just thinking in terms of plugins because that's what we were talking about, and it really (...) (25 years ago, 26-Jan-00, to lugnet.cad.mlcad)
|
| | | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Anders Isaksson
|
| | | | Steve Bliss wrote in <lugnet.cad.mlcad> ... (...) displayed (...) dragged (...) Piece o' cake! I gave it an hour... LDList ver 3.6 can load a set description, containing a lot of lines like: <count> <piece number> and will limit the display to the (...) (25 years ago, 27-Jan-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Steve Bliss
|
| | | | (...) Cool. Uhh, what about color? Augh! I don't want to think about that right now. (...) OK, I'll work on getting this feature added to LDAO. (...) How about if LDList accepted the dragged parts as well as supplied them? When a part is dragged (...) (25 years ago, 31-Jan-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Suggestion for MLCad Plug-Ins —Anders Isaksson
|
| | | | Steve Bliss skrev i meddelandet ... (...) We'll think about it later... (...) When a (...) Sounds like a good idea - I'll test it when Real Life permits. Will LDAO also allow drag *from* LDAO to xxx? By using the same protocol you could use LDAO (...) (25 years ago, 31-Jan-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| | | | |
| | | | | | 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)
|
| | | | |
