Closed ilkeraslan closed 3 years ago
Thank you @Dement0, but I'll have to this in favor of #9. If you're picking up a feature, it's worth calling dibs on the issue to make sure someone else isn't already working on it 😄.
FWIW I don't think there's enough value in exposing proxy setters for CascadePopupMenu#menu
when it's already a public property. This is also in line with PopupMenu
.
Thank you @Dement0, but I'll have to this in favor of #9. If you're picking up a feature, it's worth calling dibs on the issue to make sure someone else isn't already working on it smile.
FWIW I don't think there's enough value in exposing proxy setters for
CascadePopupMenu#menu
when it's already a public property. This is also in line withPopupMenu
.
@saket In fact I asked for to work on this issue before #9 (if you check the related issue you can easily notice that) and nobody was working on it so I've made the PR. While #9 was made before asking for if someone was already working on it or not.
For the record, #9 was opened just a few seconds before my PR.
Anyways, it's your project so you decide. Good luck!
This PR addresses the issue #1 .
addToGroup()
example:removeFromGroup()
example:Note: The
setGroupVisible()
method is not implemented as it sets the visibility of MenuItems without removing the space. One possible workaround would be to callremoveFromGroup()
method when the user callssetGroupVisible(false)
andaddToGroup()
method when the user callssetGroupVisible(false)
. To be able to implement this, though, we should memorize the MenuItems added locally before removing them in order to recreate them whensetGroupVisible(false)
is called. Consequently, this would be a duplicate implementation of the existingaddToGroup()
andremoveFromGroup()
methods.