# haxe-ui
- b
bright-gpu-74537
08/17/2021, 5:48 AMill take a look at it a little later... doesnt seem to hard to fix, and its almost there now tbh - u
user
08/17/2021, 5:48 AMWould composite backends support a context menu event? - u
user
08/17/2021, 5:49 AMI think js-based ones should, at least (yeah: https://developer.mozilla.org/en-US/docs/Web/API/Element/contextmenu_event) - b
bright-gpu-74537
08/17/2021, 5:49 AMdepends i guess, if not it could always just map it to right click, no biggie - u
user
08/17/2021, 5:50 AMI'll add a PR for that - b
bright-gpu-74537
08/17/2021, 5:50 AM👌 - u
user
08/17/2021, 5:50 AMStill need to find a way to use haxeui's Menu; iirc it wasn't building its window so I couldn't grab the hx.widgets.Menu reference for popupMenu - b
bright-gpu-74537
08/17/2021, 5:50 AMi think there needs some other work too though, not just the trigger as something else is weird... - u
user
08/17/2021, 5:51 AM(and find a common api for hxwidgets' popupMenu and composite backends alternative) - b
bright-gpu-74537
08/17/2021, 5:51 AM> iirc it wasn't building its window exactly, that why i explicitly called .ready... which should never need to be called by the user - u
user
08/17/2021, 5:52 AMThough I could grab something using
at some point iirc.object - b
bright-gpu-74537
08/17/2021, 5:52 AMoh yeah, actually, menu isnt actually a window in wx - u
user
08/17/2021, 5:52 AMAnd it wasn't easy to map to coconut, so I ended up just creating instances - b
bright-gpu-74537
08/17/2021, 5:52 AMbut either way, i had to call ready manually, so something is wrong - b
bright-gpu-74537
08/17/2021, 5:53 AMi wonder if this has always been there or if ive introduced it somehow with this bunch of updates... the fact it has code there makes me thing this is a regression... i wouldnt have been "ok" with calling .ready - u
user
08/17/2021, 5:53 AMWell, it's not added to the screen before popupMenu() is called, so I guess it's normal that it's not "ready"? chicken and egg :x - b
bright-gpu-74537
08/17/2021, 5:54 AMmaybe, but ready is certainly not a user function... if you are calling ready, something is wrong - u
user
08/17/2021, 5:55 AMI think I was calling createWindow or something instead of ready, but same thing it's not user api x) - u
user
08/17/2021, 5:55 AMand it's probably hxwidgets-only x) - b
bright-gpu-74537
08/17/2021, 5:56 AMnope... either way, something is up, 100%... you should never call .ready... ever - b
bright-gpu-74537
08/17/2021, 5:56 AMor should never need to maybe is a better way to say it - u
user
08/17/2021, 5:57 AMSo that would be the composite alternative to
?window.popupMenu(menu) - b
bright-gpu-74537
08/17/2021, 5:57 AMpreviously ive just added the menu to the screen at the correct x/y - u
user
08/17/2021, 5:57 AMWhy is it public? :P - b
bright-gpu-74537
08/17/2021, 5:58 AMis it? - u
user
08/17/2021, 5:58 AMSounds like a sane default (= fallback) behavior - b
bright-gpu-74537
08/17/2021, 5:58 AMyeah, it is - u
user
08/17/2021, 5:59 AMit does say "ok I'm here but don't call me please" though - b
bright-gpu-74537
08/17/2021, 6:02 AM😄 yeah, still dont think it should be public though... ill add it to the list - u
user
08/17/2021, 8:28 PMFirst step: https://github.com/haxeui/hxWidgets/pull/78 Some things were actually off :x