JFrame.pack() leaves 10px margin

[AndrewM16921]

I'm working on an application which essentially has a jpanel in a jframe, and then I call .pack() for jframe, and it does what it's suppose to except for a 10px margin on the right and bottom. Any clue why it is doing this? I can provide code if necessary.

[pbrockway2]

I can provide code if necessary.

That would be good - a SSCCE which creates a frame and a panel, adds the panel to the frame then packs and displays the frame.

Also, this is really a Swing question: I'll move it to the AWT/Swing forum.

[AndrewM16921]

Okay, I included the constructors which might be useful below. Also, the full file is here:
privatepaste.com :: Paste ID e905cab22c

...

public Client(String title, int width, int height)
{
	FPS = 0;
	WIDTH = width;
	HEIGHT = height;
	mouseX = mouseY = 0;
	input = new HashMap<String, Boolean>();
	updates = new ArrayList<Updatable>();
	renders = new ArrayList<Renderable>();
	
	setBackground(Color.BLACK);
	setTitle(title);
	panel = new ClientPanel(this, width, height);
	add(panel);
	pack();
	setResizable(false);
	setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
	setVisible(true);
	panel.addMouseListener(this);
	panel.addMouseMotionListener(this);
}

...

public ClientPanel(Client client, int width, int height)
{	
	this.client = client;
	WIDTH = width;
	HEIGHT = height;
	setFocusable(true);
	requestFocus();
	setBackground(Color.BLACK);
	setPreferredSize(new Dimension(WIDTH, HEIGHT));
	period = 20;
}

[pbrockway2]

Did you read the SSCCE link?

You are getting a 10px margin because somewhere within your code you are setting such a margin. The problem is, therefore, to remove things that are not relevant in order to reveal where this margin setting is taking place. That is the strategy suggested by the SSCCE and it is particularly successful: many times you will solve a problem just by revealing it. If you are unsuccessful then you still win because you have code that will be clear to others who might want to look at it.

As it is, people are rather reluctant to download code and undertake, on your behalf, the task of separating what is part of the problem and what is distracting context. More so if there are several hundred lines of code including dependencies on other classes not given which, together, define a class which is ... abstract!

-----

I realise that constructing a SSCCE takes work, but that's the point. It's productive work if it reveals what needs to change.

[AndrewM16921]

Yeah, I'm familiar with the SSCCE thing. I chopped it up and the problem doesn't persist, but I can't seem to isolate what's causing it so I'm working on that at the moment.

[AndrewM16921]

Okay, this is weird. Can the setVisible() method change the size...?

System.out.println(panel.getSize().toString());
setVisible(true);
System.out.println(panel.getSize().toString());

printed this

java.awt.Dimension[width=900,height=700]
java.awt.Dimension[width=910,height=710]

Right well, I fixed it by moving the pack() to the end. Solved.

[Fubarable]

Possibly. Where's your SSCCE?

[mrhid6]

You want to do the set visible and set resizible befor packing

[DarrylBurke]

You want to do the set visible and set resizible befor packing

Whatever gave you that notion? it's not correct.

If you post a guess, please don't phrase it as if it is an authoritative statement.

db