Open TGSParth opened 9 months ago
Hey, radio buttons are not different then let's say checkbox field(if the possible value is true,false,null), text field if the value is text or decimal if the value is number. Radio buttons have always a single value at any given moment, so I do not see trouble for using this with one of the three fields above.
There is a difference between radiobuttons (generally a list) and a checkbox. A checkbox can have a boolean value only (true/false). There's no "null" for a checkbox. With a radiobutton list, there is the possibility that the user did not select any of the options, thus the result could be null.
In this case make the field checkbox which is not required. This will create a boolean field in the database which can get the true false and null values
How would a checkbox result in a null value?
The checkbox cannot, but a select or radio list with Options like "true", "false", "" can do the trick.
Hey, radio buttons are not different then let's say checkbox field(if the possible value is true,false,null), text field if the value is text or decimal if the value is number. Radio buttons have always a single value at any given moment, so I do not see trouble for using this with one of the three fields above.
I appreciate your perspective on using radio buttons with different field types. However, when considering scenarios like gender selection where options are more than just true/false/null, it might not align well with checkboxes. Additionally, I'm curious about your thoughts on handling a signature pad; any suggestions?
I have no experience with the signature pads, and cannot help there
The current issue revolves around the absence of a designated field type for radio buttons in the entity field creation process. While the design aspect includes provisions for radio button fields, the entity creation phase lacks a corresponding feature. To address this, we need to incorporate radio button fields into the entity creation setup. Additionally, there's a lack of support for signature pad functionality. We must explore options to integrate signature pad features into our system for comprehensive functionality and user convenience.