Foro de Soporte Allplan

[Pregunta] Generating optional wall in VS, but not as PythonPart [Guardado]

Etiquetas:
  • Wall
  • PythonParts
  • Pythonpart
DGeorgiev
DGeorgiev
26.08.2022 - 08:00

Greetings comrades,
Is there a way to make an “optional” wall using VS while it remains as wall, not Python Part?

The script: Make a U-cladding command where I can turn off/on the generation of inner/outer wall or top cover.

Methods so far:
- Invalid input method: I have a switcher which I feed to the Wall’s path. When I feed a line, it gets generated, and when I feed an invalid input (point or constant 1) it crashes. It can be reproduced by disabling the inner wall generation.

- Switcher method: If I rearrange the nodes and feed the wall into the switcher, controlling the generation from there, the last line of wall becomes python part.

Any suggestions for a way around?

Kind regards,
Dobromir

Adjuntos (2)

U cladding.zip
Type: application/zip
Descargado 784 veces
Size: 11,47 KiB
img
Error message - invalid input.jpg
Type: image/jpeg
Descargado 64 veces
Size: 255,15 KiB

Show solution Hide solution

Xinling
Xinling
26.09.2022 - 16:14 *

Cita de: DGeorgiev
Is there a way to make an “optional” wall using VS while it remains as wall, not Python Part?

Currently, all architectural elements (incl. column, wall, beams) will be generated as a native Allplan object. They won't be included in a PythonPart object.

Cita de: DGeorgiev
- Invalid input method: I have a switcher which I feed to the Wall’s path. When I feed a line, it gets generated, and when I feed an invalid input (point or constant 1) it crashes. It can be reproduced by disabling the inner wall generation.

I checked your "invalid input" script. Perhaps, you can try to use nodes OutputSwitcher instead of nodes Selector. With those nodes you can define, to which output an object should be sent. In your case, if you choose not to send the line to generate the wall, then the wall remains empty. Please check if that helps.

Product Owner API, Allplan GmbH

Adjuntos (1)

img
Output Switcher.png
Type: image/png
Descargado 103 veces
Size: 111,44 KiB
Xinling
Xinling
26.09.2022 - 16:14 * [Solución]

Cita de: DGeorgiev
Is there a way to make an “optional” wall using VS while it remains as wall, not Python Part?

Currently, all architectural elements (incl. column, wall, beams) will be generated as a native Allplan object. They won't be included in a PythonPart object.

Cita de: DGeorgiev
- Invalid input method: I have a switcher which I feed to the Wall’s path. When I feed a line, it gets generated, and when I feed an invalid input (point or constant 1) it crashes. It can be reproduced by disabling the inner wall generation.

I checked your "invalid input" script. Perhaps, you can try to use nodes OutputSwitcher instead of nodes Selector. With those nodes you can define, to which output an object should be sent. In your case, if you choose not to send the line to generate the wall, then the wall remains empty. Please check if that helps.

Product Owner API, Allplan GmbH

Adjuntos (1)

img
Output Switcher.png
Type: image/png
Descargado 103 veces
Size: 111,44 KiB
DGeorgiev
DGeorgiev
27.09.2022 - 08:25

Cita de: Xinling

I checked your "invalid input" script. Perhaps, you can try to use nodes OutputSwitcher instead of nodes Selector. With those nodes you can define, to which output an object should be sent. In your case, if you choose not to send the line to generate the wall, then the wall remains empty. Please check if that helps.

Thank you, now it works like a charm.