Realm Works Version 207 is Now Available!

[liz]

A new release for Realm Works is now available! This update fixes a variety of issues that users were encountering.

Importantly, when certain types of bugs occur and you’re prompted to submit a crash report, you may also be prompted to send us your Realm Works database. This will only be requested when the nature of the crash means we need your database to properly diagnose and fix the issue. You are not required to send your database, but skipping this step will make it significantly harder (and therefore less likely) that we can solve the bug. So please help us out and provide your database when it’s requested.

To see the full list of changes and enhancements, please take a look at the Release Notes available within the product.

If you still encounter problems following this new update, please update your support ticket by sending a follow-up email or send us a new bug report.

[Acenoid]

No crashes so far.

Notice for others that might be affected:
Cutting text which includes links may cause more text than selected to disappear. A bug report was submitted.

Recommending the upgrade

[ibecker]

This update looks great so far! I had seen repeated crashes during the automatic link detection phase when saving an Article. However, since the update last night, I haven't had a single crash in several hours of work.

Thanks!

[MNBlockHead]

Another big step toward stability. I was able to get one crash with editing the names of an article, but rebuilding the index fixed it. Still, that was one out of hundreds of articles I edited, so I'm quite happy with RW's stability at this point.

[wildfire142]

This update fixed the problem I had wth being unable to edit article titles which sounds like it was a fairly common problem.

A new issue/bug has occurred though if I try to type more text after a link it sets the font to Arial with underlined active and colour blue rather than the default text settings.

It looks very close to what a link looks like so took me a few minutes to work out what had happened.

[rob]

Originally Posted by MNBlockHead

Another big step toward stability. I was able to get one crash with editing the names of an article, but rebuilding the index fixed it. Still, that was one out of hundreds of articles I edited, so I'm quite happy with RW's stability at this point.

I hope you submitted your database to us with the lone crash you encountered. If not, please do so now. We'll need the database in order to figure out the remaining problem with the indexing engine.

[rob]

Originally Posted by wildfire142

A new issue/bug has occurred though if I try to type more text after a link it sets the font to Arial with underlined active and colour blue rather than the default text settings.

It looks very close to what a link looks like so took me a few minutes to work out what had happened.

Yep. The issue arises when the snippet starts or ends with a link. Adding text at the same end is being treated as an extension of the link. We discovered that one a few days ago but haven't been able to fix it yet. Unfortunately, it looks like it's going to be difficult, as it's an issue with the 3rd party library we're using.

[wildfire142]

Originally Posted by rob

Yep. The issue arises when the snippet starts or ends with a link. Adding text at the same end is being treated as an extension of the link. We discovered that one a few days ago but haven't been able to fix it yet. Unfortunately, it looks like it's going to be difficult, as it's an issue with the 3rd party library we're using.

Thanks for explaining the issue and the fact your having trouble squashing it, but are aware of it.

[MNBlockHead]

Originally Posted by rob

I hope you submitted your database to us with the lone crash you encountered. If not, please do so now. We'll need the database in order to figure out the remaining problem with the indexing engine.

Sorry. I submitted the crash report at the time of the crash, but didn't file a bug report. Since rebuilding the index fixed it, I don't know that I have a database that contains the error. If it happens again, I'll copy the database immediately after the crass, open a bug report, and send the database if asked (no way to attach to the bug report).

[rob]

It's quite possible that your fixed database still contains the info we need to reproduce the bug you encountered. So please open a support ticket, outline what you remember of the crash (i.e. date and time it occurred, including timezone), and provide us with your database. You'll find the details of how to get us your database in the sticky thread at the top of the forums about bug reports.

Thanks!

Edit: This is not usually the case, but we've got some logging in place for the name indexing engine that may still hold the info we need.