0.2.0 second beta

[MolotovCherry]

Biggest feature is that now are included many different ways to manually destroy wands. The reason you need to do this is because JVM can't GC these since they need to stay alive, and finalize() is an incredibly unreliable, broken method, which even causes objects to be slower (so, I removed finalize(), which means, faster objects!).

You shouldn't rely on Magick.initialize().use to terminate() every time, because, realistically, apps get big, and you can't put it all your code in only one block. (And you should never terminate until you're actually done using things; it's a waste of CPU)

That means the only previous way was to call wand.destroy() on every single wand, which is very verbose, and you may need more options. Now, you can destroy all wands of a certain type (MagickWand, PixelWand, DrawingWand), clear all wands Magick.destroyWands(), and you can even access the internal id of the wand and destroy by id, (you can also batch destroy by ids).

Changes:

• Remove finalizer on Kotlin (it's EVIL. It slows things down, and it doesn't even work)
• • The solution is to destroy() things yourself (there are many way, see the example)
• Updated examples
• Panic now displays actual error message in exceptions
• More proper formatting of error messages
• Internal wand ID is now accessible from Kotlin (see why below)
• You can now destroy wands in MANY different ways. By ID, by IDs, destroy a specific wand type, or destroy ALL app wands
• • This is important as you will need to manage your memory in your app. JVM doesn't GC these wands
• Fix wand.destroy() method to actually destroy memory

Full Changelog: 0.1.0...0.2.0

---

This discussion was created from the release 0.2.0 second beta.