• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Frame's setSize() method is not working

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


Everytime I run this code, it results into a maximised window, preventing the setSize() method from taking any effect !!! Please help
 
Ranch Hand
Posts: 174
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
works, no issue

- JFrame returns Dimension(200, 200)

- ContentPane returns JFrames Dimansion minus Borders and toolbar (L&F sensitive)

- read Oracles tutorial about Initial Thread

- don't extends JFrame, create this Object as an local variable
 
Marshal
Posts: 79177
377
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That was correect, but a bit laconic.
This is where you find out about the single thread policy. As for not extending JFrame, you should do this:-Don’t use null layout. You often do not need to get the content pane separately from the frame.
 
Abhimanyus singh
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Campbell Ritchie wrote:That was correect, but a bit laconic.
This is where you find out about the single thread policy. As for not extending JFrame, you should do this:-Don’t use null layout. You often do not need to get the content pane separately from the frame.




It's still not working...let me explain it....the moment I run the program, it opens the frame in MAXIMIZED mode.!!! Earlier it was not happening.
 
Campbell Ritchie
Marshal
Posts: 79177
377
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Abhimanyus singh wrote: . . .....the moment I run the program, it opens the frame in MAXIMIZED mode.!!! Earlier it was not happening.

It didn’t appear maximised when I tried it.
 
Bartender
Posts: 5167
11
Netbeans IDE Opera Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Abhimanyus, how, exactly are you executing that code?
 
Ranch Hand
Posts: 4716
9
Scala Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
not sure if this will help, just a couple points. i also don't extend JFrame anymore but i used to.
first, you shouldn't have to call super() in the constructor. at least i didn't have to using no argument constructor and calling setTitle(String) in it.
second you don't have to say "this" all the time.
setSize(200, 200);
and
setVisible(true);
is sufficient.

try getting rid of the call to super(h)
 
Bartender
Posts: 11497
19
Android Google Web Toolkit Mac Eclipse IDE Ubuntu Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Randall Twede wrote:
first, you shouldn't have to call super() in the constructor. at least i didn't have to using no argument constructor and calling setTitle(String) in it.
try getting rid of the call to super(h)


The OP doesn't have a super() but rather a super(h) call which is akin to setTitle(String title).

Randall Twede wrote:
second you don't have to say "this" all the time.


Technically correct. But it is a good practice to use this.xxx and super.xxx as much as possible.

I suspect the OP is executing some old code and getting the strange results. Like Darryl said, once we know exactly, how it is being executed, we will know
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic