Plugin background not showing up...

[d.healey]

@Felix10870 I have the same problem with one of my projects. It's been so long since I used images that I can't remember the solution :p

[Felix10870]

@d-healey I'm changing the bit rate of the .png and next trying a .jpg
I'll let you know if this works...

[d.healey]

@Felix10870 Are you drawing the image on a panel or using an image component?

[Felix10870]

@d-healey image component...

[Felix10870]

@Felix10870 going to restart my maching and see if that helps... changing the png bit rate and to a jpg didn't work... this is the last hurdle for this pluging...

[d.healey]

@Felix10870 My issue seems to have resolved itself so I'm not sure what the cause was. I think in your case you need to add the images to the pool. Engine.loadImageIntoPool()

[Felix10870]

@d-healey I'll give it a try...

[Felix10870]

@Felix10870 so I thought this was interesting... so a dropdown happens when you click the 'up/down' arrows to show you the images that I would guess are in the pool... the current background image was not... so the first Item on that list was 'load new file' which I did and now the background image is in the pool... so 'open' to the right of the 'up/down' didn't do that... is this for preview? might be a newbie user error...

[A Former User]

Try adding a Panel and assigning the image to it, I had an issue semi-recently that was fixed by just making invisible panels with the images on them to "force" it to save/load the png

[Felix10870]

@iamlamprey my issue started when I removed all the labels and embeded them in the background image... I think your right... Hise needs things to think about... :)

[Soundavid]

@Felix10870 Make sure that you check the "Embed Image Files" in your project settings, I had a similar issue using the image component as a Parent of other components, so i use transparent Panels above the BG images.

[Felix10870]

@Soundavid Embed image files was check... I wish that ws the issue... and thanks

[Felix10870]

got it working... just rebuilt it in a fresh project... new naming conventions etc. must of had a conflict somewhere...