# haxe-ui
- u
user
08/08/2021, 8:44 PMYeah I have subtle types / constants and very subtle keywords and that's pretty much all - b
bright-gpu-74537
08/08/2021, 8:44 PMfor me, for my, dunno, eyesight? - b
bright-gpu-74537
08/08/2021, 8:45 PMthats perfect - b
bright-gpu-74537
08/08/2021, 8:45 PM... maybe its just what you get used to - u
user
08/08/2021, 8:45 PMI never usebrightlight themes so it's difficult to tell if I'd like it, but yeah seems to focus on similar things - u
user
08/08/2021, 8:45 PMNothing for type params? - b
bright-gpu-74537
08/08/2021, 8:46 PMnormally yeah, but its because itsimport wx.widgets.Point in WxPoint; - b
bright-gpu-74537
08/08/2021, 8:46 PMand HD doesnt like that apparently - u
user
08/08/2021, 8:47 PMYeah, only LSP based editors would get it (or treesitter but I don't think we have a working config for haxe yet) - u
user
08/08/2021, 8:48 PMWell, "dumb" ones could get it for type hints and type parameters with regexes, but meh :P - b
bright-gpu-74537
08/08/2021, 8:49 PMso... that sample... ... it recreated the whole wxStaticText - u
user
08/08/2021, 8:49 PMSeems like they're aware that it doesn't work to update align xD - b
bright-gpu-74537
08/08/2021, 8:49 PMyup - u
user
08/08/2021, 8:49 PMCheaters :P - b
bright-gpu-74537
08/08/2021, 8:50 PMdefo... - b
bright-gpu-74537
08/08/2021, 8:50 PMrecreating the window, i dont think, is that much of a pain though... but its more complex than "just do x"... so ill have to think about it - u
user
08/08/2021, 8:51 PMIs there a way to read styles before creating the component? - b
bright-gpu-74537
08/08/2021, 8:51 PMi think i could recreate any wxWindow pretty easy in haxeui... in fact, i think i do it somewhere - b
bright-gpu-74537
08/08/2021, 8:51 PMvalid point... that might be the path of least resistance - u
user
08/08/2021, 8:51 PMI don't mind if I can't alter the align after creation tbh - u
user
08/08/2021, 8:56 PMIs there an easier way to get a component's position inside current window? (as in the whole window, not wxWindow)Copy codevar pos = newTaskButton.window.clientToScreen(newTaskButton.window.position); pos = haxe.ui.core.Screen.instance.rootComponents[0].window.screenToClient(pos); // unsafe °° - b
bright-gpu-74537
08/08/2021, 8:59 PMdoesnt
work?myComponent.screenLeft/Top - u
user
08/08/2021, 8:59 PMEh, must have missed it because I looked for `Point`s x) - u
user
08/08/2021, 9:00 PMThanks, trying that - b
bright-gpu-74537
08/08/2021, 9:00 PMyeah, point would be nicer tbh as if you want top/left, which you usually do, you end up running it twice - b
bright-gpu-74537
08/08/2021, 9:01 PMin fact, just looking at my todo list there is a "implement .screenBounds" - u
user
08/08/2021, 9:01 PMWorks :) Gives slightly different results, but I suppose the previous (ugly) solution was giving me position relative to window border - u
user
08/08/2021, 9:02 PMWill check with a screenshot :P - b
bright-gpu-74537
08/08/2021, 9:02 PMi would guess that screenTop is based on the client size (ie, no title bar, border) - u
user
08/08/2021, 9:03 PMYeah. Perfect, that's what I need :)