Actually, it may be pretty easy. The view transitions create a StackPane for the animation. We can probably just add clipping to that pane to fix the problem.

We'd probably want to make it optional in case someone does want this overlapping behaviour.

Hopefully I'll have time to look at it later

definitely make it optional in case someone does want a full sized panel to wipe across the app

@Ruckus maybe a CSS-style overflow setting could address this globally?

...something like overflow=scroll, hidden, auto, visible. "visible" is default which means that the content will be seen regardless of layout boundaries

Is the

ListMenu.activeItem

intended to be re-assigned after an initial assignment? I'm seeing it work the first time, but subsequent assignments appear to have no effect. I stepped through its `activeItemProperty`'s setter when it's receiving a new

ListMenuItem

, and it's definitely getting called, doing its work, but effects no change on screen.

It's too bad, that

internal var TableColumn<*, *>.resizeType: ResizeType

, I need to copy

resizeType

from one column to another. Or is there another way to clone a column (of

TableView

)?

@carlw Hi Carl, sorry for delayed feedback. But thanks for your help. The slide-in of the subview works fine. I think without your help I could'nt solve that. Great! 👍❤️

glad to help. i think something like this will find its way into the toolkit. it doesn't appear intuitive unless you know about the terms of the translateX/Y properties.

Why JFX's method

PrinterJob.printPage(Node)

prints node (

TableView

in my case) with underlying parent? So if the table view is in the middle of

HBox

, then the free space around the table view will also be printed 🔥

May it be 'cause of scroll pane?

ScrollPane

does the right thing, but such containers like hbox or vbox, are getting printed with table view, spoiling margins

Anyone know why when I call

primaryStage.height

in the first View I populate my app with it returns

NaN

? Am I missing a lifecycle thing here? I thought that the stage height was already set before the View is instantiated?

Maybe stage's width and height are not being assigned? Some day I tested assigning

println

to root's width property - it showed 3 times width change before the window appeared (0, 1, 640 - it's another story of the platform secrets)

A few notes on Stage and View 1. The buck stops with Stage. Stage mirrors an OS window. If you want to set the minimum size of the app, use the Stage settings. Nodes also have a min setting, but that won't prevent the OS handles on a window from being displayed. 2. There's a Scene. This is an ambiguous construct that's somewhat hidden in TornadoFX. Before SubScene, this was the only way you could adjust the viewpoint of the graphics. This ends up not being an important distinction in most apps, so the one-to-one relationship that occurs between Stage - Scene - Parent turns into just Stage and root in TornadoFX. 3. Put global stuff on Scene. A Scene is a great place to put app-wide event handlers like keyboard shortcuts. It gets the first crack of the capture events before passing along to root and children.

4. Constructor vs. OnShown. In the Type Safe Builders, you don't have access to all the screen geometry that is being prepared and will be realized long (in computer terms) after the Scene Graph is built. Almost all of my initialization appears in OnShown. That gives me the opportunity to put in progress bars. The Stage methods like init() were once used when combined with a preloader, but I haven't seen this in a number of years. Putting stuff in the constructor or builders may delay the showing of the window.

@Shan putting reply here since the thread doesn't allow formatted code

@carlw Thank you for the explanation! It makes much more sense now.

Hello. Is it possible to rotate column header for tableview 90 degrees?

Could you please give me an example how I can do that?

@Mike Here's a sample Kotlin program with the style set as @abhinay described

Amanda’s talk is released:

lol @amanda.hinchman-dominguez’s theme music!

70's

OHHH

wow.... this is what my sick voice sounds like

I love the 70s theme for sure!

@gtnarg maybe your onDock problem is related to showing versus shown?

@carlw interesting you say that - shown does fire correctly - but the

onDock

functionality is dependent on the

showingProperty

i thought we were using onshown....i never use onshowing in my javafx code