https://linen.dev logo
Powered by
# haxe-ui
  • b
    i guess its kinda an edge case (ie, hide the mouse unless its over the UI) but it seems like the must be a nice way to handle it correctly... or at least emit something that helps
  • b
    right
  • f
    This is the real goal haha, the rest are hacks
  • f
    Ah oops, not mouse up, mouse over
  • f
    Interesting, krita handles this the way that Realmkit now works. When a menu is open, the cursor is shown, regardless of whether the cursor is over the menu.
  • f
    Gimp does the same, huh. Well, I'm happy then. And existing code should be fast, just being a single length check branch.
  • b
    i guess it does make sense
  • b
    ie, you move you mouse to the middle (its invisible) then you open a menu with a keyboard shortcut... well, i would want to see the mouse
  • f
    Fair point 🙂
  • b
    i thought the video was realmkit for a minute... i was like "wow, it changed alot"
  • b
    😄
  • f
    Ahha nope lol
  • b
    @User - not sure how to fix this 😦
  • b
    that grey line on the selected tab is actually coming from behind (ie, its the border of the tabbar / tabview content)
  • b
    bit of a shitter as i cant think of a way to hide it (if you have transparent backgrounds)
  • b
    ... i am starting to wonder if i actually need the tabbar bottom line to go all the way across the tabbar, i mean, really, it just needs to go to the right of the buttons... ... ive got some errands to run but ill have a play later... 🤔
  • b
    thats better 🙂
  • b
    Copy code
    css
.tabbar {
    background-image: none;
    border: none;
}
        
.tabbar-button {
    border: 2px solid black;
    background-color: white;
    border-left-width: 0px;
    border-left-size: 0px;
    background-image: none;
    font-size: 18px;
    background-opacity: .4;
    border-opacity: .7;
}

.tabbar-button.first {
    border-left-width: 2px;
}

.tabbar-button:hover {
}

.tabbar-button:down {
    border: 2px solid black;
}

.tabbar-button-selected {
    border-bottom-width: 2px;
    border-bottom-color: white;
    background-color: white;
    border-left-width: 0px;
    background-opacity: .7;
    border-opacity: .7;
}

.tabbar-button-selected.first {
    border-left-width: 2px;
}

.tabview > .tabview-tabs {
    margin-top: 0px;
}

.tabview > .tabview-content {
    background-image: none;
    border: 2px solid black;
    background-color: white;
    background-opacity: .7;
    border-opacity: .7;
    border-top-width: 0px;
}

.tabbar-filler {
    border-bottom-width: 2px;
    border-bottom-color: black;
}
  • b
    ^^ @User
  • m
    Sweet!
  • m
    I see what you did there, with the border opacity hahaa nice touch
  • b
    🙂
  • b
    you'll need to pull latest core + backend... some changes in both (there werent issues in compound borders, but i think they are slightly better now)
  • m
    Nice! Thanks a lot!
  • b
    np
  • m
    I've updated both core and flixel backend and I'm getting:
    Copy code
    C:/HaxeToolkit/haxe/lib/haxeui-core/git/haxe/ui/components/TabBar.hx:41: characters 29-53 : Constraint check failure for findComponent.T 
C:/HaxeToolkit/haxe/lib/haxeui-core/git/haxe/ui/components/TabBar.hx:41: characters 29-53 : { width : Int } should be haxe.ui.core.Component
C:/HaxeToolkit/haxe/lib/haxeui-core/git/haxe/ui/components/TabBar.hx:39: characters 22-46 : Constraint check failure for findComponent.T
C:/HaxeToolkit/haxe/lib/haxeui-core/git/haxe/ui/components/TabBar.hx:39: characters 22-46 : { width : Float, left : Int, height : Float } should be haxe.ui.core.Component
  • m
    I've copied your css directly to test it out.
  • b
    oh...
  • b
    howcome i didnt get that?!?!
  • b
    easy fix
1...522523524...1687Latest