https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    well, it defo insta crashes with that exception
  • l
    I mean 5ms is a very small number between clicks, if you set it to 50ms then it will run for a lot longer, but sooner or later it will crash as well
  • b
    either way, id like to understand it, even with 1ms
  • b
    drag clicking tho
  • b
    the code looks sensible... so i dont understand why it thinks something has been destroyed (and is trying to invalidate it)
  • b
    it lets you click an insane amount of time in less then a second, and most of the clicks are clumped together
  • b
    im pretty sure i myself can get to clicks 15-20ms apart (not consitantly tho)
  • b
    heh, i doubt that... 66 clicks a second?? 😄
  • b
    either way, its irrelevant, something is going wrong
  • b
    i dont think the 
    if (this._isDisposed) return
    is a valid solution (though it may make sense eventually), as the real question is "what is causing this"
  • b
    ok, i can see whats happening... the dialog tries to center itself 1 frame later... and in that time, its already been destroyed
  • b
    so its a dialog bug really
  • b
    fyi, this is a minimal repro:
    Copy code
    haxe
            var dialog = new LoginDialog();
            dialog.show();
            dialog.hide();
  • b
    OK - fixed (git haxeui-core), so this is actually a good example of why the exception is important... 
    if (disposed) return
    was there it would have hidden this bug
  • b
    My best is like 42
  • b
    (Consistant)
  • b
    Wait a sec
  • b
    42 CPS?
  • b
    With drag clicking
  • b
    oh, right, yeah - didnt realise thats what you meant... thought you meant manual clicking
  • b
    Bruh I recorded myself and it's bigger then 8 megs -_-
  • l
    seems to be fixed for me, now I can continue my quest to find the "other" one 🙂
  • b
    @loud-salesclerk-7438 - so i was kinda intrigued by your haxeuim project, and more importantly the way you dispatch events via lime to haxeui, so i thought i would have a little play around and see whats possible:
  • b
    thought it was quite fun / cool 🙂 - food for thought maybe
  • l
    nice! I haven't tested more complex mouse actions, but the building blocks are already available in the library. I think things like drag & drop could work in current version, they might not be the most convenient to use, but that will improve over time. of course every mouse event will have to be sent through the socket connection one by one. which might not be quick enough for whatever needs testing.
  • l
    sending more than one mouse event in one go should be doable (kinda like Selenium's Actions API) in a future version.
  • l
    I started work on this like two weeks ago, so everything is still a bit WIP.
  • b
    i would think local websocket should be fast enough
  • l
    so far speed has been sufficient, but I'm not testing against a real world application so who knows what testcases users will want to run.
  • b
    yeah, i would have thought sockets locally would have been near instant, obviously you have message processing etc to take care of, but i would guess its negligible overhead
1...120812091210...1687Latest