Skip to main content

JComboBox with Disabled Items

Recently, I was working on a project in Java and needed to have a combo box, but with certain items in the list disabled (e.g. gray and non-selectable). At first, I simply set a custom renderer for the combo box which checked if the item was disabled. That, however, did not prevent the items from being selected. Thus, I set about to find a viable solution. There are plenty of solutions out there, but none seemed to work exactly the way I wanted. In the end, I ended up subclassing JComboBox to provide the functionality of disabling individual items. Here is my result, in under 100 lines:

import java.awt.Component;
import java.util.ArrayList;

import javax.swing.JComboBox;
import javax.swing.JList;
import javax.swing.plaf.basic.BasicComboBoxRenderer;

public class PartialDisableComboBox extends JComboBox {
 private static final long serialVersionUID = -1690671707274328126L;
 
 private ArrayList<boolean> itemsState = new ArrayList<boolean>();
 
 public PartialDisableComboBox() {
  super();
  this.setRenderer(new BasicComboBoxRenderer() {
   private static final long serialVersionUID = -2774241371293899669L;
   @Override
   public Component getListCellRendererComponent(JList list, Object value, 
     int index, boolean isSelected, boolean cellHasFocus) {
    Component c = super.getListCellRendererComponent(list, value, index, isSelected, cellHasFocus);
    boolean disabled = index >= 0 && index < itemsState.size() && !itemsState.get(index);
    c.setEnabled(!disabled);
    c.setFocusable(!disabled);
    return c;
   }
  });
 }
 
 @Override
 public void addItem(Object item) {
  this.addItem(item, true);
 }
 
 public void addItem(Object item, boolean enabled) {
  super.addItem(item);
  itemsState.add(enabled);
 }
 
 @Override
 public void insertItemAt(Object item, int index) {
  this.insertItemAt(item, index, true);
 }

 public void insertItemAt(Object item, int index, boolean enabled) {
  super.insertItemAt(item, index);
  itemsState.add(index, enabled);
 }
 
 @Override
 public void removeAllItems() {
  super.removeAllItems();
  itemsState.clear();
 }
 
 @Override
 public void removeItemAt(int index) {
  if (index < 0 || index >= itemsState.size()) throw new IllegalArgumentException("Item Index out of Bounds!");
  super.removeItemAt(index);
  itemsState.remove(index);
 }
 
 @Override
 public void removeItem(Object item) {
  for (int q = 0; q < this.getItemCount(); q++) {
   if (this.getItemAt(q) == item) itemsState.remove(q);
  }
  super.removeItem(item);
 }
 
 @Override
 public void setSelectedIndex(int index) {
  if (index < 0 || index >= itemsState.size()) throw new IllegalArgumentException("Item Index out of Bounds!");
  if (itemsState.get(index)) super.setSelectedIndex(index);
 }
 
 public void setItemEnabled(int index, boolean enabled) {
  if (index < 0 || index >= itemsState.size()) throw new IllegalArgumentException("Item Index out of Bounds!");
  itemsState.set(index, enabled);
 }
 
 public boolean isItemEnabled(int index) {
  if (index < 0 || index >= itemsState.size()) throw new IllegalArgumentException("Item Index out of Bounds!");
  return itemsState.get(index);
 }
}

As you can see, most of the code is pretty straightforward, adding and removing elements from the JComboBox and the list of item states. The custom renderer is still used to provide the L&F for the disabled items, but the key to having the disabled items non-selectable is the setSelectedIndex(int) method. There are also plenty of index range checks thrown in there, especially in the custom renderer, as the combo box calls that method with index = -1 when rendering the combo box in its "closed" state (without the dropdown).

Of course, I want give credit to some other blogs that helped lay the groundwork and point me in the right direction, but unfortunately I don't remember their names. If I find them again, I'll be sure to include them in this post.

As always, please let me know if you find this useful, or if you find any bugs or possible improvements.

Comments

  1. This comment has been removed by the author.

    ReplyDelete
  2. This is working great (just had to make a quick change from boolean to Boolean for private ArrayList (maybe a Java7 thing?). Just what I needed. Thanks.

    ReplyDelete

Post a Comment

Popular posts from this blog

Linux on XPS 15 9550/9560 with TB16 Dock [Update:3/29]

Finally got a laptop to replace my fat tower at work - Dell XPS 15 9560. I was allowed to choose which one I wanted and chose the XPS for its Linux support since Dell ships developer edition XPS's running Ubuntu so I figured Linux support would be better than other manufacturers. At first they got me the model with the 4K screen but my monitors are 2K and multi-dpi support in Linux is virtually non-existent and even hi-dpi support on its own is pretty terrible. So I got it exchanged for the model with the regular 1080p screen (which happened to also be the updated 9560 model), which works much better. I'm very glad to report that pretty much everything works, including the TB16 desktop dock, with just a bit of settings tweaking. This post is to help anybody considering getting this setup or looking for help getting things working. For now, I am running Kubuntu 16.04 with KDE Neon installed. List of things I explicitly tested and work: WiFi, Bluetooth Thunderbolt charging

Converting single-touch events to mouse events

Many times, there are various interactions that take place in a web app based on mouse movement, clicking, dragging, etc. With a mouse, this is fairly simple, as there is a single point, and events like mousedown, mouseup, and mousemove can be used to discover the state of the mouse at any given time. On mobile browsers, however, it's a different story. Most phones support at least some kind of multi-touch, and the mousedown and mouseup events are not fired (there is, after all, no button). In addition, mousemove will only be applicable when dragging. Instead, mobile browsers dispatch touchstart, touchmove, and touchend events. Moreover, these events keep track of all touch points, not just the first or last one, and as such make handling them a bit more difficult. For the purposes of an application that only requires tracking clicks and drags, it is more convenient to translate these touch events into mouse events without having code duplication. This can be accomplished quick