While experimenting, to figure out the possible source of an error a user is seeing, I stumbled across this old gem. I've been reporting this for years, but it remains unfixed, and it's a real "trap door" bug, one that leaves the user fumbling around to get out of it.

Go to Settings > Images > General, and for either the thumbnail bounds or image bounds, scroll down and choose the "..." entry, as if you were going to enter your own bounds. Now, instead of entering new bounds, just click away to something else.

The core defaults to setting the bounds to 0x0, and you're in no-man's-land. You can't make an album, you can't switch skins, you can't reload the defaults, nothing. You're trapped, unless you figure out what you've done, and reset the bounds to rational values. You just get an endless series of console warnings, crashes, etc.

If the user chooses "..." and doesn't then enter new bounds, or tries to enter 0x0 (or any combination in which one of the dimensions is zero), the core should ignore him, and retain the bounds that were there to start with.

In fact, I think I'd set something like 50x50 as the minimum allowable entry. Stupidly small, but at least the user would get visible images of some sort.

It's possible to land in the same spot by entering an illegal value for the bounds, like 300abc35q, but at least in that case, the user should be well aware of what he's done.

This, of course, is why I always use a JSpinner for entry of a numeric value.

That's almost got it, with one exception. Try a skin like Neptune, which allows the user to specify image bounds for the folder thumbnails. In that one, if the user doesn't enter a value, it ends up being blank. Doesn't cause any errors, and doesn't crash, but the folder thumbnails end up being the same size as the image thumbnails.

And you enter, e.g., 20x10 as the folder thumbnail bounds, it doesn't create a tiny thumbnail, but it doesn't correct the settings display, either.

It must be very silent. Invisible, too!