Haxe

well, it'll be very "hxwidgets specific" but you can do it i think... maybe "AssetsImpl" needs an imageFromRGBABytes... 🤔

gotcha... so... Image (haxui component) will have a `.window` property in the case of Image that will be a StaticBitmap (hxWidgets)

on StaticBitmap there is a .bitmap property which accepts a hx.widgets.Bitmap

you can construct one of those from a hx.widgets.Image

and that class has helper functions to work with raw data

```haxe
var staticBitmap = cast(haxeiuImage.window, hx.widgets.StaticBitmap);
var image = new hx.widgets.Image(100, 100);
image.imageData.copyRGBA(someBytes);
var bmp = new hx.widgets.Bitmap(image);
staticBitmap.bitmap = bmp;
```

something like that (untested, written blind)

note: you'll probably also need to resize the haxeui image appropriately (100x100 in that example)

```/usr/src/debug/wxwidgets/wxWidgets-3.2.2.1/src/gtk/bitmap.cpp(595): assert ""image.IsOk()"" failed in InitFromImage(): invalid image```

```haxe
final img = new hx.widgets.Image(rgba, dims.width, dims.height);
final bmp = new hx.widgets.Bitmap(img);

final comp = new haxe.ui.components.Image();
comp.resource = bmp;

tplimages.addComponent(comp);```

the bytes constructor param isnt an rgba array

im not sure what you mean, they work the same as anything, the difference with the explorer is there is a whole kinda "application framework" around the views

https://github.com/haxeui/component-explorer/blob/master/src/views/MainView.hx#L30-L93

noice... forgot that this would work: `comp.resource = bmp;`... well remembered 🙂

It seems module Fonts don't work with Heaps. The prefix set in the module.xml isn't resolved when loading the font, so the program tries to load a file with a non-existing path (since it uses the prefix).

yeah, i dont think fonts can be loaded from bytes in heaps... though ill have to check that, so you'll just have to use font resources like heaps expects, which probably makes more sense anyway

yeah, no "fontFromBytes" in haxeui-heaps AssetsImpl, just "getFontInternal"