@edvin Maybe an EventHandler (not an EventFilter) on the Scene. Have the Scene handle the arrows if nothing intercepts the key event. The Node in the form has the opportunity to consume the event and prevent the transition.

@edvin did you happen to see my question about the scrollpane?

Off topic -> http://download.java.net/java/jdk9/jfxdocs/javafx/scene/Node.html#viewOrderProperty 🙂

This is what @jonathan was talking about. It will be so nice to have.

@Ruckus will this solve the tab order problem (tabbing from field to field)?

No, that is planned for either a later JavaFX 9 update or JavaFX 10

rats

@Ruckus @carlw Thanks for the input, I have some things I can try now 🙂 I'm thinking default to Alt-Left and Alt-Right and make it easy to switch to for example Space and Backspace.

@ron No, sorry I didn't.. Let me scroll back and check (pun not intended, but hard to ignore now)

np :0

hard to go back to java collections after kotlin

@carlw I agree 🙂

@ron As long as the boundsInLocal are larger than the viewport, scrollbars should appear unless you tweaked the default scrollbar policy. Maybe you are drawing outside the size of the component?

@ron Make sure you calculate the preferred size of the DagLayout correctly.

@carlw I defined the keys like this:

@User uploaded a file: Next/Previous keys for the Slideshow

@carlw Then I basically check for key presses on the scene like this:

@User uploaded a file: Untitled

Does that sound OK?

handler or filter?

@carlw It's a filter now (was before you commented) - but why is it better with a handler?

you'd give the underlying controls a chance to intercept the event and stop the scene from using it

don't worry about it. textfields will probably consume it anyway

I changed to

EventHandler

. Let me check if it makes any difference for textfields.

It doesn't appear to make any difference.

Cool, this was great! I think it's shaping up quite nicely. Not very advanced for now, but a good starting point, and I think it will be easy to evolve this API. Will sleep on it, and possibly merge tomorrow, then start preparing for a 1.5.8 release, then create some screencasts and write more in the guide.

I'm thinking the Slideshow could have an observable double property that let's you know how far into the slideshow you are. Would be nice to use with a progressbar in some sort of control with arrow keys etc.

This was the basis for a data migration tool I built. It uses a step indicator as a property since the whole numbers are probably more intuitive. (Slide 1 versus Slide 50%) http://bekwam.blogspot.com/2016/04/javafx-binding-of-step-indicators-in.html

@carlw That's pretty nice. But the approach doesn't scale well if you have many slides, since each additional slide takes up more horizontal space. I've made it possible to add components to the slideshow surface though, and there are properties for

index

and

count

.

can you do a stack pane where the indicator overlays the content if you hover?