I'm using Slick-UI in a professional project and I found some issues. Made some workarounds to handle them.
There's no destroy method for Slick-UI elements. (I think putting visible = false it's not much acceptable due to resource usage reasons). I implemented a basic one for SlickUI.Element.Panel. (Most used element I guess).
There's a reference to Phaser.Gameelement in SlickUI.Keyboard.Key, that doesn't work in some environments. In the code it references to "game", that didn't work when game is not defined as Phaser.Game. Replaced with Slick-UI Phaser.Game reference (plugin.game).
Looks like I missed the reference to the game variable in the SlickUI.Keyboard.Key when cleaning up that stuff. Destroying panels does seem useful, so this can be merged :)
I'm using Slick-UI in a professional project and I found some issues. Made some workarounds to handle them.
There's no destroy method for Slick-UI elements. (I think putting visible = false it's not much acceptable due to resource usage reasons). I implemented a basic one for
SlickUI.Element.Panel
. (Most used element I guess).There's a reference to
Phaser.Game
element inSlickUI.Keyboard.Key
, that doesn't work in some environments. In the code it references to "game", that didn't work when game is not defined asPhaser.Game
. Replaced with Slick-UIPhaser.Game
reference (plugin.game
).Any improvement to the code will be appreciated.
P.S. That's a good lib :) Good work!