Haxe

i feel 100ms is "fine" for timers... but you'd have to test on different platforms to confirm that...

but the short answer is: yeah - i think your initial concept is the right way to go about it, if you need later some type of high fidelity timer or something (which is outside the scope of haxeui) then im sure you can find one

changed tabview style, probably nobody will notice, but i like it alot more 🙂

how was it before? you were right in that I can't notice the difference

first iteration but seems to be working quite nicely

For sliders, is `min` and `max` inclusive or exclusive? I am having some difficulty with `slider.pos = slider.max`

when I isolate the example, the issue seems to go away

but I really have no idea what could be causing it...I've been exploring this for a number of days and I can't figure it out

wow by sheer luck I just fixed one of the issues...ok I think this is on my end and probably not an issue with haxeUI. thanks!

nice one, what was the issue out of interest?

I was incorrectly setting the starting position and it was causing some weirdness. There may still be an issue if you set pos multiple times in a row with the user actually dragging but I'm not positive

another thing I noticed: if I do
```haxe
slider.pos = 20;
trace('slider ${slider.pos}');
```

The output is 0 even though the pos is visually set to 20

```haxe
slider = new HorizontalSlider();
slider.min = min;
slider.max = max;
slider.pos = startingPos;
slider.percentWidth = 90;
slider.horizontalAlign = "center";
slider.disabled = disabled;
// slider.horizontalAlign = "center";
trace('created slider with ${slider.pos} from ${startingPos}');
this.addComponent(slider);
```

and then the output I see is `created slider with 0 from 99`

when i add an event in the xml for my app, does that get compiled at compile time be macros, or is it interpreted at runtime?

it seems like the latter, in which case haxeui is dead to me

if i dump one of the examples, it has this code ```haxe
var c3 = new haxe.ui.components.CheckBox();
c3.set_id("checkbox_a1");
c3.set_text("Default A1");
c3.addScriptEvent("onchange", "checkboxValue.text = this.id + (this.selected == true ? ' selected' : ' unselected')");
```so thats not compile time

hmmm.. or is it maybe possible to do this another way, so that runtime code interpreting can be avoided? such as writing a function name into the xml which is then "connected" to a normal function by a macro?