[App::Link] Link Execute Property [SOLVED]

[gbroques]

What does the "Link Execute" property do and when would you want to use it?

From Std_LinkMake, it says:

name of the execute function that will run for this particular Link object. It defaults to appLinkExecute. Set it to None to disable it.

It's not very clear what the intention was behind exposing the ability for an end-user to reference a global replacement execute function.

I'm assuming this is similar to Scripted objects and execute for Link objects is called on every recompute.

What does the default appLinkExecute function do? Are there any caveats when you choose to override it?

[paullee]

This should be where it begins before Realthunder can explain more -


[Link] of (Sketch)ObjectPython / Part FeaturePython lose its 'Proxy Methods' ?

[gbroques]

This should be where it begins before Realthunder can explain more -


[Link] of (Sketch)ObjectPython / Part FeaturePython lose its 'Proxy Methods' ?

Thanks Paullee!

You seemed to have planted this idea in this post:

Thanks mentoring Not directly calling execute() indeed. I have a more general idea about how Link should better working calling methods() in LinkObject below... make sense ? ...


Make sense ?

And should stock Link already can do this instead of making a general LinkPython ?

Then the reply was:

That is actually not a bad idea. I'll add that feature, so that Link's execute() function will search and run python method in linked object with name 'appLinkExecute', passing the linked object and the Link itself as input arguments. For array elements, it will pass two additional parameters as parent link object, and element index. The method will look something like this,

Code: Select all

class _Window:
	def appLinkExecute(self, obj, linkObj, linkParent, index):
		pass

Maybe you can try explaining at a high-level what this is for, or the problem you ran into in a concise and generally-applicable way?

It's a bit tiresome for me to try and sift through that thread to gain an understanding of this.

Seems to have something to do with using Std Link in conjunction with Scripted objects or FeaturePython Objects, and the "proxy methods" being stripped or inaccessible.

[paullee]

Seems to have something to do with using Std Link in conjunction with Scripted objects or FeaturePython Objects, and the "proxy methods" being stripped or inaccessible.

Yes it is like the way you describe.

To my understanding, it allow some 'features' of a FeaturePython objects to works in a Link. E.g. I make Arch Windows to auto placing itself to its Host object in a Method. Without the appLinkExecute, its Links would not know it should execute this and the Links would not update its placement likewise.

Realthunder would explain the potential and mechanism in details

[realthunder]

Seems to have something to do with using Std Link in conjunction with Scripted objects or FeaturePython Objects, and the "proxy methods" being stripped or inaccessible.

Yes it is like the way you describe.

To my understanding, it allow some 'features' of a FeaturePython objects to works in a Link. E.g. I make Arch Windows to auto placing itself to its Host object in a Method. Without the appLinkExecute, its Links would not know it should execute this and the Links would not update its placement likewise.

Realthunder would explain the potential and mechanism in details

Yes that's pretty much it. If you are creating a python extension object for your own workbench, you can define a customized behavior when a Link is created and links to your object. You don't need to create yet another python extension for a new type of Link. The default behavior for Link when recomputed is to look for a method called 'appLinkExecute' in the linked object's python extension (i.e. the Proxy object), and execute it if found.

[gbroques]

Yes that's pretty much it. If you are creating a python extension object for your own workbench, you can define a customized behavior when a Link is created and links to your object. You don't need to create yet another python extension for a new type of Link. The default behavior for Link when recomputed is to look for a method called 'appLinkExecute' in the linked object's python extension (i.e. the Proxy object), and execute it if found.

Thank you both for the clarifications!