We have added header section for parameter tab deliberately so that we can force user to select parameter name (and therefore parameter's data type) before adding new row. This is required because behavior of second cell (Value cell) is dependent on what parameter name user has selected in first cell (Name cell). See attached screen-shot.
For example: 1. If user selects parameter 'array_nulls' then value for this should be either true or false (and hence switch cell). 2. If user selects parameter 'cpu_index_tuple_cost' then value for this should be Integer (and hence Integer cell).
Without the custom header (and forcing user to select parameter) we cannot decide what type of cell we need in second column.
Let me know your opinion on this.
We need to figure out a way to fix it. Our difficulties encountered writing code should not dictate usability compromises.
In this case, something that needs some thought and maybe some tricky code has caused us to create an inconsistent UI workflow to side-step the problem, which is not appropriate as it leads to a poor look and feel and potentially confusion for the user.
Agree - we should handle these cases gracefully.
We need to over come the limitation by brain storming, which we already started offline. :-)
To be honest - it is a time consuming work, and there is no quick fix for this.
We can handle it as one case for each change instead of targeting all UI changes as one whole problem.
And, we can utilize the same time to fix a lot more cases in beta 2.
I can ask Harshal to find out all possible places, where the similar changes are required, and create a separate case for each (though - not without your agreement).
