Little bug fixes:
- Menu: enable/disable menu items depending on the actual state
Better support for videos on double pages
Videos now can play inside double pages also; as long as the complete video box (preview image) fits into either the left or right half of the double page (i.e. it must not be wider than a single page and not cross the fold in the middle.
The operation is very easy: As soon as the above conditions are met, the “In Book Video” checkbox appears and the checkbox is pre-selected.
If the video is too wide or spans across the fold, that option disappears and the video will play in a separate window or tab (depending on the user’s preferences).
A video that “could” play within the book can optionally be opened in a separate window/tab also.
For this simply delete un-check the box.
Improved licence key editiing
Before the licence key had to be entered in clicking
This was not obvious, because no information was provided and the next option to check/verify the key was not shown.
Now it is sufficient to move the mouse out of the licence key field and immediate pre-check is done and the
Check! button is enabled.
WIth one move to the right the then avialble
Check! can be done to verify the license key against the server database.
API and Structure Changes
- css-files re-organized
All Plugin-specific css-File are combined in the all.css file, which will be loaded first.
All Mz3-specific css-Files follow
The last css-File, and with that with the highest priority) is the custom.css File, where you can make Mz3 Project specific Layout changes and overwrite default css-Settings.
- Technology specific Parameters
Element and Book Parameters now are sorted by technology. You now first select the technology, i.e.
- Air (mz3 Viewer)
And then can modify any parameter in the technology-specific list.
Selecting mz3Viewer (i.e. more precisely: AIR) as technology, only a relevant subset of all book parameters supported in FLASH is presented.
Common Parameters are used in all technologies, i.e. modifying a common parameter adjusts that parameter in the other technologies also.
Therefore any parameter missing in mz3Viewer could still be modified in changing the corresponding FLASH parameter. As long as that parameter is supported in mz3Viewer.
Remark: In mz3Viewer e.g. all Internets specific Parameters (like Favicon, HTML Title, …) are not supported.
Sound buttons: one or more play/pause buttons with linked audio files can be put on pages.
Positioning and sizing the same way as with other elements (e.g.images).
Different designs available plus the standard control (browser dependent design)
Sound optionally starts automatically when the corresponding page becomes visible, and stops when the page is left.
A video on a single page now can be opened “in book”, i.e. on a single page of the book. Optionally a new tab can be used.
The video can be expanded to full screen ( both: the “in book” and the “in new tab” videos).
The default browser control (play/pause, scrub, mute/volume) is used.
New Menu Items: e.g. “Show XAMPP Files”, “Browse XAMPP Project”
- Help, Documentation
The new Manual/documentation is used for a context-sensitive help feature:
With every click of a menu item (and often when selecting/opening new subwindows) the corresponding chapter is shown.
The chapter is shown in a separate window, that can be sized, positioned and closed as usual.
The help window opens automatically with the start of mz3Tool, but can be manually switched to “always off” or “always on” (in the
Settings - Basic Settings).
- Better support of old Browsers
This helps to support e.g. Safari 9, the highest version available for iPad2 and some older OSx versions.
- Watermark-Area in Demo version reduced
The watermark layer started in the top-left most corner and covered the drag range and sound buttons located on top of a page.
This blocked mouse clicks and a page could not be flipped or a sound started/paused.
The “overwrite” switch in ‘Add Page Image’ only was used locally but not when the file was about to be copied.
New Page Images did not overwrite existing “pages”; which made an update only possible after the respective page image was deleted manually.