Modifications from Release 3.0 to Release 3.0.p1

Improvements

The following features, properties and modules have been improved in LECTURNITY 3.0.p1

• Vista support: LECTURNITY 3.0.p1 supports the operating system Windows Vista, i.e. LECTURNITY can now be installed and used under Vista.
  
  
• Support of PowerPoint 2007: LECTURNITY 3.0.p1 supports PowerPoint 2007. As with PowerPoint 2003 or earlier versions, documents created with PowerPoint 2007 can be imported into LECTURNITY with the build-in functionality in the LECTURNITY Assistant as well as using LECTURNITY’s plug-in functionality in PowerPoint itself. New object types in PowerPoint 2007 that cannot be displayed as a combination of the object types available in LECTURNITY are imported as images.
  
  
• Enhanced SLIDESTAR support: LECTURNITY documents can now be published with the current SLIDESTAR design and directly uploaded and inserted into a SLIDESTAR system. The upload and insertion process is user-authenticated based on the user’s SLIDESTAR account. After upload and insertion, the document appears under the user’s account in the SLIDESTAR section “My Slideware” for further processing. Using LECTURNITY’s profiles one click is sufficient to push a newly created document onto a SLIDESTAR.
  
  
• Improved display quality with freehand drawings (especially handwriting): The display quality of freehand drawings (created with the predefined pens or the “Freehand” tool in the LECTURNITY Assistant) is improved in LECTURNITY 3.0.p1. In comparison to LECTURNITY 3.0 the freehand drawings appear smoother in the Editor and all of LECTURNITY’s target formats
  
  
• Support of Firefox 3: Since the ActiveX plug-in does not work correctly in Firefox 3, which in turn is necessary to control the Windows Media Player plug-in, Firefox 3 cannot be supported in LECTURNITY 3.0 for LECTURNITY Windows Media Documents. LECTURNITY 3.0.p1 supports Microsoft’s special Windows Media Player plug-in for Firefox which itself works without ActiveX plug-in. Therefore, LECTURNITY Windows Media Documents can be replayed in Firefox 3 with LECTURNITY 3.0.p1.
  
  
• Frozen page objects (customizable): There is a new setting “Freeze loaded page objects” in the LECTURNITY Assistant’s “Edit” menu. If activated, which is the default setting, it ensures that page objects loaded or imported together with a document cannot erroneously be modified, e.g., not repositioned. This is especially interesting in a full screen presentation in which the user does not want to erroneously modify or reposition the objects of imported PowerPoint slides. However, page objects newly created in the Assistant can always be modified, even with the setting activated.
  
  
• Improved visualization of pause mode: In LECTURNITY 3.0 the activated recording pause in the Assistant is only indicated and therefore perceivable by the user through the non-advancing recording time, which itself is not visible in the full screen mode (cmp. improvement below). In LECTURNITY 3.0.p1 an activated pause is additionally visualized through a flashing pause button in the toolbar “Recording”.
  
  
• Extended colour customization in Flash design template: In addition to the text and background colour of the design template of LECTURNITY Flash Documents, LECTURNITY 3.0.p1 also supports the colour customization of the template’s control components.
  
  
• Preloader for Flash Documents: The loading progress bar of LECTURNITY Flash Documents informs the user about the loading status of the document when accessing it through the Web. The progress bar also indicates that the parts of the document which are temporally beyond the displayed loading progress level can not yet be accessed nor replayed. In LECTURNITY 3.0, the loading progress bar does not appear and can therefore not inform the user about the loading progress before the data for the Web player’s user interface itself is loaded. Depending on the network connection this might take several seconds in which the user receives no visual feedback at all. In LECTURNITY 3.0.p1, the new Preloader informs the user about the loading status before the player’s user interface appears, so that there is no time period in which the user receives no feedback, therefore minimising confusion.
  
  
• Combined actions for testing and interaction: Actions of question-, test- or interactive components can now be freely combined with the action “Start replay” or “Stop replay” in the Editor. This means, the user can combine an action, such as “Open URL …” as a result of a wrong answer to a question, with a stop or start of the replay of the document.
  
  
• Recording time in full screen mode: In LECTURNITY 3.0 the status bar of the Assistant is not displayed in the Full Screen Mode. Therefore, information displayed in the status bar, which might be important during presentation and recording, such as the recording time, is not available to the user. In LECTURNITY 3.0.p1 the status bar is also displayed in the Fullscreen Mode.
  
  
• Customizable appearance of SmartBoard support dialog: If a SmartBoard device is attached to the system, the Assistant shows a dialog after the start-up, in which the user is asked, if the SmartBoard pens should be supported. Whereas this dialog always appears in LECTURNITY 3.0, the dialog’s appearance can be customized in LECTURNITY 3.0.p1 within the “View” menu. If the appearance of this dialog is deactivated, the support of the SmartBoard pens is automatically activated during start-up.
  
  
• Customizable streaming protocol for RealMedia, Windows Media, and Flash: In LECTURNITY 3.0 the user cannot change the protocol type used for the streaming of RealMedia, Windows Media, or Flash. The standard protocol for the respective streaming technology is predefined. In LECTURNITY 3.0.p1 the user can modify this streaming protocol for all provided technologies directly in the Publisher.
  
  
• Tool “Insert New Page” also in the Presentation Bar: In LECTURNITY 3.0 the user can only add the tool “Insert New Page” by drag&drop of the corresponding button from the toolbar “Standard” into the toolbar “Presentation” during the “Customize” mode of the toolbars. In LECTURNITY 3.0.p1 this tool is also directly available as function to add in the “Add or Remove Buttons” submenu of the toolbar “Presentation” as with most other tools of the Assistant.
  
  
  

