@Carlton Whitehead No, the TornadoKeyboard didn't exist at that stage. I now have 8, with different switches and different iterations of the PCB and other components. We're soon ready for mass production now 🙂 We will sell it as a kit with your choice of switches, everything else is ready. Just chuck in the switches in the top plate, solder them on to the PCB (easy, even for beginners), put on the keycaps and pop in 5 screws to attach the PCB/plate to case and you're done 🙂 It will be sold as a complete kit, including the wooden hand rest. The case is Aluminum.

(Carl's is a prototype with a 3D printed case, but fully functional and programmable in every way). Working on the UI 🙂

I added the program I posted yesterday about OnShown to the FXDocs project : https://fxdocs.github.io/docs/index.html#_timing

It's straight-up JavaFX but applies to TornadoFX init(), createPrimaryScene(), and onDock()

@edvin I'm not sure if you have a Linux box around, but I'm getting some differences in the onDock method which is chained to the OnShowing event. On Linux, this code produces values "480,320", but on Windows, I'm getting a pair of NaN's. I verified through the debugger that both methods are called.

Is there a 'canonical' way of creating a custom menu item in TornadoFX? I need to create a few menu items that I can call

setHideOnClick(false)

on.

shownX, shownY are SimpleDoubleProperty fields

@edvin If I put an OnShown handler directly on the primaryStage, then I get dimensions in the Windows example. However, they aren't the Scene dimensions but have some extra height and width. I figure that Windows is adding in the title bar and window handles.

@melston Have you seen the item() technique? At one point, you used menuitem() as with any builder, but now you use a general item() object.

@carlw, I'm using

item

now. I have

item(...).action {...}

. I'm not sure how to turn an item into a

CustomMenuItem

, though, so I can call

setHideOnClick

.

...checking

@melston I don't see a builder for customMenuItem() so this code creates one by hand. If you click on "Operation" and stay on the Label, the Menu will stay up. There is different than clicking "Normal". Even if you stay with in the bounds of the text, the Menu will close.

@carlw, I don't know if this is the best way or not but I took the existing

Menu.item

extension function and put this together. It seems to work.

@melston You can request a builder to reduce my syntax. It ought to look something like customMenuItem { isHideOnClick = false setOnAction { println("here") }

@melston your code looks fine to me

Ah, good. Thanks.

probably would need to open up the hardcoded Label() on Line 2 for the toolkit though

Not sure what to do about that. I tried without the Label and couldn't get it to work. Didn't try very long, though.

@edvin have you considered using CustomMenuItem for the item() builder rather than MenuItem()?

@melston try this for a non-Label example

@carlw, so any node (not just a label) can be used, but it requires a node. The 'standard'

item

has both a string and a node parameter.

MenuItem

takes both.

CustomMenuItem

only takes a

Node

, it seems.

@carlw, is this more like what you had in mind? I make use of the

graphic

parameter if it is non-null. Otherwise I use the

name

parameter.

@melston yeah. are you going to submit a PR?

it could also be added to the menu / item() builder

@carlw, I forked the repo, made the change and submitted the PR.

Any ideas on how to make ControlsFX BreadCrumbBar look pretty as a DSL?

@thomasnield uploaded a file: Untitled