Hi Fam, Why is it that an input reads null inside an Imperative Function? For example: This would work, with input being driven by any integer manually or by slider. input; output = [Imperative] { if (input == 0) { output = “ZERO”; } return output; } Successfully returns “ZERO” However…

I tried on another machine and it seems to be working now. Very strange why does a code block behave differently on another machine? Anyways looking at your code, couldn’t it be simpler to do this? Why do you have different return outputs and two ending semicolons? [Screenshot_1]

Input in Imperative Function

DesignScript

Ahmed_Ramy July 27, 2022, 10:00am 9

Hi All ! I have the same issue here and can’t reach a solution. Any help is needed

Topic		Replies	Views
DesignScript Question DesignScript designscript	7	1073	June 25, 2019
Null values in Imperative block DesignScript	2	779	April 6, 2020
Understanding DesignScript, "return [Imperative]", and "if-else" Better Lists-Logic designscript , dynamo	7	247	May 11, 2023
[imperative] blocks behaviour DesignScript designscript , bugs , dynamo	2	1214	April 10, 2017
For loop problem in design script Lists-Logic	4	1981	April 23, 2018

Input in Imperative Function

Related Topics