Changed behaviour in jAlbum 28 ...

Reply to this Thread

Search Forum

Back to Thread List

Replies: 4 - Pages: 1 - Last Post: 31 May 22, 17:38 Last Post By: AndreWolff

Threads: [ Previous | Next ]

AndreWolff

Posts: 2,269
Registered: 14-Dec-2007

Changed behaviour in jAlbum 28
Posted: 30 May 22, 16:13

ctwist wrote:
I am aware of this bug. It is caused by changed behaviour in jAlbum 28.

Chris I see also some strange behavoiur in my skins with version 28.

What has.been changed in version 28 which can have effect on the skin code?

Edited by: ctwist on 30 May 2022, 16:34
This thread was branched from https://jalbum.net/forum/thread.jspa?threadID=58281

ctwist

Posts: 490
Registered: 27-Sep-2003

Re: Changed behaviour in jAlbum 28
Posted: 30 May 22, 20:05

in response to: AndreWolff

AndreWolff wrote:
What has.been changed in version 28 which can have effect on the skin code?

"AlbumBean.getTargetName(java.lang.String path)" has been removed.
"AlbumBean.getTargetName(java.io.File file)" is available, but I don't want to spend time converting to this method, since it is not needed in Mirage 11.

AndreWolff

Posts: 2,269
Registered: 14-Dec-2007

Re: Changed behaviour in jAlbum 28
Posted: 30 May 22, 21:27

in response to: ctwist

Thanks. I don’t use that I think. But where did you get that information?

ctwist

Posts: 490
Registered: 27-Sep-2003

Re: Changed behaviour in jAlbum 28
Posted: 30 May 22, 21:43

in response to: AndreWolff

The first line in Hanso's stack trace shows that the method does not exist.

The jAlbum API documents the methods that are available in the AlbumBean class.

AndreWolff

Posts: 2,269
Registered: 14-Dec-2007

Re: Changed behaviour in jAlbum 28
Posted: 30 May 22, 21:48

in response to: ctwist

ctwist wrote:
The first line in Hanso's stack dump shows that the method does not exist.

So methods are changed, but skin developers are not informed?

Pages: 1

Back to Thread List

Threads: [ Previous | Next ]

Legend
	Forum admins
	Helpful Answer
	Correct Answer