Annotation dialog garbled: has the location or format of "layout.dat" changed recently?

[Tobias Leupold]

E-Mail von Andreas Schleth via KPhotoAlbum vom Montag, 29. Dezember 2025, 
00:23:
> Hi Johannes,
> 
> im onto it - the bug report :-)

... and now, we should also be able to save the state either globally or for 
the very db being opened. If no db-specific state is found, the global state 
is used automatically.

Andreas, would you be so kind to test again?

> Andreas
> 
> Am 28.12.25 um 22:52 schrieb Johannes Zarl-Zierl:
> > Hi,
> >
> >
> > Am Sonntag, 28. Dezember 2025, 21:53:36 Mitteleuropäische Normalzeit 
schrieb
> > Tobias Leupold:
> >> E-Mail von Andreas Schleth via KPhotoAlbum vom Sonntag, 28. Dezember 
2025,
> >>
> >> 21:26:
> >>> Hi Tobias,
> >>>
> >>> thanks for the info - yes, I missed some release notes.
> >>> However, this is bad news (for me). The new method saves one layout for
> >>> all different databases. Which does not work for me.
> >> IIRC, we officially support using multiple databases meanwhile (do we?!)
> >> So what you do seems to be a legitimate use-case we should support, as
> >> having different categories in different databases may make different
> >> layouts necessary.
> > Yes, we did accept some patches to improve the multi-database scenario 
(after
> > this particular change). From my point of view it makes sense to try to 
not
> > break your use-case.
> >
> >> Maybe, we could extend the window titles with the database base dir, so 
the
> >> dataset read would be automatically matched with the database in use, 
which
> >> also would allow multiple instances to run at once without collisions?
> >>
> >> Just brainstorming ...
> > Regarding a possible fix: it would be great to continue this as a bug 
report so
> > that there is a publicly available description of the problem that we can 
link
> > to in the changelog...
> >
> > Cheers,
> >    Johannes
>