Search found 100 matches

Go to advanced search

by realthunder
Sat Mar 25, 2017 7:14 pm
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

How does it figure out the Instance object? Its Placement, in particular? Yes, this thing is complicated by existence of containers like App::Part. It would be a lot easier if DocumentObject has a method to return its own sub element. So the script just call instance.getElement('LinkedObjName.SubEl...
by realthunder
Sat Mar 25, 2017 6:49 pm
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

Simply tricking freecad in thinking an instance is the base object won't cut it at all. For some things one needs the base object when using the instance, for example when going into edit mode of it, it should be the edit mode of the base object (maybe at the instances location). But for other thin...
by realthunder
Sat Mar 25, 2017 6:26 pm
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

I understand your complaints about our fragile toponaming of style "Edge1". But what do you want now? Do you have a better option? We don't have a better toponaming just yet. If you could roll one out - that would be really awesome! But it's an independent adventure, not really tied all t...
by realthunder
Sat Mar 25, 2017 5:29 pm
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

That is a more subtle GUI question. No matter if datum geometry is used, or regular geometry, the framework remains the same. And "discouraging" shouldn't be a hard block. Sometimes, linking to elements of solids is perfectly adequate, for example when you want to quickly throw some piece...
by realthunder
Sat Mar 25, 2017 5:06 pm
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

I see what you mean here. When a Coin3D node is picked by selection, it returns a path that leads from the picked node all the way to the root node. With that information, the instance ViewProvider can provide Gui::Selection extra information. So I think it is doable. Correspondingly, assembly const...
by realthunder
Sat Mar 25, 2017 4:05 pm
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

Just for the record, I am also playing with these concepts: https://forum.freecadweb.org/viewtopic.php?f=23&t=21144 https://forum.freecadweb.org/viewtopic.php?f=23&t=20933 It is perfectly possible to copy over a node from one object to another, it works quite well, even the selection mechan...
by realthunder
Sat Mar 25, 2017 3:53 pm
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

Selecting "Edge1" of instance is probably not useful, as there is no way to look up where that edge actually is. Whole object selection should be trivial to support. Subelement selection may need some work, or maybe trivial, too. I need to experiment first. What do you mean by selecting &...
by realthunder
Sat Mar 25, 2017 3:26 pm
Forum: Arch
Topic: Ideas needed: Xref
Replies: 20
Views: 964

Re: Ideas needed: Xref

I used assembly2 alot. I think the biggest problem of assembly2 is a conceptual error. Instead of selecting all those connecting faces, edges in the assembly file, and trying to solve the unsolvable problem of updating those faces and edges after part model changes, one should in fact defining those...
by realthunder
Sat Mar 25, 2017 12:50 pm
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

I'm not quite sure what are you proposing. Please explain in more detail. Do you want Shapebinder to become Instance? Yes, to be the instance. However, after a close look at its source code, I think I'd better write a brand new feature and viewprovider for proof of concept. The feature is simple, j...
by realthunder
Sat Mar 25, 2017 3:20 am
Forum: Part Design module development
Topic: Why an object can only be inside one App::Part?
Replies: 22
Views: 176

Re: Why an object can only be inside one App::Part?

Very informant read. I am only half through the thread. So far, I am with DeepSOIC. And I'd propose promoting ShapeBinder to be the missing link, i.e. to provide a lightweight clone of the object. I'll play with it once I got time.

Go to advanced search