pmonstad : a question : what do you think of this : make all screen have 2 sets of button (same :
One at top like actually + one at bottom (like some screen in 2.06 part) .

It's a question.

I'd prefer to have three buttons on each screen: Save, Save and close, Close. I'm not sure why there are some screens with an extra button "Return to...".

I think those three buttons should be enough. Screens are very compact, and I don't know of any screens where users have to scroll down a long list. If there are such screens it could be a point to repeat the buttons in bottom right corner.

The Return to... button should not be necessary as the close and Save and Close buttons should have the same effect. What is the difference between close and return to...?

If we can agree to one standard for button appearance on screen I think we have made the gui a lot more standardized. Now there a too many variations around the gui.

This is my opinion, but I feel there should we a discussion about this at this point in development. 2.5 seems to be focusing on gui and a standard layout on screens is very important.

There are some screens where Save and Save and close should be replaced by Import. Two buttons in upper right corner: Import, Close.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=17519

Denis, I was thinking about that too. The work-flow is from top to bottom - it would then be convenient to have a save button just below the last field. But the save button in the upper right corner is still useful, since it's everywhere.

Hi olle : in all forms i found on web (example or not) : we have

The option block : fieldset / input / etc ....

At the end : the action button

Example 1 : http://getbootstrap.com/customize/
Example 2 : https://github.com/settings/profile
etc etc ....

SOmetimes we have :
Form1
action for form1
Form2
action for form2
Form3
action for form3
Actually : only LimeSurvey have action button on top. It's not standard ..... And really not usuable/accessible

I already put a bug with this , but closed

Really think the best is the screenshoit i send to you.

I already open a bug report for this : have 2 set of button : one standard + one quick access. But this bug was closed.

Well, if the form is several pages long I think it's motivated to have a fixed bar with save-buttons.

Maybe we can talk about it on the next meeting.

I'm OK for a fixed bar (see default SkeltonQUest : previous/next can be at top in double).
But really think it's standard to have the button at end of the form.

Version 2.50+ Build 160222 released