The user is entering a number. That some values are invalid for technical reasons does not change the nature of the user interaction. I would go with an option that is the most natural to enter a number
Perhaps keep a regular number field, but when the user finishes their input, nudge the number to the closest valid option with a minor message to go with it?...
I think a horizontal slider with:
Graduations (tick marks) showing the possible values
A handle with a triangle end pointing to those tick marks
Snapping to the closest possible value when you drop the handle
A feedback of the actual value
Of course, the ability to manipulate with the keyboard
Optionally, the ability to use arrows or +/- to move to the next/...
Elementary factor seems to be fixing the error.
You need some intelligent code that will loop after the collection from * and if it encounters a hole, enter a value less than (index - 1) and greater than (index + 1).
Dropdown with 50 options is too mundane(but it's possible to implement search inside)
DatePicker - sounds reasonably, 2 interactions ...
This is essentially the same as the answer above by @Mohammed Yaseen Ganai, but I felt that some more explanation was in order to really help you understand the suggestion.
The most important thing here is not breaking convention unnecessarily - there already exist UI elements to do exactly what you want to do: Radios and Checkboxes.
There are several ways to go about this. But generally, the current table data entries have no form of hierarchy whatsoever.
So we start by:
1. Creating a hierarchy between the labels and the content: Here I am doing that by font size and weight. The contrast could be created in a lot of other ways though.
2. We then look at the information themselves ...
Is it a web app or a mobile app? Either way, on mobile phones in portrait orientation it is abnormal and inconsiderate to reserve so much screen real estate for a fixed menu. In landscape it might work, but generally and as James Coyle says, a side-navigation can typically be hidden from view with a toggle.
Tabs and Bottom Navigation work well in portrait ...
By general rule, your buttons should look like buttons and your link should look like links. But reality is so that it is not always possible (or even good for your precise situation).
In my opinion, there is no real harm for links to looks like buttons. It's the other way around that is tricky (for the reasons you mentioned).
If you decide to make a ...
The user should not be bothered with your historical reasons for limitations.
Prepare a mapping between valid values and consecutive numbers, e.g.:
Id: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Valid value: 1, 2, 3, 4, *, 6, *, 8, *, 12, *, 16, 17, 18
and present the Id's to the user only ("pick a number between 1 and 50"). Behind the screens ...
If you can combine a normal number input with a drop down menu that greys out invalid number, and centers on the number entered, with up and down arrows that go to the next valid number, that strikes me as the most intuitive.
Vertically below each other in an order that makes sense to your users.
The issue with putting fields horizontally next to each other is that they are sometimes missed.
Have a search for LukeW, he is a UX researcher at Google and has some amazing content on form best practices.
Switches are generally used when there are only one or two options. In this case, there a four options so checkboxes would work better. The options could be made more user-friendly and understandable with the addition of a verb:
Allow multiple valid answers [checkbox]
Allow multiple attempts [checkbox]
Shuffle questions [checkbox]
Shuffle answers [...
Maybe you should concretize the option's choice a bit, this will help you not to spread too much in a multitude of variants.
I think the beginning you raise in your options is almost infinite: choose a font. There are millions of fonts. Instead I would propose something more generic like choosing a global style so this style can come with some default fonts,...
So, is there any UX reason for doing something like this, or is this just bad design?
There is a definite reason for this in my eyes, the learnability of interface and the predictability of the resulting behaviour.
If I have a phone / car etc with "chunks" of fuel, I can begin to learn how long a chunk lasts, "I'm on one bar on my phone" that means I have ~...
Look for all the ways your data can be presented and consider facts as : how many users will you poke the most and the least. Can I poke 500 users or 50000 users ?
What is important for me to see ? Who I poked or who responded or what the response is ?
That will lead you to a more condensed view. Maybe a chart with filters and hover to show info. It ...
Allow only 1 to be locked at a time
Essentially make them radio buttons. It looks like the three variables (rise, run, grade/angle) are one of three things to the user:
I know this value
I'm trying to find out this value
I'm experimenting with this value
If any two of them are the first, allow the user to put them in directly (just have four number input ...