Family Historian User Group

There are FH options to control the maximum size of images when creating a CD/DVD. In all cases I want the image popup to be the size of the image that resides in FH's media folder.

This is particularly important with certificates and census records where an image does often have to be displayed greater than the default max size of 1000 x 800 in order that the displayed document may be read. I will usually scan/save such documents at a larger size.

No matter what I do FH ignores the picture option size I choose, i.e. 'No Maximum Size', and always uses the default. I've also tried setting a specific size but it still reverts to default.

Interestingly, if I set my max size option then click next to view the next step in the CD Creation process, then click 'back' to go back a step, my chosen option has already been dumped in favour of the default!

How can I make FH do what I want, or is this a bug?

ID:6485

Gordon says:

No matter what I do FH ignores the picture option size I choose.

It is not that FH is ignoring your choice, but that the pop-up window script is limiting the size to a percentage of the available browser window size.
So beyond a certain point your settings have no further enlarging affect.
Choosing Display Full Picture in Own Page does produce a larger image, but not as user friendly as a pop-up.

Gordon also says:

If I set my max size option then click next to view the next step in the CD Creation process, then click 'back' to go back a step, my chosen option has already been dumped in favour of the default!

Yes, that would appear to be a minor bug, but if you Finish the wizard your chosen setting is saved as long as Save Settings is ticked.

Thanks for the note about the script, I wasn't aware of that. While the script has a part to play in size restriction from a test I did it seems its not the sole reason for the restriction of the image size display.

When choosing the option 'No Maximum Size' the actual jpg file sizes saved to the Data folder are wrongly being restricted not to exceed 1000 x 800 pixels. I'm sure that's a bug and its probably related to 'going back a step issue' I mentioned in the previous post.

I have now discovered that a way to get round that is to choose a size, say 1400 x 850, and when this is done the jpg files saved to the data folder are only re-sized where they exceed that size.

While this can result in a bigger display than the 'No Maximum Size' option its still not enough to enable some documents to be read because of the percentage scaling you mentioned that's carried out by the lytebox.js script.

I'm no expert in scripts but I did try tweaking some of its settings and while able to cause changes they were not the changes I wanted! For example I changed the setting not to resize images within the pop up window and while this gave a full sized display it went outside the screen boundary and I couldn't scroll to see the rest of the image!

The ideal would be a pop up window with scroll bars within which, where necessary, images can be enlarged to ensure fine detail, on manuscripts for example, can be read. That's beyond my skills but hopefully FH will consider doing this in a future update.

Sorry, you are quite right the No Maximum Size option does not appear to work, is not saved, and the setting reverts to Default (1000 x 800 pixels).
That must be a bug. [frown]

I have also experimented along similar lines, including the lytebox.js script autoResize = true; option, with similar disappointing results, especially given the scrollbars = 'auto'; option.
Most of the lytebox.js script is also beyond my capabilities.
I have my own fhpopup.js script that displays the image at its full size, with scrollbars as necessary, but it does not support zoom controls to enlarge/shrink the image.

For the time being, the best option is as you suggest, to use the Choose Maximum Size option with a setting such as 4000 x 3200 pixels that will allow all images to adopt their natural size.

I have followed your suggestion and will stick with that in the meantime. However, I thought I'd see if the Lytebox developer had a new version of the script at Lytebox.com

There is and I downloaded and replaced the FH version of lytebox.js and lytebox.css in the Data folder. I changed the auto resize setting to false and looked to see what would happen.

The loading of images with the new script is very nice. Also, with the latest version an image exceeding the screen size can be scrolled, not with scroll bars on the pop up window, but with the scroll bars on the web page which now allow one to move around the pop up image. In the same situation in the FH version of Lytebox the web page scroll bars had no effect on the pop up window display at all.

However, if I want to see the entirety of such a large image I have to use my browsers decrease/enlarge web page facilities. In addition I can't find a way to make the 'close' icon appear on the pop up window - it is there and can be clicked - just not seen!

So while using the latest Lytebox has helped in some ways its not an ideal solution, its a bit clunky for the user. It needs a scripting expert!

Should this be the subject of a wish list request?

Gordon, that is a good bit of detective work.

The Close button problem is because lytebox.css expects all such images to be in an images sub-folder.
Either copy the images folder from lytebox_v5.5.zip download into the data folder, or edit lytebox.css and replace every images/ with nothing.

I found it needed this.resizeSpeed = 10; instead of 5 to display quickly.

Further to my comments above, I have updated my own fhpopup.js script to include zoom buttons and scrollbars.
It will soon be published as an extra feature of the Improve Website or CD DVD HTML Plugin.

GordonH said:
snip

Should this be the subject of a wish list request?

I'd say so, yes.

Would the wish be 'FH to use the most recent version of Lytebox in CD/Webpage creation to allow better image navigation and display'

Yes, but it should also request that the script option this.__autoResize = true; be able to be selected in the Publishing Wizard.

tatewise said

Further to my comments above, I have updated my own fhpopup.js script to include zoom buttons and scrollbars.
It will soon be published as an extra feature of the Improve Website or CD DVD HTML Plugin.

Excellent - I look forward to that! Thanks too for the tips about tweaking the latest version of lytebox, I'll play with that a bit more.

ChrisM said

'FH to use the most recent version of Lytebox in CD/Webpage creation to allow better image navigation and display'

tatewise said

the script option this.__autoResize = true; be able to be selected in the Publishing Wizard.

Ok, how about this -

'FH to use the most recent version of Lytebox in CD/Webpage creation to allow better image navigation and display, that the script option 'this.__autoResize = true;' be able to be selected in the Publishing Wizard, and that the pop up window supports a zoom control and scroll bars where needed for media larger than the pop up window.'

Any other suggestions to improve this?

Re the existing No Maximum Size bug, is there a procedure for formally reporting it or will FH pick up on this from the forum anyway?

The updated Improve Website or CD DVD HTML V1.3 Plugin is now available for download.

To report bugs to Calico Pie use [url]mailto:support@family-historian.co.uk[/url] as specified at Family Historian Support.

An updated Improve Website or CD DVD HTML V1.5 Plugin is now available for download.

This version offers the following Image Popup options:

• Default LyteBox v4.0 style Popups supplied with FH
• Latest LyteBox v5.5 style Popups as mentioned above
• Custom Popups supporting Zoom & Scroll in resizeable windows that fix problems reported with V1.3 & V1.4

The LyteBox v5.5 style Popups are slightly modified compared to the standard download to be compatible with FH version as follows.

In lytebox.js :-
this.theme = 'grey';
this.resizeSpeed = 8;
this.maxOpacity = 20;

In lytebox.css :-
All references to the images subfolder have been deleted in order to use the v4.0 image files.
#lbClose, #lbCloseTop { width: 64px; ...
instead of width: 26px; to accommodate the v4.0 CLOSE icon.

Also users could edit the Plugin so this.__autoResize = false; for lytebox.js to obtain the effects discussed above.

Family Historian Support have confirmed that ignoring the max size option is a bug - this is what they say -

'Thank you for pointing that out. I can confirm that it is a bug. It will be fixed in the next minor upgrade, which will be made available as a free upgrade for version 5 users.'

The No Maximum Size issue appears to be fixed in FH V5.0.9.

Thanks for noting that Mike, I plan to create a DVD shortly and will check this out.