'm getting a VBox with a 0 opacity

HA!

I figured it out. It was a stupid mistake on my part.

In

Node.fade

I was using

target = opacity

in the reversed case instead of

target = this.opacity

.

great

I think it was a mistake when I renamed variables a while ago, but that doesn't explain why I didn't see the change in all the tests I've run since then.

I'll push up a fix

metro and fade create a new stackpane, so maybe that has a different init sequence

Fantastic @Ruckus 👏

@edvin and @Ruckus how is the cross platform testing on Tornado? I've seen odd javafx discrepancies pop up here and there

@carlw I run all my apps on both Mac and Windows, never Linux though. We haven't really had any issues, since most of TornadoFX is simply sugar over JavaFX, but these things needs more careful testing I think.

i can help with the linux testing. unfortunately i've experienced and continue to experience cross platform problems with javafx even without getting into the internals

Fix is pushed

@carlw That would be great.

@Ruckus Sweet 🙂 This was nice to resolve. Great work! OK, I'm off to watch SHIELD 🙂

Good night guys.

@carlw I run the tests on Ubuntu (that's what I currently use at home, though I desperately want to get back to Fedora), but I usually work on a Windows box.

@edvin Enjoy yourself 🙂

@Ruckus good. sounds like a continuous sampling so there aren't any blindsides

It's probably better for you to do linux tests though. I do it less and less often as the machine is slowly dying and it's increasingly unpleasant to work on.

@edvin I run Linux Mint at home a majority of the time, and I do use TornadoFX on it (for my personal banking app I've built). You can always delegate to me if you need anything specific tested, but in general I've had no issues.

@thomasnield Great 🙂 Yeah, most of our stuff is not graphics-related anyways, so we'll seldom run into stuff, but good to know 🙂

@edvin Watch for threading and Swing integration. That's where I've seen problems with an AppKit crash and a GTK run loop hanging. This is even with by-the-book use of SwingNode, JFXPanel, SwingUtilities, and Platform.runLater(). Also, this project is on the front lines for Kotlin/JavaFX integration and may find bugs in the kotlin.concurrent package for example. The #javafx Slack channel points to this one. Finally, there is the odd bug in JavaFX itself. I just had a Linux-only bug accepted involving mnemonics. Even though TornadoFX wouldn't itself fix something like this, it would be helpful to let new users know any underlying issues right away.

@edvin I think WORA, but in practice I Write-Once-TEST-Everywhere. It sounds like a number of platforms are involved in the day-to-day Tornado operations, so you have good coverage.

@edvin @carlw Thanks for the additional discussion about sharing data between views! I'm kinda slowly catching up with the things going on here. 😄 Using jfx properties and binding is another great option for sharing data and stuff. 🙂

@pjozsef If you want examples of binding and Kotlin / TornadoFX, the group on this channel is working on a TODO list reference app https://github.com/bekwam/todomvcFX

@carlw Awesome, I'll have a look at it

@carlw Wow, I didn't know there would still be such issues in 2016, but good to know. I'll install Linux on one of my machines as well and run some of my apps before each release just in case.

@pjozsef You're welcome 🙂 Yeah, properties work great, and ViewModel gives you some extra sugar on top of that, for example the ability to swap the underlying domain object for a shared state holder.

The to-do app is coming along but is on hold and me too as my dog had to be put down with cancer this morning I am not available for a few days while coping with this