It's possible to disable custom color from color picker?

Question

Hi guys!
I've searched in the threads about color picker but I found anything about it...
It's possible to disable the option to select a custom color? I work in a enterprise who makes softwares to brazilian clients, and not everybody understands english phrases...
Another way it's to translate the option, but I don't know if is possible too.
Thanks!

Answer 1

You definitely need to add the stylesheet to the Scene, not to anything else. If you take my example and change
scene.getStylesheets()...
to
root.getStylesheets()...
you'll see that it won't work any more.
The difference between this and the css you used is that the css you used is applied to the display of the color picker button; you need to apply styles to the popup (the color palette), which is not contained in your VBox or AnchorPanes. Notice how the font has changed for the name of the color in the button, but it hasn't changed for the "Custom Color" label you are trying to remove.
Somewhere there is some code that is adding the VBox you are subclassing to a Scene, and setting that scene into a stage. Your best option (perhaps second best option, see below) is to find that code so you can add the stylesheet to the Scene itself.
If you're working within a framework someone else has written, and can't access or change the code where the scene is defined, you have another option that I can see. Every Node has a scene property that refers to the scene to which that node belongs. So you could observe changes to that property and when it's updated, add the stylesheet to the scene.
So here is a hack to make my original hack work, in the event that you cannot access the scene directly, for some reason:
final String suppressCustomColorCss = getClass().getResource( "noCustomColorPicker.css").toExternalForm();
colorPicker.sceneProperty().addListener(new ChangeListener<Scene>() {
@Override
  public void changed(ObservableValue<? extends Scene> observable,
  Scene oldScene, Scene newScene) {
  if (newScene != null) {
  List<String> cssClasses = newScene.getStylesheets();
  if (!cssClasses.contains(suppressCustomColorCss)) {
  cssClasses.add(suppressCustomColorCss);
This code basically says "when the color picker becomes part of a new scene, add the stylesheet to that scene".
At this point, you're applying hack on top of hack to get the effect you need. I think if I were in this situation I would just go ahead and define my own color picker. All you really need is a MenuButton, a property to hold the selected color, and a popup with a layout of controls to choose an arbitrary color. It would be a bit of work, but shouldn't be too hard. If you take this option (which I think may be your best bet), it's more work now but it will be clear what you are doing - when you (or other programmers on your team) come back to the code later you'll understand how it works much better.
You should also file a couple of feature requests. One for API to enable/disable the option to choose a custom color, as this seems like a reasonable piece of functionality to have. The other should be for properly internationalized text for the labels in the color picker, as these are currently just hard coded into the source code in English.