https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    thats completely inaccurate... clipping is expensive pretty much everywhere, only handle clipping if "handleClipRect" gets called 🙂
  • a
    ahah, okay then 😄
  • a
    so, as long as i constrain clipping to be instantiated to within the handlecliprect, we're good?
  • b
    clipping is "so expensive" that its, for the most part, an "opt in thing" (i mean, scrollviews, etc, obviously have it) but things that you probably thing should clip, wont unless you explicitly tell them to, otherwise things get silly real fast
  • b
  • b
    technically all components should clip by default, but that gets too much for most frameworks to handle in my exp... as @billowy-waiter-28954 says, its certainly non negligible
  • b
    i guess i could also have like an "auto clip" type of thing, where if the child goes out of the parent bounds clipping is turned on / off... but anyway, certainly doesnt exist at the moment, and in general, you should only end up with clip rects on the obvious things (scrollview, listview, etc)
  • a
    @bright-gpu-74537 is there an internal flag that I can track that tells me if something needs to be clipped? because I have to add a visual to a different visual if clipping is required
  • b
    no, but you could always create one in componentimpl
  • a
    there is style.clip but I'm not sure if that's enough
  • a
    something like 'if handleclip is called we clipping?
  • b
    no thats not enough... thats for style, which basically means "clip this component" - and when that happens, handleClipRect will be called with the bounds of the component
  • b
    in handleClipRect you could always do: 
    _isClipped = (clipRect != null)
  • b
    ...to keep the analogy with html5, html elements don't clip by default
  • a
    @bright-gpu-74537 okay I've got a positioning question
  • a
    the xml here is the example
  • a
    I've got a poc filter clip working
  • a
    however
  • a
    if i readd the other example
  • a
    it goes away
  • a
    this is because the filter isn't relative to the contents anymore
  • a
    the values coming in is still 
    0, 0
    so the black square remains under the components above
  • a
    How can i follow correct spacing here?
  • a
    yooooooo i think i may have it 😄
  • a
    okay i kind of have it
  • a
    hmm
  • a
    weird, for virtual box it works fine
  • a
    for normal box it doesn't
  • a
    hehehehe
  • a
    splitter now properly works 😄
1...156515661567...1687Latest