I have a problem regarding the observablelist hibernate does not recognize them

@mariofelesdossantosjr Target the getters and setters which can expose a normal list

@edvin not to re-open this issue -> https://github.com/edvin/tornadofx/issues/626, seems that whenDocked is called when the window is already shown, so If I want to move it to another position (another monitor) it opens on the same monitor as the first one and then gets moved, which looks not so nice..

@Romanow Can you show me the code you use to move it to the other monitor?

@Romanow uploaded a file: Open on second monitor

@Romanow uploaded a file: Opening new window

Hibernate with property

Just upgraded to the latest Tornado Fx and Kotlin 1.2.0 - am now getting the following error in eclipse. It compiles fine from the command line. This eclipse project is a java project that depends on another project that I have written in Kotlin with Intellij. I posted this issue in the #eclipse channel but from past experience there is no activity there. Where does one get credentials to log an issue on the Jetbrains issue tracker?

@Ruckus commented on @gtnarg’s file https://kotlinlang.slack.com/files/U13A9PZC0/F99V1RYJJ/eclipse_error.kt: You just need a JetBrains account and use it to sign in to YouTrack at kotl.in/issue

@gtnarg commented on @gtnarg’s file https://kotlinlang.slack.com/files/U13A9PZC0/F99V1RYJJ/eclipse_error.kt: Figured out the issue - KClassImpl is now internal. Changed

((KClassImpl<T>) type).getJClass()

to

type.getClass()

@edvin or@thomasnield I have a question about streams: in eventbus.kt[92] and multiiple other places code like this is placed: ?.toTypedArray()?.forEach {. what is the purpose of first converting it to a typedArray?

Let's say I'm making a special type of element that combines a few UI components, would I use a fragment for that?

Or, should I extend a Pane/stackpane etc

@pike It depends on your use case

well, it's a graph that I'll use on many views with different data

@tieskedh I wonder if we were unable to iterate over the result earlier, either because of a missing kotlin feature or maybe we changed the data structure at one place. As it stands now, toTypedArray() should be removed.

I can't stress this enough: Don't instantiate UIComponents manually 🙂 https://github.com/edvin/tornadofx/issues/640

@edvin one more question: can I replace all the HashMaps with normal or mutable maps?

@tieskedh I seem to remember someone warning that MutableMap would be slower than HashMap. I think that's why I stuck with them.

huh, let me check on that, as it's not logical...

@tieskedh

mutableMapOf

creates a

LinkedHashMap

It should be fine to change it IMO

It might even be desirable as we'll get deterministic ordering of keys and entries

saw it, I think Kotlin did this, because of the idea that map etc. should be easy to do

Yeah, it's a good tradeoff, you basically only pay with an little extra memory. For internal data structures where iteration order isn't needed it might be best to leave it alone though.

maybe it's an idea to use MutableMap only as an interface?

Performance is likely to be just slightly below that of HashMap, due to the added expense of maintaining the linked list, with one exception: Iteration over the collection-views of a LinkedHashMap requires time proportional to the size of the map, regardless of its capacity. Iteration over a HashMap is likely to be more expensive, requiring time proportional to its capacity.

meaning, if we iterate, we probably should use linkedhashmap, if we only add and delete, we sould use HashMap

but, other than that, I think we can use MutableList/List as interface instead of the HashMap.

It's more idiomatic Kotlin and the performance impact would be minimal and probably not noticeable, so let's change it