Unable to change texture of ninepatchimage

[liang1020]

Hi netcell,

I was impress with the helper tools that you do for phaser. But can i know is there some way that can change the texture of ninepatchimage to do like rollover effects. Or how can i fit ninepatchimage into Phaser.Button.

Thanks in advanced 1st :) Hope to hear from you.

[netcell]

Hi Liang, I am currently very busy with my freelancing work as I just left my previous company and lately not really using Phaser much. Therefore, I can't immediately answer your question. Also, so far on the github repository, the nine patch image plugin has some performance issues. I have fixed the problem and also do the implementation with Phaser.Button on a project on my previous work but didn't have time to do an update on the repo. I would try to update the plugin in a week or two, but in the mean time:1. I would not recommend you to use this on a distribution build for a Phaser game.2. If you need to apply it on Phaser.Button, mess around with the file NinePatchImage.es6 in src folder and extends Phaser.Button instead of Phaser.Image (you would need some extra modification for this to work of course). Best regards, Netcell

On Mon, Mar 14, 2016 at 9:43 PM -0700, "liang1020" notifications@github.com wrote:

Hi netcell,

I was impress with the helper tools that you do for phaser. But can i know is there some way that can change the texture of ninepatchimage to do like rollover effects. Or how can i fit ninepatchimage into Phaser.Button.

Thanks in advanced 1st :) Hope to hear from you.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/netcell/nine-patch-phaser-plugin/issues/5

[fkrauthan]

@netcell Any plans to add your performance optimizations to this repository?

[netcell]

Hi, sorry I haven't been able to find time for this. Lately I've been working mostly with games on DOM instead of canvas.

In detail about the performance problem:

• This plugin produces 9 images and attaches them to a single Phase.Image instance. This causes the updates needed for this instance increased by 9 times.
• The solution is to attach those images to a Phase.Group instance instead and optionally cache that instance to produce a bitmap image so that those 9 images wouldn't need to be updated constantly.
• However, this solution costs us a few methods that only usable on Phase.Image. In the project I did, after implementing the above solution, I had to do some dirty trick to fix that, but it's not applicable in all cases.