BJ
December 8th, 2016, 03:04 PM
The following items are of special note to users updating to the most recent version of Realm Works:
• WARNING! We uncovered an error where certain snippets were not being manipulated correctly. These snippets may appear to be corrupted and/or contain incorrect links when viewed – or they may look fine, with the problem lurking beneath. This release includes corrections to the problem, but all necessary fixups must be applied before each realm can be accessed. Therefore, do not install this new version if you are in a hurry, such as shortly before a game session. The fixup process can take many minutes to complete. More details are provided below.
• NOTE! This new version requires a login to the server before you can access any of your realms. You can continue using older builds by choosing to operate offline and not logging in to the server.
The following is a summary of the significant enhancements and new behaviors introduced in this release:
• As indicated above, some realms will have snippets that were incorrectly handled in previous versions. Each realm must be analyzed and corrected prior to being loaded. When you load a realm for the first time, you will be given the option to perform the fixup or cancel the load. If you proceed with the load, any existing issues will be identified and corrected, which may take anywhere from a second to many minutes, depending on how many snippets with the problem are found.
The following minor enhancements and changes were introduced in this release:
• The workflow for adding content to Player View has been streamlined. Whenever you are viewing a smart image or external object (e.g. picture) in its own tab and attempt to show it in Player View, you will now be given the option to immediately reveal the governing topic and snippet (assuming one or both is not already revealed).
• The “Show in Player View” option is always enabled for smart image and external object (e.g. picture) snippets, even if the snippet or topic is not revealed. If selected, the user is prompted to reveal the snippet and/or topic, as necessary to show to the contents to the players.
• If you don’t want to be prompted to confirm revealing topics and snippets to show something in Player View, there is a new preference to disable this behavior.
• When you add something to Player View, it will now be immediately made visible to players. The extra step of showing the window to the players has been eliminated.
• If you don’t want content to be immediately shown t players within Player View, there is a new preference to disable this behavior.
• A visual separator line has been added beneath the header region within the content pane, providing a clear demarcation between the header and the scrollable content region below.
The following issues and problems were addressed in this release:
• When the user navigated to an external object like a picture for the first time, the Quick Help was not being automatically shown properly.
• When there were two snippets, with each snippet having exactly one potential link each and where the links' ranges within their snippets' text are the same or overlapping, only one of them was being ignored if both were specified as ignored. A second save operation was needed to re-prompt to ignore the other name before both were correctly ignored.
• Saving changes to an explicitly ordered tag domain would often leave the domain still behaving as it is was unsaved, requiring a second save to actually apply it.
• When configured to not auto-create text snippets within sections of topics, there were situations where they would still be errantly created.
• Game-specific categories, snippet types, and tag domains that were modified by the user after removing protection were no longer reporting as game-specific, which caused the icon shown next to them to be wrong.
• Under certain conditions, ignoring a link within a text snippet that also had GM directions could trigger a crash.
• On a computer where the low-memory warning is shown when loading a realm, returning to the Launch Dialog, viewing Quick Help on the Create Realm panel, and then closing Quick Help would trigger a crash.
• Revealed aliases are now shown within the appropriate topics within Player View.
• Double-clicking within a topic while the topic was being loaded could trigger a crash.
The following are known issues:
• None
• WARNING! We uncovered an error where certain snippets were not being manipulated correctly. These snippets may appear to be corrupted and/or contain incorrect links when viewed – or they may look fine, with the problem lurking beneath. This release includes corrections to the problem, but all necessary fixups must be applied before each realm can be accessed. Therefore, do not install this new version if you are in a hurry, such as shortly before a game session. The fixup process can take many minutes to complete. More details are provided below.
• NOTE! This new version requires a login to the server before you can access any of your realms. You can continue using older builds by choosing to operate offline and not logging in to the server.
The following is a summary of the significant enhancements and new behaviors introduced in this release:
• As indicated above, some realms will have snippets that were incorrectly handled in previous versions. Each realm must be analyzed and corrected prior to being loaded. When you load a realm for the first time, you will be given the option to perform the fixup or cancel the load. If you proceed with the load, any existing issues will be identified and corrected, which may take anywhere from a second to many minutes, depending on how many snippets with the problem are found.
The following minor enhancements and changes were introduced in this release:
• The workflow for adding content to Player View has been streamlined. Whenever you are viewing a smart image or external object (e.g. picture) in its own tab and attempt to show it in Player View, you will now be given the option to immediately reveal the governing topic and snippet (assuming one or both is not already revealed).
• The “Show in Player View” option is always enabled for smart image and external object (e.g. picture) snippets, even if the snippet or topic is not revealed. If selected, the user is prompted to reveal the snippet and/or topic, as necessary to show to the contents to the players.
• If you don’t want to be prompted to confirm revealing topics and snippets to show something in Player View, there is a new preference to disable this behavior.
• When you add something to Player View, it will now be immediately made visible to players. The extra step of showing the window to the players has been eliminated.
• If you don’t want content to be immediately shown t players within Player View, there is a new preference to disable this behavior.
• A visual separator line has been added beneath the header region within the content pane, providing a clear demarcation between the header and the scrollable content region below.
The following issues and problems were addressed in this release:
• When the user navigated to an external object like a picture for the first time, the Quick Help was not being automatically shown properly.
• When there were two snippets, with each snippet having exactly one potential link each and where the links' ranges within their snippets' text are the same or overlapping, only one of them was being ignored if both were specified as ignored. A second save operation was needed to re-prompt to ignore the other name before both were correctly ignored.
• Saving changes to an explicitly ordered tag domain would often leave the domain still behaving as it is was unsaved, requiring a second save to actually apply it.
• When configured to not auto-create text snippets within sections of topics, there were situations where they would still be errantly created.
• Game-specific categories, snippet types, and tag domains that were modified by the user after removing protection were no longer reporting as game-specific, which caused the icon shown next to them to be wrong.
• Under certain conditions, ignoring a link within a text snippet that also had GM directions could trigger a crash.
• On a computer where the low-memory warning is shown when loading a realm, returning to the Launch Dialog, viewing Quick Help on the Create Realm panel, and then closing Quick Help would trigger a crash.
• Revealed aliases are now shown within the appropriate topics within Player View.
• Double-clicking within a topic while the topic was being loaded could trigger a crash.
The following are known issues:
• None