get DLL path from the call library function node

[Andi_S]

Since the call library function node (3) supports wild-cards it is not clear which DLL file is physically used during runtime. Nevertheless this information can be interesting and important in some cases. Currently there is no way to get this information (1). Therefore I suggest to show the DLL-Path-Output always (2). It shall return the entire path and name of the currently loaded DLL.

[wiebe@CARYA]

+1 That would be convenient at times...

I hope that when\if this gets implemented, it doesn't hurt performance when it's not wired though. CLFNs often need to be fast, and if it would always copy a path that would certainly hurt performance significantly.

Note that if you specify a path on the diagram, the path is duplicated as an output:

Sadly, that's a duplicate path (quite useless), not the resolved path. I mention it because it potentially interferes with your proposed output...

An alternative would be a special function that resolves the given path to the path that's actually loaded. That would also have far less impact on the existing scripting, like the wizard.

This has the added benefit you can load DLLs without actually calling a function.

It's probably a lot easier to implement as well.