Wrong button order in option panes.

[mgarin]

Wrong button order in option panes.

[ianp]

OK, after a bit of digging it seems that setting the UI default OptionPane.isYesLast to true does enough for my current use case. I'll leave it up to you to close this issue or not, as button order on dialogs is really a fairly complicated subject and a simple yes/no option doesn't cut it.

To give you a taste for the complexity, here is the Windows button order string from MIG Layout, where each character has a different meaning: L_E+U+YNBXOCAH_R crazy huh!

My suggestion would be to look at the MIG Layout implementation, but rather than using layout constraints you could look in either the action values or the component client properties for tags and then order the buttons based on that.

Or just mostly ignore the issue like most other L&Fs ;-)

[mgarin]

I will think of it, but not sure yet.
I might add system-dependant buttons order into WebLaF with some of next updates.

Anyway, i will notify you about the changes made if there will be any.

[ianp]

OK, cool. I may have some time to have a go at implementing it myself later this week.

[mgarin]

I have added proper "OptionPane.isYesLast" value depending on user's platform. This might be enough to solve the issue or might be not. That is your call :)