null vs zero and its treatment

[drakh]

Oh i am struggling with this thing recently.

It is little bit annoying that as it seems for me that modules are in some (probably all) cases treating "zero" input value as "null" - so ignoring the zero. Mostly i found it in patch options - for example position or size options of the patch - when i want set size of patch/container based on some parameters and that parameters has value "0" (yes sometimes i want the size of the patch to be 0) or positioned it on left 0 and top 0 it ignores completly these input values as it was "null" which should be different data types. null should be null and ignored and zero should be zero and not ignored, this briings lots of inconsistency in data types.

should i bug report it ?

[senso]

It's not a bug but a choice. A control panel must have at least 1 pixel size.
A 0 pixel size means totally invisible and will disappear from the interface so the user will not be able to select or dbl-click it... like a phantom patch...