Bug fixes

The following bugs of LECTURNITY 3.0 are fixed in LECTURNITY 3.0.p1:

PowerPoint Import

• Overlapping text when using different styles in one line in certain situations: If a text line on a PowerPoint slide includes different text styles, such as bold, standard, and italic, in certain situations, the corresponding text blocks are not positioned correctly after the import into LECTURNITY. This means, that certain text blocks can overlap or that the gap between adjacent text blocks can be too long.
  
  
• Misleading error messages “Error: 21” and “Error: 29” in special cases: If the PowerPoint filename or the filename selected by the user for the resulting LECTURNITY Source Document includes a combination of blank characters and dots before the file extension, the misleading error messages “Error: 21” and “Error: 29” appear. As a consequence, the import is interrupted and the document is not opened in the Assistant.
  
  
• Misleading error message “Error: 23” in very rare situations: If the Assistant’s build-in PowerPoint import in the “File” menu is used, the message “Error: 23” appears in very rare, unpredictable situations. As a consequence, the PowerPoint document in not correctly imported and displayed in the Assistant. This error never occurs when using LECTURNITY’s import plug-in in PowerPoint, i.e. “Open in LECTURNITY Assistant” or “Save as LECTURNITY Source Document”.
  
  
• Disappearing progress bar without import completed: If a PowerPoint presentation of more than 70 pages is imported, the progress displayed is already “99%”, and the import of an individual slide requires more than one second, the progress bar erroneously disappears and the import is interrupted. As a consequence, the PowerPoint document is not correctly imported.
  
  
• Hyperlinks in animated objects not supported: If an object on a PowerPoint slide includes a hyperlink and is at the same time bound to an animation effect, the hyperlink can erroneously not be activated in the Assistant after the import.
  
  

Assistant

