https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • r
    correct
  • b
    showing 3d stuff?
  • r
    it was an example; it's not actually a modelling app 😅
  • b
    haha, gotcha 🙂
  • r
    but if I'm editing a property and select text and hit 'delete', it also deletes whatever is selected in the canvas's state, is the issue
  • b
    yeah, sounds like a pretty compelling argument to make it interactive
  • r
    so I need to know whether the user has last clicked on the canvas or has focused elsewhere...and that includes if they for example pressed ctrl+o to bring up an "open file" dialog etc, so i can't just rely on naive click position checks etc
  • b
    lemme have a think about, just woke up, need to get some food etc... but im thinking it probably doesnt hurt to make canvas extend InteractiveComponent, and maybe even make "allowFocus" false to start with
  • r
    I appreciate it, and absolutely no rush of course :)
  • b
    np
  • b
    @bright-gpu-74537 were you looking for sprites for animation or animation handling code?
  • b
    either / both... just wanted to see an example of something i could use as a "custom image handler" thingy
  • b
  • b
    So ultimately I think it would take an array of strings, maybe let the backend convert strings to Tile/FlxFrame/etc
  • b
    With the atlas/spritesheet(s) defined in Toolkit init
  • b
    And then any anim parameters like fps, etc
  • b
    interesting... whats "Spritesheet"?
  • b
    nvm
  • b
    got it
  • b
    so i think, as for some custom handler, you would handle that in your image handler however you want, something like: 
    <image resource="animation://frame1;frame2;frame3?spritesheet=myspritesheet&loopPoint=8">
    or 
    <image resource="animation://some_pre_packaged_animation_id>
  • b
    ie, haxeui would lookup "animation" and run your handler and just pass to that 
    frame1;frame2;frame3?spritesheet=myspritesheet&loopPoint=8
    or 
    some_pre_packaged_animation_id
  • b
    That makes sense
  • b
    its a neat idea, for sure... super flexible
  • b
    Does it make sense to keep it kinda generic and let the backend handle 
    animation:
    as well?
  • b
    i have a sparrow player for haxeui-flixel i wrote ages ago, would be interesting to see how i could integrate that also
  • b
    well, i would need to extract that part to know which handler to call... "http", "file", "resource" (default), "sparrow", "animation", etc
  • b
    so the backend (or your app) would register different handlers in a module.xml...
  • b
    core would expose "the normal ones", haxeui-flixel would expose the sparrow one, your app could expose the "animation" one, etc
  • b
    an eg of what i would expect haxeui-core to have in its module.xml after:
  • b
    Copy code
    xml
<image-loaders>
    <image-loader prefix="resource" class="haxe.ui.core.loaders.image.ResourceLoader" default="true" />
    <image-loader prefix="http" class="haxe.ui.core.loaders.image.HttpLoader" />
    <image-loader prefix="file" class="haxe.ui.core.loaders.image.FileLoader" />
</image-loaders>
1...153715381539...1687Latest