maybe we can add condition too (and a button for edit ?)

5X.png (25,276 bytes)   

5X.png (25,276 bytes)   

6X.png (25,786 bytes)   

6X.png (25,786 bytes)   

When editing advanced settings : no speed way to verify the question currently edited .

Really hard for Equation for example

Capture d’écran du 2023-12-20 10-32-10.png (23,759 bytes)   

Capture d’écran du 2023-12-20 10-32-10.png (23,759 bytes)   

@DenisChenu let me know if you want to talk about "how to fix this" from design perspective.

?

Capture du 2024-02-26 16-06-58.png (44,279 bytes)   

Capture du 2024-02-26 16-06-58.png (44,279 bytes)   

@tibor.pacalat : OK for such design ?

Why does type of question have green border, but it looks like a button and disabled?

If it can not be changed from this screen, then it shouldn't look like a button. Plain text should be fine.

Why does type of question have green border, but it looks like a button and disabled?

I just copy paste the current one for activated survey : it's the boostrap theme

If it can not be changed from this screen, then it shouldn't look like a button. Plain text should be fine.

It can be open if survey is activated

Stage btn-block don't seem to work

Capture du 2024-02-29 17-00-18.png (24,422 bytes)   

Capture du 2024-02-29 17-00-18.png (24,422 bytes)   

Capture du 2024-02-29 17-06-27.png (15,909 bytes)   

Capture du 2024-02-29 17-06-27.png (15,909 bytes)   

Capture du 2024-02-29 17-09-10.png (17,604 bytes)   

Capture du 2024-02-29 17-09-10.png (17,604 bytes)   

Adding condition just after Question text ?

This one looks fine, you can add condition after Question type in the same row. Look that it is responsive as possible, thanks!

Screenshot 2024-02-29 at 17.15.31.png (34,744 bytes)   

Screenshot 2024-02-29 at 17.15.31.png (34,744 bytes)   

Unsure about condition

Ping @Mazi : what your opinion about the place for Expression manager condition textarea ?

I think it is difficult to differentiate. One could argue that mandatory setting is also a core detail and should be moved to the left.
I will leave that to the design experts.

I will leave that to the design experts.

It's not design here : ergonomy. And for ergonomy you need feeback by real user ;)

Lets'start bye code + type :)

Thank you

Unsure on the good concept here …

Some user search it at right where you have all settings, and some other user at top before question text (primary settings).
Maybe need more user test ?

@DenisChenu, I recommend following the way you read. We usually start with adjusting the question code, so having that top left is fine. Then selecting the question type is the next logical step followed by entering the question text below.
The settings on the right are often not touched at all so placing the elements as shown at your screenshot makes sense!

The settings on the right are often not touched at all so placing the elements as shown at your screenshot makes sense!

Yes, but helping a new user, she search on this place to update Question type.
I know you do a lot of training : what seems to be te choice of user ? You confirm the «Have the most important things in the middle part» ?

From my experience with recent training for LS 6.x users are a little confused with the right side. It mixed core elements (question code and type on top) with a large list of additional options. To placing the core question code and type field above the question text editor is a better design from my point of view.