On Fri, 11 Oct 2024 18:59:43 GMT, Michael Strauß <mstra...@openjdk.org> wrote:
>>> So, inside of the single event filter, I'm going to call requestFocus() on >>> the next element as dictated by my business rules. >> >> so basically reinvent TraversalPolicy? > >> > So, inside of the single event filter, I'm going to call requestFocus() on >> > the next element as dictated by my business rules. >> >> so basically reinvent TraversalPolicy? > > It's more like the existing tools are sufficient for this particular > scenario. Or put another way: a custom TraversalPolicy is not less complex > than what I've described, since it needs to solve exactly the same problems > (namely, selecting the next input field according to business rules). > @mstr2 thank you for clarification! > > and if we assume that we won't be adding these properties, the use case you > describe should be covered by the > `TraversalPolicy.selectFirst()/.selectLast()` ? If `selectFirst()` is called as an entry point, then yes. ------------- PR Comment: https://git.openjdk.org/jfx/pull/1555#issuecomment-2407973525
