https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    right, yeah, pretty much what i think... the components explorer esp. not sure what to do there... maybe a totally different layout... not sure
  • h
    Ah, I missed this the first time actually . . . but now that I look at it again after a modest break I noticed the 
    class Button
    in the top right of the docs. That wasn't easy to see initially . . . maybe make it larger or centered? Not sure
  • b
    yeah, maybe larger... or the full class name (inc package)
  • h
    I'm gonna take a stab at a slightly modified version of it here in a sec . . .
  • h
    (the component view)
  • b
    Nice... much appreciated!
  • h
    Does this inspire any better feelings or ideas?
  • h
    No problem! I just hope I can be helpful any little bit I can, haha! My thoughts on this approach was: maybe all that's missing is some spacing. The original design is very compact, so maybe it just felt cramped . . .
  • b
    yeah, i think you are right about the spacing... i wonder if just adding some whitespace at the top will do the job
  • b
    lemme try
  • b
    (i think i also might get rid of the log window - or move it)
  • h
    I was curious about what it did, just for debugging?
  • b
    yeah, it was originally, but not really sure if its of any actual use tbh
  • h
    Perhaps it could be collapsible and then could be used as an emergency reporting tool? Or tells someone something's wrong with the syntax, etc
  • b
    so yeah, i do think that is quite alot better actually... maybe a little text there instead of white space, and line things up a little better
  • h
    I do also think adding some padding to the right of the components list or left of the results would be good too - since they almost blend together at a quick glance; that does look nicer for starters though!
  • b
    right...
  • h
    It's very late my time right now . . I should get some sleep; but good luck man! I like everything I'm seeing right now 👋
  • b
    thanks for the input! Sleep well!
  • b
    defo better i think
  • b
    👍
  • q
    @brave-kangaroo-30399 here I'm thinking I need to actually pop things open, but we can just start with the question itself. I submitted two issues around the same time. Neither had followups. The question now is "are the two of these still not fixed, then?" I've not tried to build with the recent version. Probably the next move here, but we can at least clarify these were the two issues I was referring to.
  • b
    Oh I forgot about the first one
  • b
    I still need to see if that one is a flash (and potentially OpenFL) limitation for large bmds
  • q
    To be fair, I've not tested them.
  • q
    As I said, it's only intended as clarification on the question itself.
  • q
    Note that 16 and 15 are distinct issues.
  • q
    I fear you may be thinking more of 15. 16 appears to be able to be triggered with as little as "just enough to make it actually be a scrollable".
  • q
    I suppose we have mouse events now, I could try a text box.
  • q
    It also does appear that 16 and 17 are related; it has something to do with how switching between ui surfaces works. [Edit: Which I think we concluded was an architectural issue that wouldn't be easy to solve in Flixel for substates]
1...9899100...1687Latest