This action might not be possible to undo. Are you sure you want to continue?
The following notes describe differences in the appearance or behavior of certain objects in native ToolBook when compared to these same objects displayed in a Web browser after export to HTML using the ToolBook Web Specialist. Since the browsers have certain limitations, it is not always possible for each ToolBook object to have precisely the same look and behavior in different browsers. These differences are listed below.
Actions for randomized answers
Actions created for answers to randomized multiple-choice questions do not behave the same in ToolBook and an exported HTML application. When an action for an event (such as the On click event) is created for a specific answer to a multiple choice answer field or button, the action will not remain associated with the event after the question is randomized in an HTML application.
Assigning click events to a group
The On click and On double-click events are not supported for editable fields and combo boxes in ToolBook. However, the On click and On double-click events are supported for editable fields and combo boxes in HTML. This difference is apparent when On click or On double-click events are defined for a group that contains editable fields or combo boxes. In ToolBook, when the user clicks on the editable field or combo box in the group nothing happens, but in HTML, the On click or On double-click events for the group execute when the combo box or editable field is clicked.
Feedback message does not stop action sequence
In HTML, when a response to a question triggers a popup feedback message, the processing of any subsequent statements in the action sequence continues. In ToolBook, the processing of an action sequence with a feedback message is stopped until the user dismisses the pop-up message.
Fill color is not supported for draw objects in Actions Editor
In ToolBook, draw objects such as rectangles and circles can be created with the tool palette. You can set the color inside of these objects before exporting to HTML and the object will appear as expected in a browser after export. However, if you try to use the Actions Editor to set the rgbFill property of a draw object, this property is not available since all draw objects are exported as graphics and the fill color cannot be set after export.
In a list box or combo box, setting the selectedItemText property allows you to select a specific line of text. The value stored in this property is case-sensitive in HTML but not in ToolBook. For example, if you set the selectedItemText property to "triplet" (all lowercase) in an HTML application, an existing line of text that says "Triplet" will not be selected because the property value is case-sensitive in HTML.
On load book event sent when new page pops up
If you have a button with a hyperlink that pops up a new page, after export to HTML clicking the button in a Web browser causes the pop-up page to generate an On load book event. In the HTML 1
version of the book, a pop-up hyperlink is actually opening another instance of the HTML runtime and loading the book in that instance. The two HTML instances are totally separate, whereas in native ToolBook there is only a single instance of the runtime open when you display a new page in a popup window.
Order of events
Actions within an action sequence will always execute in the same order regardless of the browser in use. However, the order of events is not always consistent between ToolBook and a specific browser, so authors should never rely on an exact order of events. For example, when you click on a list box object in ToolBook, this is the sequence of events for a click that causes a property change: trigger click select (if an item is selected) property change In a browser, after exporting to HTML the order is: click select (if an item is selected) property change trigger
Assigning the action named “On media complete” to a path animation causes slightly different behavior. In ToolBook, the animation stops, returns to the start, and then the complete event occurs. In HTML, the animation stops, the complete event occurs, and then the animation returns to its start.
Pop-up text boxes
Timed Delay actions
You cannot use a Timed Delay action within a loop or an “if” condition in an action sequence, if you plan to export to HTML. The delay will function in ToolBook but is ignored in HTML.
Universal Media Player and periodic time markers
Periodic time markers allow developers to check the status of the media at regular (but not guaranteed to be precise) time intervals. In ToolBook, the timing event is fired at regular intervals, but in HTML the timing events could be at any interval and might even stop if the movie stops at a frame while waiting for user input. For media that uses frames, such as a Flash movie file, the timing unit is in milliseconds because frames are not "regular" - frames might be set at different rates at different parts of the movie, and the movie can stop at any point.
Graphic / Images
The following three styles are not supported in HTML: tile from center (tile from upper left is substituted) checkerboard 3 (checkerboard 1 is substituted) checkerboard 4 (checkerboard 2 is substituted)
When a computer is running with a 16-bit color display driver, a graphic that uses a chromakey color may not export to HTML properly, since the export is dependent on the video driver mapping colors correctly between 16-bit and 24-bit.
Displaying a path animation
In ToolBook an object can have a defined path animation that includes resizing the object. After exporting to HTML, playing the animation in a browser will not display any resizing of the object.
Embedded images in text fields
A text field or record field that is editable cannot contain an embedded image in an HTML application.
If a bitmap is inserted into a text object that is set to single-select list box or scrolling, it will display in ToolBook. In HTML, the bitmap does not appear.
"Use Windows colors" option
A HTML application running in a browser cannot determine the system colors set on the computer of the end user. When the "Use Windows colors" option is checked in ToolBook, the export to HTML code checks the author's computer for the current settings of the Windows button face and stroke colors and uses these values in the HTML files. The colors displayed in ToolBook (for example, a background pattern) may not be the same as the colors seen in HTML. This difference in color values applies to the options labeled "Use standard Windows colors" and "Use dialog box color" found in the properties dialog boxes for objects such as buttons, text fields, draw objects, and stages.
Image not Centered if “stretch to fit” Unchecked
If the “stretch to fit” option is not selected in an Image Object, and the Image Object is larger than the graphic it is displaying, then the graphic will be displayed in the upper left corner of the image object, rather than in the center.
If a hyperlink is specified as going back to the previously displayed page, in an HTML application the link is not functional if the previously displayed page is in another book. In other words, if a hyperlink to a page in another book is triggered, and that page has an object with a hyperlink to go back to wherever you came from, clicking that object will have no effect. If a hyperlink specifies going to a page in another book with a transition effect, the HTML form of the hyperlink does not use the transition. When such a link is triggered, the page in the other book is actually displayed in a new browser window and the one showing the first book is closed.
Scores tracked through AICC/SCORM are not reported
If a book contains a hyperlink that closes the current book and opens another book, and both books are exported with AICC or SCORM support, student scores will not be tracked when running the books from an AICC or SCORM LMS server. To take advantage of the score tracking feature in an AICC- or SCORM-compliant learning management system (LMS), set up each one as a separate lesson in the LMS.
Displaying multiple Popup Universal Media Players on a page
You can have more than one Popup Universal Media Player (UMP) on a page. In native ToolBook, only one Popup UMP can play at a time. If a user tries to play media in two different Popup UMPs at the same time, ToolBook will close the media file currently playing and will then start playing the second media file. After export to HTML, two separate Popup UMPs can play simultaneously. However, if one Popup UMP is triggered in response to question feedback, in HTML the Popup that plays the media feedback file will close when another Popup UMP is triggered.
Displaying multiple Universal Media Players that overlap
Placing one Universal Media Player on top of another Universal Media Player will not simultaneously display the media files properly. You can, however, place a Popup Universal Media Player on top of another Popup Universal Media Player and achieve the intended result when each is set to hide automatically after the media file has finished playing.
Media player hotwords that open a second window to display the media (such as playing a video file) show a Minimize, Maximize and Close button in the new browser window. In ToolBook, the user clicks a media player hotword a second time to close the media window, but in HTML users must close the media window by using the Close button on the media window. In HTML, applying a second click to the media player hotword causes the media to stop playing and sets the focus to the HTML window, which layers the media window under the HTML window.
Media clip start and end points
When start and end points for a clip are set in ToolBook, after export to HTML these settings are disregarded and entire source file is played. To work around this issue, create a new media file that contains only the portions of media that you want to display.
Video Synchronizer text color slightly different
The behavior of the Video Synchronizer is the same in ToolBook and an exported HTML application; however, the appearance of the text color differs. In ToolBook, the strokeColor of the text is blue; after export to HTML the browser displays the text by inverting the color of the text and the area of the page beneath the text (reverse video effect).
When using a separate book containing glossary terms, in HTML the popup window is a new browser window sized to the page being displayed. If the glossary is part of the existing book, HTML shows a normal popup window similar to ToolBook. If a separate glossary book is used (glossary.tbk or the book entered in the Glossary file name field), the book must be exported to the same project directory as the main book.
Browser window sized for biggest background
When using the Web Specialist to export a book, the Start page section allows you to select whether or not you wish to have a launch page created automatically by the Web Specialist. If you select either “Automatically create an HTML page” or “Use a custom HTML page”, and the book you are exporting includes backgrounds of different sizes, then the HTML window will be the size of the largest background. In HTML, the size of the window cannot change once it is created. If you choose the option labeled “Do not use an HTML launch page” in the Web Specialist, the resulting HTML window is not a fixed size and the window can be manually resized. 4
A button with a pushbutton border style can be set to be disabled in the Properties for Button dialog box on the Behavior tab. In HTML, a disabled button appears disabled, and behaves disabled, but the hand cursor shows when the mouse moves over it.
Draw object boundary extends after triggering an action
If you have used the Actions Editor to assign actions to the On click event of a draw object, the clickable area of the draw object may be larger after export to HTML. In a browser, the full rectangle that contains the draw object becomes the clickable area, rather than the draw object itself. For example, if the draw object is a circle, the entire invisible rectangle containing the circle is clickable, not just the visible circle.
A book may be set to display full-screen at reader level (on the Window tab of the Properties for Book dialog). When such a book is exported to HTML, the browser may display the book within a fullscreen window. Mozilla-class browsers, and Internet Explorer in Windows XP Service Pack 2, require a browser window to have a frame, title, and status bar. If you design your pages to fill the screen at a certain resolution, a user with one of these browsers may need to scroll to see the entire page. There is a way to overcome this in Internet Explorer via an end-user configurable setting, as described in this Knowledgebase article: P661.
A label button with a fill color set to a color other than white has a slightly different appearance after export to HTML. The fill color for a label button in native ToolBook appears only behind the caption of the button (regardless of the size of the button). After export to HTML, a label button with a fill color other than white displays the fill color throughout the enclosed bounds of the button. This occurs even when the label button is set to be transparent. Setting the enabled or disabled property of a label button is not supported in HTML.
Text field objects with the field style property set to single-select list box or multi-select list box will appear in a browser with a gray frame and scrollbar.
Text translated to HTML
During the HTML export process, text is translated to HTML and standard HTML rules are applied. For example, tabs are displayed as a single space.
Sometimes a browser will not properly display very small objects. An object that is less than 16 by 16 pixels may display in an unexpected manner.
Definable Arrange Objects question
In the Questions category of the Catalog, the Definable Arrange Objects question requires one additional step when you plan to export a book to HTML. The question button that you drag from the Catalog must be highest in the layer order to allow the draggable answer objects to function properly in a browser. To achieve the proper layer order, in ToolBook prepare the answers for this question. After adding all of the answer objects, select the button with the Definable Arrange Objects caption. From the Draw menu, point to Layer, and then select Bring to Front. If you set immediate feedback for an answer to a Definable Arrange Objects question, after export to HTML the feedback option labeled "Correctly placed objects" works properly. The following two 5
feedback options display the feedback for the correct answers only (not the incorrect answers): "Every object moved" and "Incorrectly placed objects".
Feedback text does not display CRLF entries after export
You can enter text that will automatically display in response to an answer selected by a student in the Properties for Question dialog box. Question feedback text can have line feed (LF) and carriage return line feed (CRLF) entries in native ToolBook, but these line breaks do not appear after the application is exported to HTML.
Position of dropped object
In native ToolBook, a Drag Object question with the option "Reject unrecognized answers" selected will remain where it is dropped. After export to HTML, dragging the object and dropping it where there are no objects causes the drag object to snap back to its original position.
Weight of scored questions in a randomized Quiz Book
In the Book Wizard, the Book Type page offers the option to create a Quiz Book. Every question in a randomized Quiz Book deployed to HTML must have the same weight in order for scoring to work properly. The minimum and maximum point value for each question has to be configured the same way for all questions in a randomized Quiz Book.
In the Quiz Summary, the slider question displays the correct answer differently in HTML and native ToolBook, as it stores/constructs the correct answer differently for the two deployment methods. In native ToolBook, the correct answer for a slider type question is displayed in the form “Value > 50” , whereas in HTML, it might be displayed in the form “From 51 to 100” (assuming the maximum value is 100).
During export to HTML, a blank item is added to the top of the list of items in any Catalog object that includes a combo box (such as the Jump To URL object in the Navigation category of the Catalog). The user must click the drop-down arrow to view and select one of the items in the list. The blank line is necessary because a previously highlighted item cannot be selected in HTML combo boxes by a mouse click: no action occurs. With the blank line being the first item in the combo box, it appears that no item is selected. To select an item that is highlighted, the user must first click on the blank line, and then click on the desired item. In HTML, pressing the Enter key when an item is already highlighted in a combo box is not supported.
Text field objects with the field style property set to single-select list box or multi-select list box will appear in a browser with a gray frame and scrollbar. Font characteristics such as bold and italic are not supported. The height of the list box is based on the font. In list boxes, hotwords are supported in native ToolBook, but they are not supported in HTML.
Scrolling in a text field may differ
In ToolBook, when a user scrolls a text field the scroll movement is line by line. When viewing an exported HTML application in a browser, scrolling in a text field occurs in pixels. During the export of a ToolBook application to HTML, the font size of the field is used to determine how many pixels to scroll. If a field has text lines of different heights (due to the use of different font sizes), scrolling will not work in exactly the same fashion that it works in ToolBook.
The default hotword properties are set on the Draw tab in the Properties for Book dialog box. In HTML, using the hotword styles of Dotted or Frame will display the same look as the Underline setting. Using the style setting of None will cause the hotword to appear in HTML with the same setting as the color value.
Issues specific to Internet Explorer
Draw transparent option deactivates click action for text field
In the Properties for Text Field dialog box, the Draw tab includes an option called "Draw transparent." If this option is selected, and an action sequence for the "On click" event has been added to a text field, in HTML the action will execute only when the user clicks on the portion of the field that contains text. To work around this issue, overlay the text field with a transparent button or rectangle, and place the click event actions on that object.
ToolTips do not display for some text objects
ToolTips that are assigned to list boxes or combo boxes will not display in Internet Explorer
Issues specific to the Firefox browser
Windows Media Player
In order for Firefox to be able to utilize a Windows Media Player, the correct player component has to be installed. There are two different Windows Media Player plug-ins which work within Firefox. One is installed by default when installing the Windows Media Player and this plug-in (npdsplay.dll), however it is not usable by ToolBook because it is not a scriptable plug-in. Microsoft has recently developed another plug-in (np-mswmp.dll) which is scriptable, but it is not installed by the Windows Media Player install. This plug-in is linked from the Firefox plug-ins page, and is also directly downloadable from here: http://port25.technet.com/pages/windows-media-player-firefox-plugin-download.aspx Note that this plug-in only supports Windows XP and Windows Vista.
Mac is not supported with Firefox browser
The Firefox browser support for ToolBook does not include the Macintosh version. Use the Safari browser on the Mac.
QuickTime in Firefox doesn’t play on local machine
QuickTime files within Firefox will only play when the files are moved to a web server.
Issues specific to the Safari browser
Neuron doesn't launch in Safari
The Neuron plug-in does not work within the Safari browser on the PC or the Mac.
Safari changes default Universal Media Player selection to QuickTime
When you choose the Windows Media Player to be used within the Universal Media Player to play your AVI, MP3 or WAV files, the media player actually used will be the QuickTime player when displayed within the Safari browser under Windows, if the Windows Media Player plug-in is not installed. 7
Safari under OS X Supports QuickTime Media Only
When deploying media such as MP3 files that can be played on either the Windows Media Player or the QuickTime player, if the target browser is Safari on the Mac, QuickTime must be specified. To do this, open the Properties for the Universal Media Player, go to the Advanced tab, and select the QuickTime player.
"Scrolling" field doesn't scroll in Safari if field is too short to display scroll bar arrows
“Scrolling” text fields may lose their ability to scroll when viewed on Safari on a PC or Mac if the height of the field is too short (approximately 3 text lines). However, scrolling through the list can be done with the mouse wheel if available.
Voice Recordings under Safari
To play Voice Recordings under Safari, the recording must be published to MP3, and the QuickTime plug-in must be installed to Safari on the client machine. For more information on publishing Voice Recordings to MP3, please see Knowledge Base article P3018.
Issues specific to the Safari iPhone browser
Voice Recordings don't play on the iPhone
Voice Recordings don’t play in Safari on the iPhone. Voice Recordings are converted to .AU files during the web export process and the iPhone cannot play these .AU files. The recommended solution is to not use the Voice Recording feature and instead use a Universal Media Player to play the audio file. For each page where a voice recording is desired, place a Universal Media Player on the page and configure it to be hidden. The iPhone will still show a play button where the Universal Media Player is, so resize and position the player as if it were a Play button. The media player will play in full screen, and then close when finished. Although there is a way to get ToolBook to convert a Voice Recording to an MP3 file instead of an AU file (see Knowledge Base article P3018), the iPhone is still unable to play it.
iPhone supports only QuickTime
The iPhone currently only supports QuickTime. Universal Media Players should be configured to use the QuickTime Player. This can be specified on the Advanced tab of the properties for the UMP dialog box.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.