ill probably use the bitmap value of a haxeui image for this

(or just use haxeui's imageFromBytes, the

.data

will be a

ImageData

which in haxeui-openfl is

typedef ImageData = openfl.display.BitmapData;

)

using it rn

the benefit of using imageFromBytes is that its supported across frameworks, so if you decided to move, you shouldnt need to change anything (in that part at least)

eg:

same app, hxwidgets

nice it works!

ok, @icy-zebra-52882 - datasource filtering should work now, you'll need git haxeui-hxwidgets and hxWidgets

filtering now works as intended, thank you!

another bug: on latest git for relevant haxelibs, adding a

<switch>

came up with this constant error when running the output:

ASSERT INFO:
../src/gtk/bitmap.cpp(963): assert ""IsOk()"" failed in GetWidth(): invalid bitmap

BACKTRACE:
[1] wxBitmap::GetWidth() const
[2] wxBitmapBase::GetLogicalWidth() const
[3] gtk_container_propagate_draw
[4] gtk_container_propagate_draw
[5] g_closure_invoke
[6] g_signal_emit_valist
[7] g_signal_emit
[8] gtk_container_propagate_draw
[9] g_closure_invoke
[10] g_signal_emit_valist
[11] g_signal_emit
[12] gtk_container_propagate_draw
[13] g_closure_invoke
[14] g_signal_emit_valist
[15] g_signal_emit
[16] gtk_container_propagate_draw
[17] gtk_container_propagate_draw
[18] gtk_main_do_event
[19] g_signal_emit_valist
[20] g_signal_emit
[21] g_main_context_dispatch
[22] g_main_loop_run
[23] gtk_main
[24] wxGUIEventLoop::DoRun()
[25] wxEventLoopBase::Run()
[26] wxAppConsoleBase::MainLoop()
[27] __libc_start_main
[28] _start

changing the switch to a checkbox stopped the crash, seems to be to do with detecting width of component in a grid

adding a switch where?

fyi, there is no switch per se in hxwidgets, it maps to a toggle buttons, it also wont work in an custom table renderer

that said, i wouldnt have expected it to crash

oh, that crash is a different thing looks like when you use an image it cant find... again, wouldnt have expected a crash

OK, both those issue should be fixed: non existent images shouldnt crash the app (whoops! not handling nulls!) and if you use a switch in a custom renderer it will default to checkbox (there is no "switch" in wxwidgets that i know of) latest haxeui-hxwidgets and hxwidgets

fyi, i made bunch of updates to hxWidgets and haxeui-hxwidgets to fll in the blanks to some of the tableview api that i noticed while playing around

haxeUI recompiling has driven me to re-rearrange my room back to having my gaming PC at a desk, just so I can use it for compilation instead of just controller games, to avoid laptop compile times

I hope you're happy 😛

haha

HXCPP compiler cache is a a life (power!) saver!

wont save you everytime, but will defo shave alot of time off

... someone was having a hxwidgets issue on the forum so i spun a blank VM, compiled wxwidgets (and haxe test app) from source and maaaaaan, took about 40 minutes, literally just compiling wx...

(i forgot to add more cores to the vm, but still... thats not "have a coffee and come back", thats "have a nap and come back")

yep I had to compile it 3 times on my laptop, when I was having trouble initially compiling the haxeUI-hxWidgets template, just to check if it were GTK or the

--with-opengl

that was at fault

would likely have given up if every compile were without HXCPP cache

Piece of advice: Use Linux :) MSVC is slower than GCC/Clang in my experience. Alternatively get a Ryzen Threadripper.

40 minutes is a bit long though, building wx in release mode took 6 minutes on this i3-4130.

yeah, was defo ages... i think because the VM was setup with a single core