Parameters of scripted component (mcu)
![arcachofo](https://simulide.com/p/storage/ultimatemember/2/profile_photo-80x80.png?1725762710)
Quote from arcachofo on January 9, 2024, 10:36 amThose are strings, but what if a list of addresses in ram/rom or the number of bits (8, 16, 32) or even different voltage levels shall be selected?
The component handles it.
The list of options are always strings, so the property widget should covert those values to strings.
The amount of posible cases are huge, for example: how the list of values should be represented? Decimal, Hex, Binary, float? how many decimals? or which kind of HEX representation? how many bits? what if there are units like Volts?, etc, etc, etc.It is much easier that the component set a list of strings for the list and do whatever it needs with the string received.
Because components knows exactly what they need, but the property has no idea of what the component wants.
Those are strings, but what if a list of addresses in ram/rom or the number of bits (8, 16, 32) or even different voltage levels shall be selected?
The component handles it.
The list of options are always strings, so the property widget should covert those values to strings.
The amount of posible cases are huge, for example: how the list of values should be represented? Decimal, Hex, Binary, float? how many decimals? or which kind of HEX representation? how many bits? what if there are units like Volts?, etc, etc, etc.
It is much easier that the component set a list of strings for the list and do whatever it needs with the string received.
Because components knows exactly what they need, but the property has no idea of what the component wants.