https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • f
    Happy Birthday . I have a bug(or bad description) for you 🎁 🙂 In the dragoptions. Its is said
    Copy code
    /**
     * A Rect specifying the bounds in the screen's coordinate space.
     * Default: screen's bounds
     */
    @:optional var dragBounds:Rectangle;
    But in fact its the rectangle compared to the x, y of the dragged component, which is not very instinctive. ( Because it's not easy to calculate when a component position isn't calculated yet)
  • b
    Happy Birthday!!🎉🎉🎉
  • b
    sounds like more of a bad description... id like to revamp / extend the dragmanager soon(ish) as there is a bunch of other stuff id like to do with with...
  • b
    thanks! 🙂
  • f
    Ok cool. i'l wait before using the drag options then 🙂 Have a nice weekend ! 🙂
  • b
    well, use the current impl by all means, i mean, im not going to be changing anything there anytime soon
  • b
    i think its just a l¡ttle bit of a bad decription... the problem is that if you have an absolute at position 100x100, then you are going to be naturally bound by the size and position of that component (regardless of the bounds)
  • b
    or, actually, is that right? 🤔
  • b
    so yeah, the drag manager calls "moveComponent" on the currently dragged component
  • b
    which means if its in a parent component that is 100x100 size, then really, you are already constrained by the 100x100 (i mean, effectively)... really it should probably pop it out the container (or ghost it) and put in on the screen (rather than leave it in the component tree)
  • b
    ... ... ... anyways ... ... ... ill check it out... id like it to become much more useful in general (like dragging and dropping between components)
  • f
    Yeah dragging between components is awesome, I'm using it this way. When dragging it , I move it one the ancestor component ( the one I want be the z-index to be over) , I lock the layout during the dragging, then add the dragged component to the target component at the drag end and unlock all the layouts. Hacky, but not so complicated and works nearly perfectly , ( the second time I drag an object it appears for a frame at 0,0 but I put the opacity at 0 just for this frame) .
  • b
    oh, very interesting... ill be coming to you then for opinions... got a gif of it in action? Im curious
  • f
    Yeah, I can record it 🙂
  • b
    no rush, just curious to see what you came up with
  • f
    Oh I didn't record the mouse . There is a menu component which contain all the menu rods. And the grid contains plenty of boxes where I add the image
  • b
    interesting stuff, think this already goes out of the "general" usage of drag manager... like, i dont think there is any built in "drop" functionality
  • b
    would be interesting to see what we can come up with to make things like this "effortless"
  • b
    another one that came up in a GH issue is the ability to drag / drop nodes in a treeview, but, if that is going to be implemented (which would be nice), then i would prefer to drag / drop items between any components (eg: drag nodes off a treeview and drop them in a listview, drag them off a listview and drop them in a tableview, then drag / drop them back to the treeview)
  • b
    (but all in such a way that its not really specific to tree, list or table)
  • b
    (is the first video a "counting" program / teacher?)
  • f
    Yeah, it is an educational project ( which teaches reading, counting, multipling, all the basics, in multiple languages) , which I abandonned for a few years, I first made it in Stencyl. But i worked so much on it, I just couldn't open Stencyl anymore and finish it well. But I have I found my motivation back by using haxeui, which have nearly everything I need. Plus the project is so big, that I'm confident that haxeui will have the feature I want when I need it haha.
  • f
    >
    Copy code
    var originBox = objects[line][column];
>         component.registerEvent(MouseEvent.MOUSE_DOWN, function(e) {
>             if (component.draggable) {
>                 if (component.parentComponent != null)
>                     Utils.changeParentContainer(component, this);
>                     this.lockLayout();
>             }
>         }, 9999);
    Here is part of the code for the behaviour in the grid. The instereseting part , is the MOUSE_DOWN, which I highly prioritises the change the parent component. The changeParentContainer just change the parent container, and sets the x an y at the correct position .
  • g
    I'm veeery late but happy birthday dude have a great day!
  • i
    happy yesterbirthday!
  • b
    thanks guys 🙂
  • r
    The ``haxeui-kha`` readme recommends installing hscript, I assume I don't need that anymore?
  • a
    correct haxeui got rid of the hscript dependency
  • r
    Yeah, I know that. I just didn't know if the Kha core required it
  • a
    afaik hscript was a dependency of haxeui-core, not of the backends
1...125412551256...1687Latest