Re: KeyboardSelectionPolicy BOUND_TO_SELECTION vs ENABLED

I have the very same question. Can somebody please explain this please?

On Monday, November 14, 2011 at 11:40:01 PM UTC+5:30, Raziel wrote:

Hi, could somebody provide a simple but complete explanation, and
perhaps a use case, for the usage of
KeyboardSelectionPolicy.BOUND_TO_SELECTION and
KeyboardSelectionPolicy.ENABLED?

I've looked at the code, and see a number of tickets being resolved
around this concept, but I'm still not clear of the intention and thus
usage of this concept (specially when the enumeration names seem
orthogonal: ENABLED/DISABLED vs BOUND_TO_SELECTION).

Thanks a lot

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.