• Record control components erroneously not enabled during Pure Screengrabbing: During the recording of a Pure Screengrabbing Document in Assistant the GUI components “Start”, “Stop”, and “Pause” in the toolbar “Recording” for the recording control are erroneously disabled.
  
  
• Freehand drawings not completely removable in certain situations: Page objects of freehand drawings (created with the predefined pens or the “Freehand” tool in the Assistant) cannot always be completely removed using the Assistant’s “Delete” tool. In these cases, parts of the polylines erroneously remain displayed on the page and cannot be reselected or subsequently removed.
  
  
• Assistant window redisplayed in wrong resolution after end of Screengrabbing: If a user maximizes the Assistant window before the start of Screengrabbing together with the activated setting “Minimize Assistant when starting”, then the Assistant window is redisplayed after the end of Screengrabbing, but not maximized as expected. Instead, the Assistant window is erroneously displayed with a resolution of 800x600 pixels.
  
  
• Wrong undo of object repositioning: If a user performs a certain editing action on a page and afterwards repositions an object on this page, an undo action results in an undo of the first editing action and not in the repositioning of the object back to its recent position.
  
  
• Font “Arial” used instead of “Stone”: If text objects (especially imported from PowerPoint) use the font “Stone”, the Assistant erroneously displays these text objects with the font “Arial”.
  
  
• Wrong button images for the text style functions “Bold” and “Italic”: The letters included in the button images for the text style functions “Bold” and “Italic” in the Assistant’s toolbar “Format”, are not “B” and “I” as expected, but “F” and “K” for the corresponding German words of these text styles.
  
  
• Wrong display of objects with exit effects in PowerPoint:  If “Exit” effects (fade out, disappear, fly out, etc.) are bound to objects (text, images, shapes, etc.) in PowerPoint, these objects are sometimes not correctly displayed or removed from the page after import of the PowerPoint document in the Assistant.
  
  

Editor

• Wrong error message when opening Pure Screengrabbing Documents in rare situations: In very rare situations, the opening of a Pure Screengrabbing Document in the Editor erroneously results in the error message “Building the preview failed. The following error code was generated: 0x80070057. ‘One or more arguments are invalid.’” This error message is wrong, since the document can be used afterwards without any problems in the Editor.
  
  
• Font “Arial” used instead of “Stone”: If text objects (especially imported from PowerPoint) use the font “Stone”, the Editor erroneously displays these text objects with the font “Arial”.
  
  
• Incomplete list of pages or target marks for jump actions due to stream view zoom factor:  If a document includes several pages and/or target marks and the zoom factor of the stream view is not “Complete document”, then the list of possible pages and/or target marks available for an action, such as “Jump to page …” or “Jump to target mark”, is erroneously limited to the pages and/or target marks in the zoom selection of the stream view.
  
  
• Wrong button images for the text style functions “Bold” and “Italic”: The letters included in the button images for the functions “Bold” and “Italic” in the Assistant’s toolbar “Format”, are not “B” and “I” as expected, but “F” and “K” for the corresponding German words of these text styles.
  
  

Publisher

