@vlaaad hi again, is there a way for :renderer-error-handler
to know where in the fx-graph the error occured?
Hi! Unfortunately, there is no way to do that.
I understand that it's frustrating, I don't like it too. I thought a bit about the idea of inspector for javafx nodes and cljfx graph, but haven't come up with anything yet. What might be worth exploring is custom debugging fx->lifecycle middleware function that wraps all fx lifecycle with something that allows some kind of introspection. Your use case seems to be expressable with this middleware
Looks like something I will look into when I have a bit more time. Thanks for the tip!
out of curiosity, does cljfx work by creating fxml by any chance?
not sure if it does that or maps the specs to javafx objects directly
No, it is more of a replacement for fxml — more dynamic and clojurey. Cljfx does not depend on fxml at all
It maps props to objects directly
ah ok
For your information, guys: I'm currently developing Reveal tool (Read-Eval-Visualize Loop), it's built on top of cljfx. There is a repo: https://github.com/vlaaad/reveal and a channel: #reveal
@vlaaad awesome!