Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
The moose likes Swing / AWT / SWT and the fly likes Handling GUI event separately. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Swing / AWT / SWT
Bookmark "Handling GUI event separately." Watch "Handling GUI event separately." New topic
Author

Handling GUI event separately.

T James
Greenhorn

Joined: Aug 09, 2012
Posts: 2
Good day to all, I'm hoping anyone can give me an idea on how to solve my little problem.

I have a class to handle all GUI drawing/updating but I want to have another class to deal with
all event handling and I am confused on how to proceed.



So basically, I have a main class that calls the EventHandler start() then the EventHandler
should take care of everything. The problem is that the two loop around creating each other
which I suspect is due to them creating new instances of each other. However, I am confused
as to an alternative of handling this.

Anyone care to give hints on how I should proceed with this?
Any words to point me in the right direction is much appreciated. Thanks.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

The EventHandler class shouldn't create a new ScreenHandler object. It needs a reference to the existing ScreenHandler object, doesn't it? So provide EventHandler with a constructor which accepts and stores a ScreenHandler reference, and have ScreenHandler pass itself to that constructor.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Handling GUI event separately.
 
Similar Threads
Problem with Inner Classes
changing font style and size
ActionListener code. Problem deciphering of
Event Handler for current menu selection.
Find jLabel reference to update (from array of jLabels)