• Imprecise Pointer positioning with certain page resolutions: If the user chooses a page resolution larger or smaller than “Standard” in the Publisher, then the Pointer object, if used in this document, is erroneously displayed a few pixels left or right of the correct position.
  
  
• Target directory setting for profiles ignored: If the user modifies the setting “Target Directory” in the profile settings and therefore does not use the default target directory, all documents published with this profile are erroneously stored in the default target directory anyway.
  
  
• Wrong snap-in and repositioning behaviour of images in Drag&Drop Questions: If the movable images of a Drag&Drop Question are much wider than they are high and the Drag&Drop target areas are ordered vertically, then the following undesired effects appear: the first image snaps in a wrong page area not necessarily corresponding with the visualized target area; the repositioning of all other images erroneously repositions the first image as well.
  
  
• Wrong behaviour on deactivated test feedback: If a document contains a single question and the “Answering Feedback” of the corresponding test is deactivated, the action bound to the event “If answer is correct” of the question (for the last test question usually not executed) is erroneously executed anyway and the feedback for the correctly answered question is displayed for a very short time span only.
  
  
• Replay error with clips displayed in the video area: If a document contains video or Screengrabbing clips and “Clips in video area” in the Publisher’s advanced settings is activated, then the replay of the corresponding document in the Web browsers fails. The replay button is disabled and the Internet Explorer, as an example, displays the message “Error on page”.
  
  
• Wrong success status passed from SCORM-published documents in certain situations: If a RealMedia Document published with SCORM support is accessed in a SCORM-compliant Learning Management System (LMS), the success status (mandatory value for SCORM communication) is sometimes erroneously set to “not passed” in the LMS before any question in the document is answered by the user.
  
  
• Misleading error message together with clips in very small resolutions:  If a user tries to publish a document including video or Screengrabbing clips with a resolution smaller than 32x32 pixels to a RealMedia Document, the Publisher displays the misleading error message “Encoding of the data stream failed! Possible cause: Disk is full. A RealMedia file already exists which has been opened and therefore can not be overwritten.". As a consequence, the publishing process is interrupted and the RealMedia Document is not correctly created.
  
  
• Incorrect replay of Pure Screengrabbing Documents: If a Pure Screengrabbing Document is published as a RealMedia Document, the Screengrabbing clip is not displayed during replay. A black screen region is displayed instead.
  
  
• Wrong and bookmarking together with SCORM publishing in certain situations: If a Windows Media Document published with SCORM support is accessed in a SCORM-compliant Learning Management System (LMS), the bookmarking is sometimes not correctly stored in the LMS. As a consequence of a wrong or missing bookmarking, the learner cannot resume an interrupted learning session of this document, since the last visited position within the document and maybe results of already answered questions are no longer available.
  
  
• Imprecise Pointer positioning with certain page resolutions: If the user chooses a page resolution larger or smaller than “Standard” in the Publisher, then the Pointer object, if used in this document, is erroneously displayed a few pixels left or right of the correct position.
  
  
• Target directory setting for profiles ignored: If the user modifies the setting “Target Directory” in the profile settings and therefore does not use the default target directory, all documents published with this profile are erroneously stored in the default target directory anyway.
  
  
• Setting “Use extended suffix (.wmv or .wma)” ignored in profiles: If the user activates the setting “Use extended suffix (.wmv or .wma)” of the advanced Windows Media settings for a profile, all Windows Media files of documents published with this profile are erroneously stored with the file extension “.wm” anyway.
  
  
• Wrong snap-in and repositioning behaviour of images in Drag&Drop Questions: If the movable images of a Drag&Drop Question are much wider than they are high and the Drag&Drop target areas are ordered vertically, then the following undesired effects appear: the first image snaps in a wrong page area not necessarily corresponding with the visualized target area; the repositioning of all other images erroneously repositions the first image as well.
  
  
• Wrong behaviour on deactivated test feedback: If a document contains a single question and the “Answering Feedback” of the corresponding test is deactivated, the action bound to the event “If answer is correct” of the question (for the last test question usually not executed) is erroneously executed anyway and the feedback for the correctly answered question is displayed for a very short time span only.
  
  
• Wrong positioning of Pointer object together with hidden Document Structure: If the user customizes the design template “Standard design” for Windows Media Documents in the Publisher, so that the Document Structure is hidden during replay, the Pointer object, if used in this document, is displayed at the wrong position. The same behaviour appears when using the design templates “Player design without document structure” or “Standard design: Popup window/Full screen” for Windows Media Documents.
  
  
• Wrong success status passed from SCORM-published documents in certain situations: If a Windows Media Document published with SCORM support is accessed in a SCORM-compliant Learning Management System (LMS), the success status (mandatory value for SCORM communication) is sometimes erroneously set to “not passed” in the LMS before any question in the document is answered by the user.
  
  
• Replay error with clips displayed in the video area: If a document contains video or Screengrabbing clips and “Clips in video area” in the Publisher’s advanced settings is activated, then the replay of the corresponding document in the Web browsers fails. The replay button is disabled and the Internet Explorer, as an example, displays the message “Error on page”.
  
  
• Wrong “session time” and bookmarking together with SCORM publishing in certain situations: If a Flash Document published with SCORM support is accessed in a SCORM-compliant Learning Management System (LMS), the “session time” of the learner’s session as well as the document’s bookmarking is sometimes not correctly stored in the LMS. As a consequence of a wrong or missing bookmarking, the learner cannot resume an interrupted learning session of this document, since the last visited position within the document and maybe results of already answered questions are no longer available.
  
  
• Target directory setting for profiles ignored: If the user modifies the setting “Target Directory” in the profile settings and therefore does not use the default target directory, all documents published with this profile are erroneously stored in the default target directory anyway.
  
  
• No user feedback about problems caused by publishing a document twice:  If a user publishes a document to a Flash document and directly opens this Flash document in a Web browser, then a second publishing of the same document into a Flash document cannot be performed by the Publisher, since the files of the first document are still in use and can therefore not be overwritten. For that reason, the Publisher stops processing on the second publishing, but provides no further feedback and no error message to the user.
  
  
• No audio replay together with clips in certain situations: If a document contains video or Screengrabbing clips, but no accompanying video, and is published as Flash Document with the setting “Clips on top of the pages” activated, then there is no audio output during the replay of the Flash Document.
  
  
• Underlined style in text not displayed: Underlined text in documents is erroneously not displayed as being underlined after the publishing to a Flash Document.
  
  
• Wrong snap-in and repositioning behaviour of images in Drag&Drop Questions: If the movable images of a Drag&Drop Question are much wider than they are high and the Drag&Drop target areas are ordered vertically, then the following undesired effects appear: the first image snaps in a wrong page area not necessarily corresponding with the visualized target area; the repositioning of all other images erroneously repositions the first image as well.
  
  
• Wrong behaviour on deactivated test feedback: If a document contains a single question and the “Answering Feedback” of the corresponding test is deactivated, the action bound to the event “If answer is correct” of the question (for the last test question usually not executed) is erroneously executed anyway and the feedback for the correctly answered question is displayed for a very short time span only.
  
  
• Settings concerning Standard Navigation ignored: If the user modifies the settings concerning Standard Navigation in the extended settings of the Publisher for Flash Documents, these modifications are ignored. Particularly, the Standard Navigation in Flash Documents cannot be disabled or hidden.
  
  
• Incomplete display of images together with non-default Flash movie resolutions: If the user chooses another resolution for the Flash movie than the default in the extended settings for Flash Documents in the Publisher, images used in the document are not displayed completely during the replay of the Flash Document. One or two pixel lines on the right and/or bottom border can be missing.
  
  
• Wrong success status passed from SCORM-published documents in certain situations: If a Flash Document published with SCORM support is accessed in a SCORM-compliant Learning Management System (LMS), the success status (mandatory value for SCORM communication) is sometimes erroneously set to “not passed” in the LMS before any question in the document is answered by the user.
  
  
• Wrong error message “Temporary file is missing” in certain situations: If a document contains questions and buttons, the creation of the corresponding Flash Document in the Publisher erroneously results in the error message “Temporary file is missing” in certain situations. As a consequence, the creation of the Flash Document cannot be completed.
  
  
• Uncontrolled termination in rare situations:  If a document includes lines of width or height “0” (created by mistake and also not perceivable by the user) the creation of the corresponding Flash Documents results in an uncontrolled termination of the Publisher. As a consequence, the Publisher windows disappears and the Flash Document is not created.
  
  
• Error message during creation together with documents displaying clips in the video area in certain situations: If a document contains at least one clip and the clips starts after replay time “214 seconds”, the creation of the corresponding Flash Document results in the error message “An error occurred during the following task: Converting video”. As a consequence, the creation of the Flash Document cannot be completed.

Player

• Wrong snap-in and repositioning behaviour of images in Drag&Drop Questions: If the movable images of a Drag&Drop Question are much wider than they are high and the Drag&Drop target areas are ordered vertically, then the following undesired effects appear: the first image snaps in a wrong page area not necessarily corresponding with the visualized target area; the repositioning of all other images erroneously repositions the first image as well.

LECTURNITY 3.0: Release Notes

Modifications from Release 2.0.p4 to Release 3.0

New Features

The following new functionalities have been introduced in LECTURNITY 3.0:

• Server transfer functionality for a rounded publishing process: The LECTURNITY 3.0 Publisher, in addition to the existing transfer copy to connected network drives of (maybe remote) servers already available in LECTURNITY 2.0.p4, offers a real upload functionality for all target formats and different server types (streaming server, Web server, file server, Podcast server, etc.). The server transfer, especially the server upload, automatically starts after the creation of the target document. In order to cover arbitrary application areas, the Publisher provides the network services “FTP”, “SCP”, and “SFTP” for the data transfer of the upload as well as authenticated server access. For publishing variants in which more than one server is necessary, such as with Streaming or Podcasts, the Publisher simultaneously distributes the document to the required destinations. The LECTURNITY publishing process now therefore consists of document creation in the selected target format and the optional transfer (upload) to remote servers.
  
  
• Profiles for a much more convenient publishing process: Publishing a document in LECTURNITY is “the” step within the whole content creation process which, in comparison to the other steps (recording, editing, etc.), requires a little bit more technical understanding on the one hand and on the other hand a little bit more effort to customize all the different settings. The reason is that the publishing process provides functionality for arbitrary ways of electronic distribution which is inherently technical, such as network access, streaming, or Web-based document exchange (SCORM). Therefore, technical settings such as video resolutions, audio sample rates, bandwidth, compression, etc. are necessary and have to be configured for the publishing process. In LECTURNITY 2.0.p4 the user has to customize all these settings for every publishing process once again. There is neither the option to save the settings once set nor to switch between setting sets for different application scenarios. For users who routinely publish documents, several a day perhaps, this may be a time-consuming step. For users who do not have the required technical understanding or for those who simply do not know what the real values for the different settings in the current IT infrastructure should be (since they are not the administrators), this might be a difficult step.
  LECTURNITY 3.0 therefore offers profiles for publishing. A profile covers all the necessary settings of the publishing process, including those for server transfer (upload). That means, one document is published during each use of a profile. Once a profile is created and activated, a single click in Publisher is sufficient to create a document in the target format and to transfer it to a server. Just another three clicks are required before publishing in order to change the current profile. The new Profile Manager in the Publisher allows the user to create new profiles and to administrate existing ones (edit, rename, delete, activate, etc.). Using the import/export function, profiles can be transferred from or to other LECTURNITY systems in order to ensure consistent, uniform, or standardised publishing in a work group or department. In addition, this is supported by the fact that profiles created with administrator rights cannot be edited by users without those rights.
