You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if the context menu gracefully handled people trying to trigger it before the ContextMenuItems had been found by the ContextMenuComponent.
We could create a Subject that emits the menuItems in the ngAfterContentInit hook of the component and use that in the onMenuEvent method to only trigger the context menu after the menuItems are loaded.
Yes that's a nice idea. Currently I'm using it like this:
Retrieve contextMenuActions anyhow, async way maybe.
Call contextMenuService.show.next.
Would be nice to show a menu with a scroller and than show items.
Though there's one question here. For some reason currently I need to call setTimeout(() => contextMenuService.show.next) otherwise execute actions don't work.
It would be nice if the context menu gracefully handled people trying to trigger it before the ContextMenuItems had been found by the ContextMenuComponent.
We could create a
Subject
that emits the menuItems in thengAfterContentInit
hook of the component and use that in theonMenuEvent
method to only trigger the context menu after the menuItems are loaded.Originally reported by @achyutgp in issue #6.
The text was updated successfully, but these errors were encountered: