jgraphx | jgraphx 4.0.4 build for cs project | Video Game library

I see 3 major problems in your code:

1. Inappropriate use of a static field: protected static mxGraph graph = new mxGraph() {
2. Inappropriate inheritance: public class AddGraphLink extends Editor {
3. And again, inappropriate inheritance: class AddGraphNode extends Editor {

By making the graph field static, changes made to one variable will be felt in all variables, and this is the likely cause for your so-called "artifacts". And the reason that you feel that you must make the field static is because since the two classes above are inheriting from Editor (again inappropriately). The solution is obvious:

1. Make the graph field an instance field, not a static one, and
2. Don't use inheritance where it doesn't belong. Instead your AddGraphXxxx classes should not extend Editor but rather should have Editor fields within them, one that you can set via the constructor, and one whose methods you can call, something like this, for example:

Swing uses layout managers. The default layout manager for a JFrame is the BorderLayout. When you add a component to the frame the default constraint used is BorderLayout.CENTER. Only a single component can be added to the CENTER of the BorderLayout.

The setBounds(...) will only work temporarily. As soon as the frame is resized the layout manager is invoked and the button will be given the new size/location based on the rules of the layout manager.

The solution is to use layout managers properly. I'm not sure what layout you are trying to achieve so all I can suggest is that you read the Swing tutorial on Layout Managers for working examples to get you started. Then you can nest panels with different layout managers to achieve your desired effect.

Start with something simple like:

I found the solution. The object properties in the object class (here Valve) should be the same as the getter/setter method name. For example, the variable (property) with the name "_valveName" should match its getter/setter method. Here the getter/setter methods for this variable are:
public void setElementName(String elementName) public String getElementName() Which are not the same as variable name. So, by changing either the variable name or getter/setter method names the problem get solved. Here is the revised custom object class:

Yikes, not sure how I feel about this but here is a solution. I partially converted the tree.html example from JavaScript to Java. I did not convert all of the code to Java; I didn't even try because I do not care about the location of the collapse button. I did get the functionality I desired. I did add a few codes that the super method was performing in case that portion is important to keep.

If anyone wants to finish converting the example and provide that to me I will gladly award you the answer instead of awarding myself the answer. Other ways to get awarded the answer - point out a bug in my code, improve it in someway or provide a better approach with code.

Here is my Java code:

It is not possible :( (atleast as of now).

Using the EDGESTYLE_ELBOW is not a bad option but if you want to use the layout you can probably adapt the following.

The CompactTreeLayout creates a edge of three points. If you extend the layout, you can edit the first 2 points of the edge to be the x midpoint of the source vertex bounds. Below is an example for vertical layout option of the CompactTreeLayout.