• 
  
  

Improvements

The following features, properties and modules have been improved in LECTURNITY 3.0:

• Improved performance with freehand drawings (especially handwriting): The usage of the predefined pen tools and the Freehand tool in LECTURNTIY 2.0.p4 can result in irritating effects, which in turn can influence the display quality of sequences of connected lines (polylines) or handwriting in general. The performance of this functionality may lead to the loss of individual sampling values of a mouse movement or the movement of a pen-based input device and therewith to displayed polylines which do not exactly correspond to the round trace with the input devices. It may also lead to a slightly delayed display of polylines in comparison to the corresponding current mouse pointer position. Especially together with the Freehand tool, line segments can completely get lost. In LECTURNITY 3.0 this freehand performance is improved in comparison to LECTURNITY 2.0.p4, so that these effects are less perceivable or not perceivable at all. This covers the usage of pen-based input devices, such as touch screens (SMART Sympodium, etc.) and Tablet PCs.
  
  

Bug fixes

The following bugs of LECTURNITY 2.0.p4 are fixed in LECTURNITY 3.0:

Assistant

• Wrong error message on opening a project file of a packed project: If a project is packed in the Assistant and transferred afterwards to another system, then opening the project file of this packed project in Assistant erroneously results in an error message concerning a non-existing directory in certain situations. This error message has no further consequence.
  
  
• Malfunction of hotkeys for Pure Screengrabbing in certain situations: If the hotkeys are not defined before the recording start and no “normal” recording (not a Pure Screengrabbing recording) happens before the Pure Screengrabbing, the defined hotkeys do not work properly.
  
  

