JavaFX context menu item group
I want to set visibility of some (not all) context menu items inside the same context menu without having to explicitly set visibility of each of them as that seems like a lot of boilerplate code. Is there any way to have a common container or something similar for these menu items, so that I can simply set the visibility of this container? I've googled for a bit but found nothing related so far.
I'm thinking about giving these menu items the same css class then creating 2 style sheets that define the behaviour of this class, one with visibility:visible and the other visibility:hidden, then I can dynamically load the style sheets to suit my need. I believe this could work but it seems a bit hacky for my taste. I would prefer a more normal way to do this.
java javafx contextmenu menuitem
asked Nov 15 '18 at 23:18
GnasGnas
528210
add a comment |
I want to set visibility of some (not all) context menu items inside the same context menu without having to explicitly set visibility of each of them as that seems like a lot of boilerplate code. Is there any way to have a common container or something similar for these menu items, so that I can simply set the visibility of this container? I've googled for a bit but found nothing related so far.
I'm thinking about giving these menu items the same css class then creating 2 style sheets that define the behaviour of this class, one with visibility:visible and the other visibility:hidden, then I can dynamically load the style sheets to suit my need. I believe this could work but it seems a bit hacky for my taste. I would prefer a more normal way to do this.
java javafx contextmenu menuitem
asked Nov 15 '18 at 23:18
GnasGnas
528210
add a comment |
I want to set visibility of some (not all) context menu items inside the same context menu without having to explicitly set visibility of each of them as that seems like a lot of boilerplate code. Is there any way to have a common container or something similar for these menu items, so that I can simply set the visibility of this container? I've googled for a bit but found nothing related so far.
I'm thinking about giving these menu items the same css class then creating 2 style sheets that define the behaviour of this class, one with visibility:visible and the other visibility:hidden, then I can dynamically load the style sheets to suit my need. I believe this could work but it seems a bit hacky for my taste. I would prefer a more normal way to do this.
java javafx contextmenu menuitem
asked Nov 15 '18 at 23:18
GnasGnas
528210
I want to set visibility of some (not all) context menu items inside the same context menu without having to explicitly set visibility of each of them as that seems like a lot of boilerplate code. Is there any way to have a common container or something similar for these menu items, so that I can simply set the visibility of this container? I've googled for a bit but found nothing related so far.
I'm thinking about giving these menu items the same css class then creating 2 style sheets that define the behaviour of this class, one with visibility:visible and the other visibility:hidden, then I can dynamically load the style sheets to suit my need. I believe this could work but it seems a bit hacky for my taste. I would prefer a more normal way to do this.
java javafx contextmenu menuitem
java javafx contextmenu menuitem
asked Nov 15 '18 at 23:18
GnasGnas
528210
asked Nov 15 '18 at 23:18
GnasGnas
528210
edited Nov 15 '18 at 23:27
Gnas
asked Nov 15 '18 at 23:18
GnasGnas
528210
asked Nov 15 '18 at 23:18
GnasGnas
528210
asked Nov 15 '18 at 23:18
GnasGnas
528210
528210
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Bind their visibility properties to a single, separate property.
private final BooleanProperty selectionItemsVisible =
new SimpleBooleanProperty();
// ...
cutMenuItem.visibleProperty().bind(selectionItemsVisible);
copyMenuItem.visibleProperty().bind(selectionItemsVisible);
saveSelectionMenuItem.visibleProperty().bind(selectionItemsVisible);
// ...
selectionItemsVisible.set(true);
answered Nov 16 '18 at 0:49
VGRVGR
23.4k42840
This is indeed better than my CSS approach. I would still prefer a common parent approach though. I mean what if I want other behaviours that are shared between the menu items such as dragging or removing them as a group. Do you have any suggestions?
– Gnas
Nov 16 '18 at 8:32
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53329219%2fjavafx-context-menu-item-group%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Bind their visibility properties to a single, separate property.
private final BooleanProperty selectionItemsVisible =
new SimpleBooleanProperty();
// ...
cutMenuItem.visibleProperty().bind(selectionItemsVisible);
copyMenuItem.visibleProperty().bind(selectionItemsVisible);
saveSelectionMenuItem.visibleProperty().bind(selectionItemsVisible);
// ...
selectionItemsVisible.set(true);
answered Nov 16 '18 at 0:49
VGRVGR
23.4k42840
This is indeed better than my CSS approach. I would still prefer a common parent approach though. I mean what if I want other behaviours that are shared between the menu items such as dragging or removing them as a group. Do you have any suggestions?
– Gnas
Nov 16 '18 at 8:32
add a comment |
Bind their visibility properties to a single, separate property.
private final BooleanProperty selectionItemsVisible =
new SimpleBooleanProperty();
// ...
cutMenuItem.visibleProperty().bind(selectionItemsVisible);
copyMenuItem.visibleProperty().bind(selectionItemsVisible);
saveSelectionMenuItem.visibleProperty().bind(selectionItemsVisible);
// ...
selectionItemsVisible.set(true);
answered Nov 16 '18 at 0:49
VGRVGR
23.4k42840
This is indeed better than my CSS approach. I would still prefer a common parent approach though. I mean what if I want other behaviours that are shared between the menu items such as dragging or removing them as a group. Do you have any suggestions?
– Gnas
Nov 16 '18 at 8:32
add a comment |
Bind their visibility properties to a single, separate property.
private final BooleanProperty selectionItemsVisible =
new SimpleBooleanProperty();
// ...
cutMenuItem.visibleProperty().bind(selectionItemsVisible);
copyMenuItem.visibleProperty().bind(selectionItemsVisible);
saveSelectionMenuItem.visibleProperty().bind(selectionItemsVisible);
// ...
selectionItemsVisible.set(true);
answered Nov 16 '18 at 0:49
VGRVGR
23.4k42840
Bind their visibility properties to a single, separate property.
private final BooleanProperty selectionItemsVisible =
new SimpleBooleanProperty();
// ...
cutMenuItem.visibleProperty().bind(selectionItemsVisible);
copyMenuItem.visibleProperty().bind(selectionItemsVisible);
saveSelectionMenuItem.visibleProperty().bind(selectionItemsVisible);
// ...
selectionItemsVisible.set(true);
answered Nov 16 '18 at 0:49
VGRVGR
23.4k42840
answered Nov 16 '18 at 0:49
VGRVGR
23.4k42840
answered Nov 16 '18 at 0:49
VGRVGR
23.4k42840
answered Nov 16 '18 at 0:49
VGRVGR
23.4k42840
23.4k42840
This is indeed better than my CSS approach. I would still prefer a common parent approach though. I mean what if I want other behaviours that are shared between the menu items such as dragging or removing them as a group. Do you have any suggestions?
– Gnas
Nov 16 '18 at 8:32
add a comment |
This is indeed better than my CSS approach. I would still prefer a common parent approach though. I mean what if I want other behaviours that are shared between the menu items such as dragging or removing them as a group. Do you have any suggestions?
– Gnas
Nov 16 '18 at 8:32
This is indeed better than my CSS approach. I would still prefer a common parent approach though. I mean what if I want other behaviours that are shared between the menu items such as dragging or removing them as a group. Do you have any suggestions?
– Gnas
Nov 16 '18 at 8:32
This is indeed better than my CSS approach. I would still prefer a common parent approach though. I mean what if I want other behaviours that are shared between the menu items such as dragging or removing them as a group. Do you have any suggestions?
– Gnas
Nov 16 '18 at 8:32
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53329219%2fjavafx-context-menu-item-group%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
