yeah, tbh as soon as you said "textfield" i thought... "shit, thats an interactive, isnt it"

haha

Getting there!

OK, i think thats working now

Nice, one moment

git haxeui-heaps btw

Works!

🥳 - nice catch

i hate text... and text input especially, which is a shitter as ive promised myself im going to add text input to pdcurses this weekend :/

Oh golly

Hope that goes smoothly for you!

yeah, we'll see, ive written text inputs for kha and raylib, so i guess its not going to be anything like that

in the sense i would assume its simpler - but thats famous last words

Woo, another problem found!

This time with a crash log!

haxe
table = new TableView();
table.addColumn("Color"); //<-- Crashes here

Can't cast haxe.ui.components.Label to haxe.ui.core.ItemRenderer

Called from haxe.ui.containers._TableView.Builder.fillExistingRenderer (haxe/ui/containers/TableView.hx line 437)
Called from haxe.ui.containers._TableView.Builder.onInitialize (haxe/ui/containers/TableView.hx line 322)
Called from haxe.ui.core.Component.initializeComponent (haxe/ui/core/Component.hx line 1503)
Called from haxe.ui.core.ComponentValidation.validateComponent (haxe/ui/core/ComponentValidation.hx line 172)
Called from haxe.ui.validation.ValidationManager.process (haxe/ui/validation/ValidationManager.hx line 140)
Called from haxe.ui.util.$Timer.~delay.1 (haxe/ui/util/Timer.hx line 10)
Called from haxe.ui.backend.$TimerImpl.update (haxe/ui/backend/TimerImpl.hx line 13)
Called from haxe.ui.backend.$BackendImpl.update (haxe/ui/backend/BackendImpl.hx line 7)
Called from haxe.$MainLoop.tick (C:\HaxeToolkit\haxe\std/haxe/MainLoop.hx line 204)
Called from haxe.$MainLoop.~injectIntoEventLoop.0 (C:\HaxeToolkit\haxe\std/haxe/MainLoop.hx line 118)
Called from sys.thread.EventLoop.progress (C:\HaxeToolkit\haxe\std/sys/thread/EventLoop.hx line 114)
Called from hxd.$System.runMainLoop (hxd/System.hl.hx line 152)
Called from hxd.$System.runMainLoop (hxd/System.hl.hx line 142)
Called from haxe.$Timer.~delay.0 (C:\HaxeToolkit\haxe\std/haxe/Timer.hx line 144)
Called from haxe.$Timer.~__constructor__.0 (C:\HaxeToolkit\haxe\std/haxe/Timer.hx line 76)
Called from sys.thread.EventLoop.loop (C:\HaxeToolkit\haxe\std/sys/thread/EventLoop.hx line 150)
Called from sys.thread._Thread.$Thread_Impl_.processEvents (C:\HaxeToolkit\haxe\std/hl/_std/sys/thread/Thread.hx line 62)

you dont use / want to use xml, right?

(i mean to test)

Correct

ok, then what if you create a

Header

add the `Column`s to that and then add that to the table?

One moment

although, that stack is more strange... i feel like maybe @User opened an issue about this

yup: https://github.com/haxeui/haxeui-heaps/issues/30

Header appears to be a ``component`` type, would I just do ``= new Component()``?

in this case i dont think its going to make a difference, looks like an old(ish) bug

im just not sure if the proposed fix is the right one, plus i feel like tableview is going to get some huge updates soon as ive hit some issues with it for the OpTex stuff ive been working on

Understandable, avoid for the time being?

hmmm, not sure really, avoid seems like a bad idea.... its a useful component and its going to be a while till it gets its revamp

this only happens on HL as fair as i remember too

Well I can't exactly use it if I can't add columns, lol

no no, im not suggesting that... just thinking