color of selected rows depend on theme color

Hello Hugo!

That is correct, see point 8 of this blog about the UI changes for explanation.

The whole concept is that color setup is made as simple as possible, whereas the menu deliberately gained a color background to make it possible to look distinctively different from the data (in forms and grids etc) where we want the users to look at (the prior version of the Universal UI had the same background color as the data, making it cognitively the same and adding strain to the users).

Can you tell us the reason you choose a light color for the menu? 

Thanks for answering Bart.

The first time we opened the 'new’ gui the color setting was bright blue. The impact on user experience was huge in my opinion (and I was not alone here ;-)). The first thing we tried was to make the color less intruding, so we chose a lighter version of blue. That was much better but than we noticed the contrast of the filters and the contrast of the selected rows was very low. 

Effectively, we can only choose a darker color for the light theme and a lighter color for the dark theme. The only reason for the limitation being the fact that we cannot control the contrast of the selected rows or filters seperately.

I think we have found a color that is less intruding and still offers a good contrast on the rows. Basically a color with less luminance, that seems to do the trick.

We are curious about the opinions you received, what were the initial opinions and what was it after a longer period of use of these UI changes? 

The base of the UI color addition in the menu background was to lessen the strain of the users’ mental load (in the old style, and with a lighter color, the menu quickly becomes another area of data presentation) By using a darker color for lightmode (and lighter for darkmode), it quickly becomes an area not constantly drawing attention, which we highly encourage.

And the answer to your initial question is no, it is not possible to setup the (contrast of) colors separatly for menu, prefilters, rowcolor etc. If this is a feature you are missing we ask you to raise this as an idea, so others have the chance to react on it.

​@Bart Metselaar overall the active row color works great, but it doesn’t really work well with conditional layout background colors that span the whole row. Is this something that will still be looked at?

​@Freddy what do you mean with “doesn’t really work well”? Since Release 2024.3.14 the Active/Selected state should override the Conditional layout, as described in the Release Notes. Before this fix there was no clear visual indication of a Conditional formatted row being selected or not.

• When selecting multiple rows with conditional layouts in a grid, only the active row was highlighted as selected. The conditional layout would override the styles (row background color) of the other selected rows. This has been fixed.

We did not have the chance yet to collect opinions over a longer time. I will get back to you in a while and monitor the user experiences.

That would be really great, thanks!

​@Arie V ​@Bart Metselaar basically it starts with the inability to steer column headers.. so we have to create one..   and before the change it didn't work well either.  But consider this scenario, which happens more often. 

As we cannot steer column names, we have to create a header row with in this case the date of values. For visual purposes we want it to be darker of color (light theme for example). Basically when you open the screen it shows the first row.

This one looks odd because it's a tint of the primary color..  Wouldn't it be more logical to follow the primary color but if there is a full row background color it should adjust itself based on this color? 

When I move to the next line it becomes clear it's a header row. 

​@Freddy With all due respect, but also the second image looks odd to me. Too bad you need such a solution… For such an edge case we are not going to change the current behavior. Would rather have you raise an Idea in which you explain the various Use Cases where you use this and request a better solution from Thinkwise.

P.s. If you don’t want the first grid line to be in selected state, maybe consider to add a Process Flow with action Go to next row on Open Document / Activate detail.

​@Arie V probably odd due to lack of context. Basically this is a cube in a grid form where years are pivoted because I need the 'dimensions' with the actual read financial information from the balance sheet. (a cube cannot do this, it will aggregate). Also the cube doesn't have the 'tabular layout' (see excel) that denses the information shown.

Unfortunately no time to make such an elaborate idea, maybe later in the year when I'm less busy.