I am developing a Processing sketch in the Eclipse IDE. I have a basic test sketch running in it. Now I need to add a menu, and in my attempt to do it I am using the information in this webpage:
I copied and attempted to run the example code. But there were two errors. One of them I solved by adding “public” before “mouseReleased(” so that it is now:
addMouseListener(new MouseAdapter() {
public void mouseReleased(MouseEvent evt) {
This removed the error in the second line: “Cannot reduce the visibility of the inherited method from MouseAdapter” in the second line above.
There is still an error in the first line I am not sure what to do about. This is: "The method addMouseListener(new MouseAdapter(){}) is undefined for the type " I do not know what to do about this error. Will I have to create a class derived from MouseListener in a separate file, instantiate it in the first file, and qualify the addMouseListener method call by that class?
By qualify I mean, suppose the class I derive from MouseListener is “MouseClass”. Then to use it to qualify in the main file I would do something like this:
mymouse.addMouseListener(new MouseAdapter() {
public void mouseReleased(MouseEvent evt) {
I have taken the info provided by @GoToLoop and the code from the old forum to produce a simple sketch that creates and displays a Java Swing popup menu in Processing 3.5.4 (i.e. latest version). As GoToLoop states this will only work with the default JAVA2D renderer.
Couple of things to point out -
According to the Java documentation the adapter should catch and test both RELEASED and PRESSED events because the trigger is system dependent.
Both Processing and AWT have a class called MouseEvent so we must state explicitly which class we are using.
import javax.swing.*;
import java.awt.event.*;
import java.awt.*;
public JPopupMenu menu = new JPopupMenu();
public Component win;
void settings() {
size(400, 400);
}
void setup() {
// Get the visual component for this sketch
win = (Component) getSurface().getNative();
// Create and add a menu item
JMenuItem item = new JMenuItem("Item Label 1");
item.addActionListener(new ActionListener() {
public void actionPerformed(ActionEvent e) {
System.out.println("Item 1");
}
}
);
menu.add(item);
item = new JMenuItem("Item Label 2");
item.addActionListener(new ActionListener() {
public void actionPerformed(ActionEvent e) {
System.out.println("Item 2");
}
}
);
menu.add(item);
win.addMouseListener(new MouseAdapter() {
// The popup trigger depends on the OS so should check
// both RELEASED and PRESSED
public void mouseReleased(java.awt.event.MouseEvent evt) {
if (evt.isPopupTrigger()) {
menu.show(evt.getComponent(), evt.getX(), evt.getY());
}
}
public void mousePressed(java.awt.event.MouseEvent evt) {
if (evt.isPopupTrigger()) {
menu.show(evt.getComponent(), evt.getX(), evt.getY());
}
}
}
);
}
void draw() {
background(100, 100, 255);
}
Thank you for this code. It is a big help to see it all together. I migrated this code into the Eclipse IDE and it works perfectly. But due to the application I need it for some questions are raised.
The application is to display a menu of available serial ports to select from. The list of available ports can change between times the menu is displayed. This means the calls to menu.add() have to called in the draw() function. Also, to refresh the list, menu.removeAll() will have to be called, and then the calls to menu.add done all over again. Would a call to item.removeAll() also be necessary for each menu item to prevent memory leaks? Or just the one call to menu.removeAll() sufficient?
Deal with the easy one first. In Java a memory leak is caused when an unwanted object that is no longer needed is still being referenced.
If you look at the code the object reference item is declared inside the setup so is a local variable and will be lost when the method ends. So after setup you have no reference to item so you can’t call item.removeAll() . All the ActionListeners are anonymous so no risk of memory leak there.
The only external refernence for the popup-menu menu so a call to menu.removeAll() will remove all JMenuItems objects so these and their ActionListenerers will be garbage collected therefore no memory leak.
Be very wary here, the draw method is executed about 60 times a second so you only want to rebuild the pop-menu if the list of available ports changes. I suggest that you need a mechanism to detect if there has been a change since the menu was updated, the actual way you do this is up to you.
