tag:blogger.com,1999:blog-6266231010760265271.post5272290029627502914..comments2024-03-28T05:23:13.144-04:00Comments on Bekwam Blog: InvalidationListener Not CalledCarlhttp://www.blogger.com/profile/15013889141640529637noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6266231010760265271.post-89298217902848295972015-09-23T10:44:41.371-04:002015-09-23T10:44:41.371-04:00Great, thanks for your kind and quick confirmation...Great, thanks for your kind and quick confirmation. Will integrate that habit from now on.tlafayehttps://www.blogger.com/profile/13309555018298006441noreply@blogger.comtag:blogger.com,1999:blog-6266231010760265271.post-44971670326264241052015-09-23T09:11:13.296-04:002015-09-23T09:11:13.296-04:00Yes. I always use WeakChange / InvalidationListen...Yes. I always use WeakChange / InvalidationListeners unless I plan on manually disposing of them.<br /><br />We're taught early on that Java garbage collection will handle all memory management. However, you can still get memory leaks. The weak listeners help the JVM to untangle an object graph that is a cycle. Weak listeners allow one side of a reference holder to defer to the other when an object graph is freed, breaking the cycle.Carlhttps://www.blogger.com/profile/15013889141640529637noreply@blogger.comtag:blogger.com,1999:blog-6266231010760265271.post-23662503472079423792015-09-23T07:52:03.524-04:002015-09-23T07:52:03.524-04:00Love your blog and nice post indeed! As I am fairl...Love your blog and nice post indeed! As I am fairly new to advanced programming and new to JavaFX, am I right by reading documentation that we should also use WeakChangeListeners over ChangeListeners?tlafayehttps://www.blogger.com/profile/13309555018298006441noreply@blogger.com