Channels
#tornadofx
- a
amanda.hinchman-dominguez
12/27/2017, 12:53 AMI was just reading it! - a
amanda.hinchman-dominguez
12/27/2017, 12:53 AMStill going through it - c
carlw
12/27/2017, 12:53 AMi put event filters on which intercept the events. you can stop the processing with an evt.consume() - c
carlw
12/27/2017, 12:53 AMfilters=before; handlers=after - a
amanda.hinchman-dominguez
12/27/2017, 12:54 AMah, I was having a hard time understanding what exactly is evt.consume(). You see, right now, I can drop the tile (not in a place where I can control yet, although I can remove the tile in the appropriate spot) - c
carlw
12/27/2017, 12:54 AMi'm not sure if you ran into this yet, but there's no concept of propagating to sibilings. for example, a game piece in front of a square - c
carlw
12/27/2017, 12:55 AMthat's why i took a step back and dealt with events at a container level and dispatched them accordingly. then, it was on me to make sure that the event target was associated with the right child Node - c
carlw
12/27/2017, 12:56 AMi'm going to add to my examples, but i'll put some events on the Nodes themselves like you've done up to this point. for example, toFront, toBack, delete can all go on a context menu event that's on the node itself. - a
amanda.hinchman-dominguez
12/27/2017, 12:58 AMhmmm, yeah that's too bad - I was actually trying to find an equivalent to javascript's e.stopPropagation() earlier - c
carlw
12/27/2017, 12:59 AMthat's equivalent to evt.consume() - c
carlw
12/27/2017, 1:00 AMi think javafx is richer because you can work the two directions; filters before the normal event processing; handlers after the normal event processing. if anyone calls evt.consume() along the way, processing stops - a
amanda.hinchman-dominguez
12/27/2017, 1:05 AMalright. I'll need a bit of time to read through the documentation, let me get back to you on it! - a
amanda.hinchman-dominguez
12/27/2017, 1:25 AMokay, so I'm trying to understand what I'm reading and what you're saying - what I'm using right now is an event handler for the button (i.e. setOnAction), so eventFilter will always come first. What I need to use instead is an event filter for the button so that the filter can occur first in the button node before the class event filter - a
amanda.hinchman-dominguez
12/27/2017, 1:26 AMor, I could have the event consume if the target is a button - c
carlw
12/27/2017, 1:51 AMfilters first - a
amanda.hinchman-dominguez
12/27/2017, 1:53 AMawesome. thanks. I'm taking my sister to get some dinner back when I get back I'll work on it👍 1 - t
thomasnield
12/27/2017, 2:29 AM@edvin btw agree on killing the Google groups. Stack Overflow and Slack is more than enough, and even GitHub.👍 1 - a
amanda.hinchman-dominguez
12/27/2017, 2:52 AM@carlw replaced setOnAction with an event filter and it solved the problem with overriding filter events. I'm committing my code and also posting a snippet if you want to add it to your blog - a
amanda.hinchman-dominguez
12/27/2017, 2:53 AMThe documentation was excellent, but the ONLY small detail that left me a little confused was the fact that the grid had been made horizontally, I wasn't sure whether it ought to be read left to right or right to left haha - a
amanda.hinchman-dominguez
12/27/2017, 2:53 AMperhaps a better interpretation is a hierarchy top to bottom - a
amanda.hinchman-dominguez
12/27/2017, 3:00 AM@amanda.hinchman-dominguez uploaded a file: Untitled - a
amanda.hinchman-dominguez
12/27/2017, 3:01 AMI highly recommend looking at the rest of the class as well. I managed to get the drag and drop partially working. Not quite as intended but I have about half of the snap-to-grid functionality coming along - a
amanda.hinchman-dominguez
12/27/2017, 3:09 AManimate still not happening, I'm probably working on that next. - a
amanda.hinchman-dominguez
12/27/2017, 3:12 AMI created the Tile and added it to the root, but can't quite figure out why it isn't rendering yet - u
user
12/27/2017, 4:19 PM@kastork commented on @amanda.hinchman-dominguez’s file https://kotlinlang.slack.com/files/U78L28DMX/F8LG6G5AT/no_onstartdragging__but_no_event_either.kt: This an interesting snippet. It never would have occurred to me that I could use
the way you do in the builder.circles.add( this ) - u
user
12/27/2017, 4:45 PM@amanda.hinchman-dominguez commented on @amanda.hinchman-dominguez’s file https://kotlinlang.slack.com/files/U78L28DMX/F8LG6G5AT/no_onstartdragging__but_no_event_either.kt:
can be useful! I'm not sure about the full extent of usingthis
in TornadoFX, but I assume it works similarly as a java class, only with different annotation. This instance allows me to refer to the class I'm currently working with as opposed tothisMetroTileHomepage::this - k
kastork
12/27/2017, 4:49 PMThe magic of extension functions with receivers. - k
kastork
12/27/2017, 4:49 PManyway, it is a slick way to stash a reference to a UI element that you might want to get at from other code👍 2 - c
carlw
12/28/2017, 3:21 PMThis is an advance copy of my next blog post on selecting items on a canvas. I'm using the same strategy as I did with the last drag article and testing and manipulating the objects through a parent container. Also, I put a flat, non-graphical model view on the right side so readers can visualize how to get at the selected items without dealing with the Scene Graph. - t
thomasnield
12/28/2017, 4:17 PMSo apparently JB provides a tool to generate a Kotlin Native interop library from a C header file. Might be something to try with Nuklear. https://kotlinlang.org/docs/reference/native-overview.html