mstr2

> This is basically another case where it is better to only listen (or bind) to other targets when absolutely necessary (when the source itself is being observed) and to...

> I had a look at the PR. But it took quite a while to fully understand the changes (also the current implementation 😄). I think it make sense to...

@Maran23 Would you be interested in reviewing the implementation and the added documentation?

I've expanded the documentation of the improved algorithm, which hopefully makes it easier to understand the changes.

> When a null value is possible, guards against are needed. Unfortunately there is no built-in way to forbid null in Java as whole. I think null checks should only...

Here's an update on the current state of this feature. The API has evolved a bit to offer more flexibility, and can be used in several different ways: ### 1....

I've iterated on this feature for several months, and I'm quite comfortable with the latest version. The API was changed considerably: there are no "theme URIs" masquerading as user-agent stylesheets...

> This will take a fair bit of discussion regarding how various applications might use such a feature, what the API should look like, etc. > I think there are...

1. In a property setter, you cannot do anything other than call `property.set(...)`, since `setFoo(...)` and `fooProperty().set(...)` must be equivalent. 2. As you discovered, `ComboBoxPopupControl` implements a skin that violates...

At first glance, this doesn't seem to be a good approach to solve the problem, since you're now treating all `WM_TOUCH` events as direct touches, independent of what they actually...