Why is my JAR Bundler application lagging or terminating when using OSXAdapter?

JAR Bundler using OSXAdapter causing application to lag or terminate

This question arises from the need to associate a JAR file with a specific file type (.jarbundlerproblem) using Apple's Jar Bundler for OS X. Additionally, the application requires the ability to handle files that are double-clicked and passed as arguments.

To achieve this, the developer utilized the OSXAdapter library to handle file-related events. However, this modification has led to inconsistent behavior in the application. Sometimes, it doesn't open or displays a blank window for an extended period.

Analysis and Solution:

The issue stems from the application's potential to block the event dispatch thread (EDT) due to the use of 'Thread.sleep()' in the 'doWork()' method. This can result in the GUI not being fully responsive or even causing the application to lag or terminate.

Recommended Approach:

To resolve this issue, it is recommended to use a SwingWorker or implement the 'Runnable' interface to perform the time-consuming task in a separate thread. This will free up the EDT, allowing the GUI to remain responsive.

Alternative Approaches for Auto-Scrolling JTable:

• Utilize the 'SwingWorker' class, which automatically invokes 'process()' and updates the model on the EDT.
• Use the 'invokeLater()' method to invoke the model update on the EDT.

Additional Notes:

• It's suggested to use an alternative approach to constructing a Mac OS application bundle without relying on JAR Bundler.
• The code snippet provided in the answer demonstrates how to add rows to a JTable and maintain auto-scrolling behavior.

The above is the detailed content of Why is my JAR Bundler application lagging or terminating when using OSXAdapter?. For more information, please follow other related articles on the PHP Chinese website!