https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • a
    This would be my expected result (red square is clipped out)
  • a
    hmm... "native" ceramic clipping may be incompatible with haxeui 🤔 that will be awkward if so 😄
  • b
    i dont think anything is special about these
  • b
    You have 2 options for nested clipping
  • b
    First is to clip with mesh objects that can be multiple shapes (in a single mesh) so that you can clip a child with a mesh that is shape of the child + shape of the parent. But that’s a bit complicated and not so good performance wise
  • b
    Second option is to use Filter objects instead of clipping
  • b
    Basically, with a filter, you draw a hierarchy of objects onto a render texture and display the result. That means everything outside bounds is clipped
  • b
    And Filter objects can be nested
  • b
    Although this require some memory as you allocate textures, it’s a better option that regular clipping because first you can nest them, but they are also compatible with renderer’s batching
  • b
    So you’ll have less draw calls if you use filters
  • b
    (That’s what I use over clipping for the elements plugin)
  • a
    ah okay, so if i understand this correctly green and blue squares are filter objects and red square can just be a normal visual? Could you link me to an example of this, this is new territory 😄
  • a
    ah i found visualcontainerview
  • a
    which i think is what i'm looking for
  • a
    hmm, so essentially every visual will need a fliter
  • m
    Why this error happening.
  • r
    you should probably be using the git version of both those libraries, but not sure if haxeui-android is in working condition anyways
  • m
    Yes I am using Git version Is it not in working condition.
  • b
    Mmmmh you'd rather not do that. You should create a filter only if you need clipping
  • b
    (and destroy it if you don't need it anymore)
  • a
    i guess i'll have to see, right now i'm trying to make a little test case outside of haxeui to figure out the usage
  • a
    but i think all components will have a "clip effect" of some kind but maybe i'm wrong
  • a
    components do have a 
    clip
    property, but the absence of that property doesn't imply clipping not to be needed
  • a
    maybe in haxeui having the parent visual be clipped is "enough" 🤔
  • b
    What I mean is that clipping (with or without filter) has a cost that is non negligible so when using filters you should only create a filter if you need it to do an actual clipping
  • a
    okay, maybe i'll just use it if 
    clip
    is set to true then, but not sure on the effect that will have on the haxeui component ecosystem
  • a
    from what i've seen across all of the other backends, clipping to some degree is just on by default
  • a
    so that may not be a thing that is possible
  • b
    What's the rule here @bright-gpu-74537 ?
  • b
    the version of haxeui android is crazy out of date, i have a new version on my other machine, but havent gotten around to kicking the dust off of it and putting in on GH... been meaning to every weekend though... ... hopefully this weekend (tm)
1...156415651566...1687Latest