https://linen.dev logo
Powered by
# haxe-ui
  • f
    Oh, it actually works now ... (I had noted this bug a few days ago, and actually warned people who tested it about it ) As I feel I'm going crazy , lol , I'm going to check changelos of firefox as it has been updated .
  • b
    weird... well, happy it works i guess
  • b
    ¯\_(ツ)_/¯
  • f
    Still, thank you 🙂 I can remove it from my list of potential haxeui bugs . I keep a little list but most have easy workarounds. And I don't want to overwhelm you, specially coming back from holidays 🙂 so the others will wait .Sorry to have bothered you !:)
  • b
    doesnt hurt to list them 😉 Even if i dont get round to them instantly, its always good to know about them, they can digest / percolate that way
  • f
    Okay here's a core ( I think but at least html5) one https://github.com/haxeui/haxeui-core/issues/459 🙂 . Most bugs I have are with wxwidgets.
  • b
    fixed 😉
  • f
    Fast ! 🙂
  • b
    yeah, funnily enough, ive been fixing some other cloneComponent issues, thought it might be related - it wasnt
  • h
    Thanx for this. What I didn't initially realize was that XML elements - component names are mapped to classes of the same name. But regardless #id > label does in fact work if I assign an id, so I'm guessing label is a direct descendant of frame. And that's the only label I want to select the frame text attr - the name displayed in the frame. Other labels further down the hierarchy I wanted to size differently.
  • h
    I was also trying to use custom class names
  • h
    that appears not to be doable by specifying class though you can specify className
  • h
    but I could not get CSS to select by className value
  • h
    ah ... this is perhaps what I was missing - is this doc'd anywhere ?
  • f
    @bright-gpu-74537 Interesting timing 🙂
  • f
    I don't see it really in docs. But good ressource to read are the haxe-ui guides ( plenty of them are empty though) https://github.com/haxeui/haxeui-guides This tutorial is old and some functions have change names ( the haxe ui part) https://keyreal-code.github.io/haxecoder-tutorials/ but still interesting to understand how it works
  • f
    Then looking at the posts of the new released versions https://community.haxeui.org/search?q=HaxeUI could also be helpful
  • b
    I actually saw haxecoder tutorials, and i wondered if i should restructure them and make them more "modern" and include those in the haxe learning center
  • b
    of course with copyright, I'm not a code thief
  • h
    I had a look over the guides - most are empty and I didn't see anything pertinent to the markup lang. Tutorials are not exhaustive and if they are videos not usually searchable in a useful way. I know people like them and they are helpful if they cover what you want but they get out of date. You really want accurate doc - a thing that in the Haxe ecosystem is a rarity alas. I haven't yet located the source code for the style lang - I found some of it but not the bit that the defines the supported markup.
  • b
    wdym style lang?
  • h
    Is HaxeUI CSS CSS ? What properties exist ? what are the names and what is the value space of each ?
  • b
    yep, just CSS
  • h
    The basic assumption is that the XML element names are roughly like HTML element names - ok. And that the CSS selectors and properties work as per normal CSS but in fact that's not the case - you have to use styleName not class
  • f
  • p
    class
    is a keyword in haxe, so you can't use it as a property name.
  • h
    and what version of CSS is it compatible with ?
  • h
    ok - but that doesn't have to impinge on the XML markup - couldn't that be fixed up in the macro code ?
  • f
    it's a haxeui css there are multiple things that are compatible and some note, in the style.hx file where all the cases are, you can see what will work
  • h
    read a chunk of that last night - styleName isn't mentioned for example
1...113111321133...1687Latest