Das Wissen aller Anwender nutzen

Im Allplan Connect Forum tauschen sich Anwender aus, geben wertvolle Tipps oder beraten sich bei ganz konkreten Aufgabenstellungen − auch international.
Und damit wirklich keine Frage unbeantwortet bleibt, unterstützen die Mitarbeiter des Technischen Supports ebenfalls aktiv das Forum.

Es erwarten Sie:

  • Foren-Vielfalt aus CAD Architektur, CAD Ingenieurbau uvm.
  • Tipps von User für User
  • international: Deutsch, Englisch, Italienisch, Französisch und Tschechisch

Melden Sie sich jetzt an und diskutieren Sie mit!

Zur Registrierung

[Frage] Transform "standard" pythonpart into "interactor" pythonpart ?

Schlagworte:
  • Allplan 2024
uid-303591
uid-303591
29.07.2024 - 14:42

Hello,

I manage to realize different "standard" pythonparts (for example, i created foundation with reinforcement).

Now, I would like to use them with existing object in Allplan but I don't really understand how to use "interactor" pythonparts.
I there a way to transform one into another ? Or is there a documentation which would be easier to understand than the API one ? (or that is more described ? with more examples ?)

Thanks in advance.
Will

Hilfreichste Antwort anzeigen Hilfreichste Antwort verbergen

bmarciniec
bmarciniec
30.07.2024 - 16:24 *

Hi Will,

transforming a standard PythonPart into an interactor is pretty tricky. But if you can wait for 2025 (release in October), then what I could suggest you to transform it to a Script Object (have a look on this page to know the differences). It is a third way of how a PythonPart can be implemented. Much easier to implement than an Interactor, but offering almost the same possibilities. And, a Standard PythonPart can be pretty easily turned into a Script Object with a couple of code tweaks. We are planning to release a training video on how to do it. So, please have a little patience
Best,
Bart

bmarciniec
bmarciniec
30.07.2024 - 16:24 * [Hilfreichste Antwort]

Hi Will,

transforming a standard PythonPart into an interactor is pretty tricky. But if you can wait for 2025 (release in October), then what I could suggest you to transform it to a Script Object (have a look on this page to know the differences). It is a third way of how a PythonPart can be implemented. Much easier to implement than an Interactor, but offering almost the same possibilities. And, a Standard PythonPart can be pretty easily turned into a Script Object with a couple of code tweaks. We are planning to release a training video on how to do it. So, please have a little patience
Best,
Bart

keops
keops
31.07.2024 - 09:38

Top ! Can't wait for october

ChippyCat
ChippyCat
18.09.2024 - 08:26

Zitiert von: uid-303591
Hello,
I manage to realize different "standard" pythonparts (for example, i created foundation with reinforcement).
Now, I would like to use them with existing object in Allplan but I don't really understand how to use "interactor" pythonparts.

I there a way to transform one into another ? Or is there a documentation which would be easier to understand than the API one ? (or that is more described ? with more examples ?)
Thanks in advance.

Will

I used SelectedObject and Execpythonpart in Visual Scripting. It runs pretty good

uid-303591
uid-303591
18.09.2024 - 13:18

I used SelectedObject and Execpythonpart in Visual Scripting. It runs pretty good

Thanks for your answer but.. I'm looking for these function in Visual Script and I can't fin none of them...

ChippyCat
ChippyCat
19.09.2024 - 02:44

Zitiert von: uid-303591

I used SelectedObject and Execpythonpart in Visual Scripting. It runs pretty good
Thanks for your answer but.. I'm looking for these function in Visual Script and I can't fin none of them...

In Visual Scripting, we have many tools that can support the selection of available objects.
EX : SelectAllObject, SelectGeometryObject, SelectObjectbyAreaInput, v.v.v.
After selected, you can copy all standard code to Node ExecPythonScript, adapt few things and get the result.

Anhänge (1)

img
Screenshot 2024-09-19 093236.png
Typ: image/png
18-mal heruntergeladen
Größe: 56,05 KiB