José Pereda

The javafx artifacts for each module like `javafx.controls` come in an empty platform-neutral jar and up to three platform jars. Notice, however, that there is only one pom per module....

Possible fix in `MapView`: ``` protected void markDirty() { dirty = true; Parent p = this; while (p != null) { p.setNeedsLayout(true); p = p.getParent(); } } ``` however `Parent::setNeedsLayout`...

@brunesto We have just merged a pending PR, can you fix the conflicts?

Can you clarify the issue and how to reproduce it?

Thanks, @mipastgt. We are also working on some tooling, still far from ready, but this: https://github.com/jperedadnr/substrate/tree/492-fxml will get the classes and all their methods used in all the FXML files...

Removing the CAP options `"-H:+UseCAPCache"`, `"-H:CAPCacheDir="`, and using `"-H:-UseCAPCache" `(somehow this is required, though by default it should be already false), I get to avoid the CAP cache, which is...

That pic looks awesome! You are right, we are creating two different meshes based on the same 2D grid, and the first call creates `listVertices`, that could be used for...

Is this still something we should implement, or can we close this issue @johanvos ?

We have first bullet in place. Second one leads to a similar discussion as in #34 I believe this can be closed @johanvos ?

Thank you for the detailed issue and logs. If you check the touch points for each event: fiftystates_Samsung.log - 17:28:31 -> Successful list item selection attempt Pushing TouchState.Point[id=0,x=179,y=194]] Pushing TouchState.Point[id=0,x=179,y=194]]...