https://linen.dev logo
Powered by
# haxe-ui
  • b
    I can't imagine it would, but not 100% positive without a bit more thought.
  • b
    i think the "dragEventType - specifies wether to use mouseMove or frame loop during drag for position updates." might, which is why i would drop it for the first iteration
  • b
    I've written similar MoveManager things for AS3 and PixiJS. In both cases, it's pretty straightforward... besides a bit of coordinate space juggling.
  • b
    Good point, Ian. I may be the only odd duck that would want that frame loop functionality anyway. 😉
  • b
    it might be a candidate for second pass, but i think for the first pass, K.I.S.S
  • b
    Word. Then let's see if others have feedback on this most-bases-covered approach. I'm game to jump in and help some time this week.
  • b
    sounds great!
  • b
    I assume PRs would be the preferred path for me?
  • b
    as opposed to?
  • b
    Didn't know if the scope might call for direct commits to a new branch... just thinking about your current bandwidth for review on something that may be a bit iterative.
  • b
    Doesn't matter to me
  • b
    yeah, valid point... are you a collab on haxeui-core?
  • b
    Not yet
  • b
    At least not to my recollection
  • b
    yeah, you werent, invited you
  • b
    Thx. Naturally, I'd only work in a new branch special for this.
  • b
    yeah, cool - i was wondering actually if you could have more granular control over that stuff... i mean, im not worried by the 7 people who are collabs, but i wonder what type of restrictions i can impose
  • b
    ie "can create branches but not commit to master" type thing
  • b
    I feel fairly confident that can be managed, but never looked into it.
  • b
    same
  • b
  • b
    jinx 😉
  • b
    🤣
  • b
    looks like i already did it, or GH already did it
  • b
    can you try and push something to master, just to see?
  • b
    Sure, after a smoke
  • b
    👍
  • b
    And was happy to see I could drop the commit without issue after it failed.
  • b
  • b
    ok, nice... so thats all working as expected then, i think GH did all that automatically to stop any potential bad actors from nuking repo contents
1...470471472...1687Latest