Java swing when is paintcomponent called

Called automatically when it becomes visible When a window becomes visible uncovered or deminimized or is resized, the "system" automatically calls the paintComponent method for all areas of the screen that have to be redrawn. Called indirectly from a user-defined listener via repaint When a listener mouse, button, keyboard, Change instance variables.

The listener code should set instance variables that paintComponent uses in drawing the panel. After changing the values, the next time paintComponent is called, these new values will be used. Ulf Dittmer. Which is as it should be. You should never call any of the painting methods directly, but rather call "repaint" on the component. You're welcome. Boost this thread! Components are visible in the middle of the panel on using GridBagLayout. Swing - Calling repaint in actionPerformed method.

This is left as an exercise for the reader. When you use getClass. In the case where the class loader loads classes from the file system, these essentially equate to the same thing, and it does actually work though even then there's no technical reason it has to. When the class loader is loading classes by other mechanisms and probably in all cases anyway , then it's important to pay attention to the Java specifications for a resource.

Each substring must be a valid Java identifier. The resource name is of the form shortName or shortName. Both shortName and extension must be Java identifiers. My emphasis. It happens that the file system class loader resolves this in the way you expect, which is why it works in your IDE, but the implementation of getResource Since you have organized your code so that each FXML is in the same package as its corresponding controller file which I think is a sensible way to do things , you could also leverage this in loading the FXML: just load the FXML "relative to its controller":.

This seems fairly natural in this setup, and the compiler will check that you have the package name for CustomerHomeCtrl correct at the point where you import the class. It also makes it easy to refactor: for example suppose you wanted to split sm. In Eclipse you would create the subpackages, drag and drop the FXML and controllers to the appropriate subpackages, and the import statements would automatically be updated: there would be no further changes needed.