It is evident that our performance improvement code introduced several nasty bugs in beta 022. Firstly, our sincere apologies caused by this previous beta release.
What made most of these bugs particularly difficult to fix was that we were unable to reproduce all of them. However, given the large amount of feedback clearly there were issues.
The following bugs have been addressed:
Scrivener saving issue. Hopefully, this has been addressed. Unfortunately, we were not able to reproduce this most sinister issue so we’ll have to wait for confirmation that our changes have in fact worked.
Scrivener Crash when editing folders text. Fixed.
Pulled 7Zip code fix attempts out. Reverted to standard Windows zip archiving once again. Please note to open Scrivener zipped backups please use the built in Windows zip tool not 7Zip. Which is not supported.
Additional View/Group mode changes to align functionality identically to Mac platform. Fixed.
Project search and replace saved after project close. Fixed.
Templates now work as expected and no longer open to blank template. Fixed.
Document inspector sticking to previous document when using splits and closing out of project and returning. Fixed.
Paste and Match Style within fullscreen with short cut keys. Fixed.
Horizontal split screen mashing up of text for scrivenings and long documents. Fixed.
Minor installer fixes with wording. Addressed.
Beta Release 023 is now available for download (Windows and Linux). http://www.scrivenerforwindows.com (Please remember to refresh your browser as it may have cached contents from the previous release)
IMPORTANT NOTE: a full install is required and any personal settings that you’ve made within Scrivener will be lost so you’ll need to customise them again. This was unfortunately due to the need to rename a registry keys to align with the Mac platform. There should be no further changes so you’re settings should be safe moving forward. I’m sorry about that too.
Moving forward, we are still aware of the following issues: various compile fixes, word count not showing issues, total word count issues, binder icon refresh issues, rtf lang issues when importing non utf-8 Chinese text. We are also aware that the CTRL+ALT short cut key combination are going to need changing due to international languages and Windows legacy code using the right ALT key combination for creating accented characters. As usual we will do our best to address these outstanding issues as soon as possible.
Thank you for you continued support with the beta and once again apologies for any inconvenience beta 022 may have caused.
Thanks Lee! So far no more saving issues for me. But I’ve only been playing around with it a little bit, so I don’t know for sure.
Interesting GUI changes. I’m not quite used to the grey at the moment, but anyway, it’s nothing.
One thing I noticed while fiddling around with the customisation options – in the snapshots, the text is only at 100% zoom, even though I usually use 135% zoom. This is a bit of a problem as I usually have a small font with the 135% zoom setting, and with the 100% zoom in the snapshots, the text is illegible and I can’t compare the two versions. Could you please add a zoom setting for the snapshots, too? Thanks!
Put back in text that went poof. Everything seems to be ok.
Decided to export everything as a back up but the notes are not saving. I have tried twice, checking the notes box and unless I am doing something very daft (which could be possible) the notes are definatley not saving. Meta Data and main filess are saving ok however.
Could you promote the new update more widely - just spent all morning backing up and preparing to reinstall Windows thinking it was my machine that was knackered. I’ve been on the Windows Troubleshooting forum first thing, but the news of the update is not there - just in Bug Hunt.
Hi. Thanks for the quick update. But it re-introduced another bug.
I posted before about compiling for docx and receiving the error that it “may require MS Word to be installed.” This was version 021. Then in version 022 it went away and I could compile for docx no problem. I downloaded 023 and it is giving me the same error again. So something was fixed and now is not again.
FWIW, I do have Windows 7, Word 2010 installed, all bought and paid for, legal eagle, scout’s honor.
Please let me know what I can do to help you find this little bugger.
I actually encountered the release at 4:30 this morning when I woke up for a while, and just wanted to check again that the split-stuck synopsis bug was really fixed: looks like it is.
The binder scriv highlight still isn’t keeping up when you close the editor split, but things do work otherwise both before and after a close-reopen. I’m keeping a little list of misses like this, and will send a set up soon.
Confirm with garpu that compile-to-pdf isn’t there again yet, and that it is a low priority until getting ready for actual release. Probably something very simple, since it tries to work, and worked before.
7-zip. It’s a tight compression framework, but a nasty little program, perhaps just in its GUI add-on, as I think it started out in command-land. I suspect that by comparing what it prefers from Winzip with the QT output, you can figure out the actuality of the flags, but there are many more important fish to fry at this time, much agreed.
Saves themselves are looking solid: I tried to rush them by creating a text and immediately hitting the close button, no 2-second wait I intended. The writing was there when I opened Scrivener again, which I imagine is your intent.
Great job on the recovery, Lee, and the other team (ExpressionEngine) also got a fix in this interval, so software works again in this world. Kind of amazing, isn’t it .
YES PLEASE. I can’t duplicate the ODT, PDF or DOCX compile generation issues reported. I produced all the files immediately after reading the post. I did however notice that I had to press F5 to refresh my desktop and see the files which wasn’t usual, but it’s probably my machine needing a re-boot?
I was not able to reproduce point 5. See notes on point 1.
Here’s a link to the post with the screencast on this I posted yesterday, in case you didn’t see; might be helpful. Doesn’t show the “requires MS Word” issue, but I’ll toss that up when I can get it if someone else doesn’t first.
Seems to just not be consistent (the worst kind of bug!), as I have had it throw the “you need Word” error on a machine without Word but also go through the process and use WordPad instead without giving me that error and ultimately create a successful PDF.
looked at MimeticMouton’s screen drama - not exactly like mine, but I picked up the Very name and downloaded their pdf kit after finding also the dll in Scrivener folder.
I can’t see making you a film of this myself. The action is very simple, after some tries at variations:
= with a long file or tiny, try Compile to PDF. It doesn’t matter if you use custom (very mild) or one of the preformatted compiles selectable.
= upon setting the file name, a small progress window comes up. It doesn’t say anything about Very. Progress is very slow indeed, something like 1% per 2 seconds.
= at some point between 7% and less than 20%, the small progress window disappears. Waiting longer, even minutes longer, doesn’t change what you get, so it is really done.
= observe your generated PDF. It won’t open, says corrupted. It’s 6KB for a tiny (4 scrivs of 1 line) project. It’s about 168KB for a huge project.
= try compile to print, printing to Adobe Acrobat. Takes about 3 seconds after filename approved, for the huge project. Output pdf is 401KB, and it works splendidly.
now, Scrivener compile to pdf worked, just a version or two ago. I know because I was making a small portion of those font observations with it. It was quick - maybe quicker than Adobe. Output I think was actually fine, and we are in future going to assure that.
I am on Win7 like Mouton, all freshly fresh to include yesterday’s MS updates, and Scrivener has been installed each time by a deinstall followed by dump of any progdir Scrivener folder. This last time, Scrivener deinstall had fully removed that folder itself, with my thanks.
i am speculating, but to no usefulness. So I look with a hex editor. Guess what – the entire text is there in the bad Very pdf, apparently in UTF-8 because each character prefixed with zeros. I can see its beginning and end. The adobe file is three times as large, while all the text and inclusions are compressed, so I can’t read it. Apparently there is lots of the usual included stuff there, and perhaps this is where Very is at present breaking down. Is it possible there are resources missing in the install, esp. as the fail came after clean deinstalls?
Think that’s as helpful as I can think to be, Lee. I would have cleared for and run one of the old installs again, but of course they’re date-limited.
It’s a very solid problem - repeats much the same each time. One other clue is that dual 2GHz cpus seem very busy (or something is) right about the time the small progress bar dialog wants to come up. It’s very sketchy, then fills in as the amount hits between 2 and 10%.