Editor

• Wrong button type after reopening an edited document: If a document with image buttons in questions is opened in the Editor and the settings of a question are modified, then text buttons are erroneously used for this question further on, even if the user does not modify the button type.
  
  
• Malfunction on reopening documents with questions including “<” or “>”: If the title or text of a question includes a “<” or “>”, then the question cannot erroneously be edited after reopening this document in the Editor.
  
  
• Incomplete test feedback on merging several documents with tests: If several documents (more than one) with test are merged in the Editor, only the questions of the first inserted or opened document are covered in the test feedback of the Editor’s preview mode.
  
  
• Wrong text object positioning in certain situations: Text objects (including text on buttons) are not correctly positioned in certain situations in the Editor, even if the objects are correctly positioned in Assistant, Player, or other target formats.
  
  
• Wrong replay behaviour together with disabled test feedback in certain situations: If the test feedback in a document is disabled, then the feedback of the last question is erroneously displayed for a very short time span only and the action bound to the test completion is erroneously executed twice (e.g., “jump to next page” is executed twice).
  
  

Publisher

LECTURNITY Real Media Documents

• Incomplete display of Pointer objects in certain situations: If the spatial distance between two consecutive positions of a Pointer object in a document is too small, the later one of the two positions (with regard to the document time) is erroneously dropped during the creation of the RealMedia Document. As a consequence the Pointer object is not displayed on this position during replay. Therefore, in certain situations no Pointer object at all is displayed on a page.
• Wrong page changes in certain situations: Under certain circumstances the next page in a document is displayed too early whereas the annotations of the current page are still displayed, i.e., the annotations appear as displayed on the wrong page.

   

   

  LECTURNITY Windows Media Documents

• Incomplete display of Pointer objects in certain situations: If the spatial distance between two consecutive positions of a Pointer object in a document is too small, the later one of the two positions (with regard to the document time) is erroneously dropped during the creation of the Windows Media Document. As a consequence the Pointer object is not displayed on this position during replay. Therefore, in certain situations no Pointer object at all is displayed on a page.
• Wrong page changes in certain situations: Under certain circumstances the next page in a document is displayed too early whereas the annotations of the current page are still displayed, i.e., the annotations appear as displayed on the wrong page.

   

   

  LECTURNITY Flash Documents

• Partially overlapped or completely hidden interactive objects in certain situations: If documents are very long or consist of many objects, interactive objects in the document, such as buttons or interactive areas, are erroneously overlapped or completely hidden behind other objects in certain cases.

   

   

  LECTURNITY Presentation Documents

• No visual feedback or interactivity with documents including “ in question titles or texts: If a document includes the character “ in a question title or text, the creation of the corresponding LECTURNITY Presentation Document results in a Publisher status with no further visual feedback or interactivity. As a consequence the document is not correctly created.
  
  

Player

• Error “Unable to init WhiteBoardPlayer” with documents including “ in question titles or texts: If a document includes the character “ in a question title or text, the opening of this document in the Player results in the error message “There was an unexpected error! RuntimeException: Unable to init WhiteBoardPlayer”. As a consequence the Player cannot open the document.
  
  
• Malfunction of keyboard shortcut <Space> in Full Screen mode: If a document is opened in Full Screen mode or the view mode is switched to Full Screen before the first replay start, the keyboard shortcut <Space> for replay start does not work properly.
  
  
• No jump or scrolling over stop marks possible: If a user tries to jump or to scroll over a stop mark on the time line during replay, the replay erroneously stops on this stop mark, i.e., the current replay position is placed on the stop mark.