Hi all,
1) recent defined color (value !== null) behavior ok
mouse on, mouse out on recent defined color => change previous new color
zone = good
click on recent defined color => change previous new/old color zone, set
value with the new
and close widget => good
2) recent not defined color (value === null) behavior not ok
mouse on, mouse out on recent not defined color => change previous new
color zone but color is not defined! => wrong
click on recent not defined color => change previous new/old color zone
and
set value with the new but color is not defined! => wrong, widget doesn't
close => good
IMO, 1) => ok, 2) => do not anything (don't modified old / previous color
zone or value). Maybe add a new button "no color" to set value "null".
I know that background color (or other) can have "null" value.
Show this exemple: Is my last recent defined color is white or null?
Playground <http://tinyurl.com/kow3pcc>
3) autoHide
Even if autoHide property is set to "false", widget disappears on color
selection (of course not disappears to lose focus) because
qx.ui.control.ColorPopup.js line: 355 :
if (vValue) { // => if( !!vValue && this.getAutoHide() )
this.hide();
}
Could you enlighten me?
Regards
Jean-Luc
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/ColorPopup-strange-behavior-2-1-1-master-tp7583912.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
