https://linen.dev logo
Powered by
# haxe-ui
  • b
    fair enough, ill see if your advice pans out... im not hopeful, but who knows... 🙂
  • o
    other thing to try is rotate back and forward. These might help test if it's a dirty flag issue.
  • o
    I got the impression fixel was like virtual display list so kind of like doing it with structures and just drawing to a texture, they may well be trying to minimize update propogation in the render cycle, and you just need to get the code to re-evaluate every change.
  • b
    that may very well be the case
  • o
    but maybe the transform matrix of offsets and scales and clipping are conflicting but nesting them it will apply them like matrix multiplication
  • u
    The reason why scintilla is wxwidget only is because they integrate directly in wxwidgets right ? cuz in theory scintilla is just a c lib so could be included in any language that can use C
  • b
    yeah, basically, the wxWidgets "version" is just a thin wrapper around the C api
  • b
    and so for ease hxWidgets just uses that
  • b
    but certainly no reason you couldnt create externs for scintilla directly and use it from any C app (hxcpp or otherwise)
  • b
    So i was today years old when i found out that wxWidgets comes with show effects
  • b
    not that useful to me, but coolish anyway, wonder how it works under the hood... wonder if the OS does it or wx... i would assume the OS
  • b
    if ( !::AnimateWindow(GetHwnd(), timeout, dwFlags) )
    , yeah, at the os level
  • b
    wip / poc new sidebar component:
  • b

    http://haxeui.org/shared/sidebar1.gifâ–¾

  • m
    Looks awesome!
  • b
    what backend? .top / .left is the official way, but .x and .y should have also worked
  • b
    ok, i can see from #165234904815239168 that you are using haxeui-flixel... so .x and .y should have worked there i think... any chance you could .zip up a test project when you get a moment?
  • m
    Can I jump in on this positioning convo, too? I'm trying to have a cursor icon move around the screen (like most NES era games) while also supporting mouse controls. It looks like 
    FocusManager
    is the sort of thing that might help me here, but trying to get the position of buttons in screen-space doesn't seem to work. 
    .top
    and 
    .left
    give me what looks like the relative position within their parent container and not absolute position. 
    getPosition()
    and 
    getScreenPosition()
    both just return 
    (0, 0)
    .
  • m
    I'm trying to think here on how to solve this. Somehow I haven't had that need yet, but I'm looking for some sort of global position in FlxObject and it doesn't seem to have one.
  • m
    You might need to resolve that recursively up the hierarchy.
  • b
    Flixel positioning is pseudo global
  • b
    Or is it pseudo local? 🤔
  • b
    It may be easier to use the haxeui 
    components
    array since you can't go up the chain via flixel alone
  • b
    It's been a minute, but I believe haxeui-flixel uses openfl mouse events directly
  • b
    So you'd have to dispatch events yourself... yeah not sure what that looks like
  • m
    It seems to be local. With this rough code, I'm seeing the correct positions:
    Copy code
    var focus:Component = FocusManager.instance.focusNext();
var absPos = FlxPoint.get();
var traceUp = focus;
while (traceUp != null) {
    absPos.x += traceUp.left;
    absPos.y += traceUp.top;
    traceUp = traceUp.parentComponent;
}
trace('recursive pos: ${absPos}');
    It does seem that @User 's observation that x and y are behaving a little strangely is reflected here (I had to use 
    top
    and 
    left
    as those were the only ones with correct values).
  • m
    I'll try it and see if I see the same
  • b
    HaxeUI's 
    left
    and 
    top
    are local. Flixel's 
    x
    and 
    y
    are weird
  • m
    @bright-gpu-74537 do you have a 9slice usage example? Couldn't find one.
  • b
    @User - component.screenLeft / .screenTop?
1...595596597...1687Latest