This question is answered. Helpful answers available: 2. Correct answers available: 1.

Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 7 - Pages: 1 - Last Post: 17 Apr 24, 15:01 Last Post By: davidekholm
JeffTucker

Posts: 8,225
Registered: 31-Jan-2006
Yet another fatal flaw in the integrated browser
Posted: 15 May 23, 23:41 		 
  Click to reply to this thread Reply
Do this simple test:

  • Create a new album with a handful of suitably large original images (big enough to produce sharp theme images, like 4000x3000 originals).
  • Choose Neptune, with default settings.
  • Adjust the theme image crop.
  • Make the album.
  • Preview the album in the integrated/windowed browser. Looks OK.
  • Now go back to Neptune > Title Bar, and switch to the Full page theme image. Click OK, and notice that the theme image crop mask has changed size.
  • Make the album, and try to preview it.

The browser is stubbornly continuing to use the theme image that was produced for the 300px-high theme image in the default settings. There is simply no amount of refreshing or forced remaking that will show you a proper preview of the album. You can even delete the local album and make it again, and still the integrated browser is using the now-nonexistent version of the theme image. As a quick sanity check, click the icon that opens the album in your default browser, and you'll see what it's supposed to look like.

ETA: One more data point. Closing and reopening the project isn't enough to fix the problem. If you shut down jAlbum, relaunch, reopen, and preview again, it finally straightens itself out.
hanso

Posts: 95
Registered: 16-Apr-2008
Re: Yet another fatal flaw in the integrated browser
Posted: 16 May 23, 10:57   in response to: JeffTucker in response to: JeffTucker 		 
  Click to reply to this thread Reply
Must be stubborn caching!

Does the integrated browser cache items (obviously it does) and how and where is the cache emptied? Can jalbum force the cache content to be deleted?
davidekholm

Posts: 3,483
Registered: 18-Oct-2002
Re: Yet another fatal flaw in the integrated browser
Posted: 16 May 23, 12:07   in response to: hanso in response to: hanso 		 
  Click to reply to this thread Reply
I've been struggling with this annoying caching behavior myself. It's a known problem, but I don't know of any easy solution. I've tried to apply any API switches to turn off caching that I've found. We're talking about the "JavaFX WebView" and "WebEngine" components in case you're interested in googling it.

I soon plan to switch from Java 19 to Java 20. In the v20 release, they have updated the underlying binaries for the WebView/WebEngine components. Hopefully this will improve several aspects of the embedded browser. Unfortunately, the updated JavaFX files requires at least Java 17 to run, meaning that we can no longer provide a Java14 version of jAlbum for users running older Macs.
JeffTucker

Posts: 8,225
Registered: 31-Jan-2006
Re: Yet another fatal flaw in the integrated browser
Posted: 16 May 23, 14:26   in response to: davidekholm in response to: davidekholm 		 
  Click to reply to this thread Reply
davidekholm wrote:
I've tried to apply any API switches to turn off caching that I've found.

Yes, given the way we're using the browser, it would be nice if it didn't do any caching at all, since there's no "bandwidth" to worry about.

Alternatively, is there a way to refresh the cache on demand?

I soon plan to switch from Java 19 to Java 20. In the v20 release, they have updated the underlying binaries for the WebView/WebEngine components. Hopefully this will improve several aspects of the embedded browser. Unfortunately, the updated JavaFX files requires at least Java 17 to run, meaning that we can no longer provide a Java14 version of jAlbum for users running older Macs.

The hardware lasts too long. If Catalina and earlier won't handle Java 20, that effectively cuts out any hardware that's more than about 10 years old. My 10-year-old Macbook Air is still perfectly healthy - even the "battery health" is fine. The processor is slow, compared to newer equipment, but the laptop isn't ready for the trash bin. It's running Big Sur, so it's still taking the latest Java releases without complaint.
davidekholm

Posts: 3,483
Registered: 18-Oct-2002
Re: Yet another fatal flaw in the integrated browser
Posted: 16 May 23, 17:43   in response to: JeffTucker in response to: JeffTucker 		 
  Click to reply to this thread Reply
I haven't found any way to force a refresh or clear the cache on demand. I've been googling "clear javafx webview/webengine cache" "turn off javafx webview/webengine cache etc.
JeffTucker

Posts: 8,225
Registered: 31-Jan-2006
Re: Yet another fatal flaw in the integrated browser
Posted: 1 Jun 23, 14:35   in response to: davidekholm in response to: davidekholm 		 
  Click to reply to this thread Reply
It's even worse than I realized. If you simply choose a different image for the theme image and make the album again, you don't see the new theme image until you have shut down jAlbum and relaunched it. I can imagine a lot of user confusion in that situation.
JeffTucker

Posts: 8,225
Registered: 31-Jan-2006
Re: Yet another fatal flaw in the integrated browser
Posted: 17 Apr 24, 00:00   in response to: JeffTucker in response to: JeffTucker 		 
  Click to reply to this thread Reply
This problem appears to have been fixed in JavaFX 22.
davidekholm

Posts: 3,483
Registered: 18-Oct-2002
Re: Yet another fatal flaw in the integrated browser
Posted: 17 Apr 24, 15:01   in response to: JeffTucker in response to: JeffTucker 		 
  Click to reply to this thread Reply
That's awesome. I didn't test that.
Pages: 1
Back to Thread List Back to Thread List
Legend
Forum admins
Helpful Answer
Correct Answer

Point your RSS reader here for a feed of the latest messages in all forums