Which if haxe installation did not define, it's not defined at all

Well seems lime copies everything it needs to the export folder when you build. So first thing I'm gonna try is copying de hdlls directly into the export folder, although that's not very neat

Ideally lime should have this dependecies within it and copy them along hl and it's dependecies as needed

worth a try

Well as imagined, copying ssl.hdll direclty into the export bin folder worked

I just wish lime did that for me 😫

where did mousecaneta come from..... i know i had guifes tagged in that post.

well..... i would think theres a way to tell lime where to find them.

nvm, i see where the mousecaneta came from now lol

@User thought this was interesting..... i guess for each platform you have to build the needed ndll and then it knows where to found them...... The "lime/ndll" directory will be empty, but you can easily rebuild the binaries for any platform using "lime rebuild", like: lime rebuild windows lime rebuild windows,blackberry lime rebuild linux -64 lime rebuild android -debug Most platforms do not require additional dependencies (other than usual dependencies) to rebuild, but if you are running linux you will development libraries for GL and GLU, as well as multilib versions of g++ if you plan to rebuild both 32- and 64-bit versions of the Lime native layer (which is done through "rebuild" by default)

> where did mousecaneta come from..... i know i had guifes tagged in that post. @User It's my original nickname

I changed it for this server to match my github's

ah ok

saw that little bit of info here...... https://lib.haxe.org/p/lime/0.9.8/

the old lime but i'm assuming it may still hold accurate on the ndll's

Haxe UI is working great! 😄

At the moment the tool panel on the left hand side is just a vbox of buttons, but as in photoshop, inkscape, gimp, etc, only one tool should be selectable at a time. Should I try and use radioboxes, where it makes sense for one of a group of items to be selected? I noticed that radio boxes don't have an

icon

style.

maybe buttons with .toggle=true? Although it wont handle the unique selection of them for you, so you'd probably have to remember which is currently selected and flip it off when a new on is seleected

Ah yes that sounds much more convenient than radio boxes, thanks 🙂

i wonder if i should add a group property to button (that is only relevant when .toggle=true), so they behave like option boxes

there are probably quite a few times when you want a set of tool buttons and only one in a group to be depressed at any given time

I think that would only be useful for toolbars, but as you say, tool buttons are relatively common amongst some apps

I just tried out textarea, it works but not quite native haha. Control (word) movement, mouse and ctrl+a selection aren't implemented and copying crashes Kha. Tbh still pretty impressive, text is hard 😐

yeah, ive noticed there are some little bits missing from kha text input... any chance you can open issues for them on haxeui-kha? Makes sense to get them dusted away

Yep sure. Mouse selection seems tricky but the other stuff should be very possible

So do those text features work on other targets?

depends, openfl for example has its own text input, so it uses that, same for html5... kha didnt so i had to implement one

Ah yeah makes sense.

i noticed some issues with it also, so it needs a little love, but ive been avoiding it as, as you say, text input is a pain from scratch

ill implement .group in button a little later, it doesnt hurt to add it, it wouldnt affect anything and its just useful if you want to use it - ive wanted something like it before and rolled out my own "unselect the selected one" so thats at least two people who would have benefited from a .group property