I’d like to inquire about the most efficient way to build a table with multiple enum questions.
In my case, I have a “Settings” table with several different enum columns. Some are “On, Off”, one has a list of four different text sizes (with text names, not just numbers), another has a list of time zones, and another has a list of languages. The easiest way to build the table is to put enums with different contents into separate columns. With the settings I’ve just described, that would be at least 4 columns.
What bothers me is making a separate column just for one settings, such as the time zone setting. I was looking for a way to have heterogeneous enum lists within one column. Today I thought I had found the solution in something that @Fabian wrote:
This works quite well in button enums of the kind that @Fabian demonstrated. Unfortunately, however, I encountered a problem with dropdown enums. First, here’s what I want:
Unfortunately, however, when I try to use the “suggested values” spot to control what is displayed (so that I can have different enums in the same column) the “Search” area becomes “Add or search”:
As my app is not designed to allow people to invent their own time zones, I don’t want this. By the way, this happens even though “Allow other values” is off.
I think this is a bug and I think it means that it’s probably better to use a single column for one enum in just one row. Here are my questions: Am I right about this? Is is better to use multiple columns even though it seems sort of inefficient? Also, is there a way around the problem I encountered?