Scrivener 1.1 beta (1.07) public beta now available

Scrivener Beta Testing (Mac)
1

Hello all,

Right, now hopefully this really is the final 1.1 beta (I said that last time) and that all I have to do now is update the Help file. Here it is:

literatureandlatte.com/dlbet … _1b107.dmg

This beta basically just fixes the bugs that arose in 1.06b. The changes between 1.06 and 1.07 can be found at the end of this post and also in the readme file; the full change list since 1.03 is way too long to post here, so please refer to the readme file on the DMG.

FYI, 1.1 is fully compatible with Leopard as of the latest (WWDC) Leopard seed. And very nice it looks, too.

Note that this version will update even projects created on 1.055b, as it now stores version information in a different way. (A problem in the past has been that older versions of Scrivener that encounter a .scriv file in a newer file format will mistake it for an older format and try to update it, thus corrupting it; it is too late for me to fix this in versions that are already out there, but as of this version, it won’t try to update files created on future versions of Scrivener.)

I provide this beta so that users can test out new features and stability, to ensure that 1.1 is as solid as possible whilst I update the Help file. If you download this beta, please do help me out as follows:

1) Whilst using the beta, try to have Console.app open at the same time
As soon as anything strange happens in the beta, have a look at the log in Console.app. Anything strange should appear in bold. Let me know if anything strange does happen and copy and paste the log for me to see. This is often invaluable.

2) Post anything related to the beta HERE, not anywhere else on the forum
Please post bug reports or anything else related to the 1.1 beta as a reply to this thread. (Only moderators can create new topics in the Beta Testing forum because I don’t want it getting clogged up with individual bug reports - hence reports should be posted as replies.)

3) Remember it’s a beta
All that means is that the Help file is out of date. The menus, especially, have been shifted around a little and so won’t match the descriptions in the Help documentation. (If anyone has the time to take a look at the tutorial and e-mail me a list of what needs updating in the Tutorial, I would be grateful, as my priority will be the Help file itself for now.)

Enjoy!
Best,
Keith

Change list between 1.06 and 1.07
• Fixed bug whereby Edit Scrivenings commands in menu did not work.
• Added cmd-ctrl-T as keyboard shortcut for Typewriter Scrolling.
• Fixed bug whereby Backup Project To panel would not open because Scrivener was trying to use some methods not supported on Tiger.
• Moved “Re-capitalize Scriptâ€

2

The About Scrivener splash still shows the book and coffee cup as a mask.

(Magnificent!)

:smiley:

3

Hello,
still Crash on Project statistics, similar behaviour as previous,
(wondering if it may be due to filevault ?)

how is this, anybody to confirm ?

cheers and thank you again KB !

4

I, for one, don’t mind at all. Thanks and cheers :slight_smile:

5

I have “Scroller type” set to “No scroller” in Full Screen prefs, yet I am still seeing a (normal Aqua) scroller in full screen. This is the first beta version I have used, but in the current official release, this had been working as expected.

6

I confirm a grey line still appears where the scroller should be (… or not be). It is this way both with No Scroller or Auto-Hiding Scroller selected.
OSX 10.4.8 Italian.

Paolo

7

I know this is not a bug - but unlike my namesake I do mind the new colour for gradient highlights in the binder. Is there any chance (or any trick) to get back the wonderful blue of 1.06? Of course, if this is not an option, I´ll try to get used to “Blood on the Binder” or I´ll reconsider my ten-year-old choice of red for highlighting text and probably smash the distinction between choosing text and choosing elements - actually, this distinction has always been quite arbitrary (at least when it comes to scrivenings :slight_smile: ).

(To keep this short, my general praise is to be found in the feedback section. I absolutely love this program.)

8

This really should not have happened since 1.04. Please, please, whenever posting a crash report follow the procedure and post the exact steps to reproduce along with the crash report (the sticky post in the Bug Hunt forum tells you how to get to the crash report if you don’t know). It makes my life a lot easier if I don’t have to ask every time. :slight_smile:

That is a bug caused by me changing it in Photoshop and making it like that intentionally. :unamused:

I’ll look at the full screen scroller thing.

Best,
Keith

9

In case people think that this Jan from Berlin is just one guy who thought this forum would be a good place to act out his schizophrenia, be assured that there are at least as many Jans in Berlin as there are Johns in London :slight_smile:

As for the Binder highlight color, I can see a problem with the new behavior if your highlight color of choice is red. (Unless the title of your next novel is “redruM” …)
In iTunes, the highlight color in the source list is based on the system appearance color (Graphite or Blue), not on the color for highlighting text. I didn’t notice the difference in the way iTunes and the latest Scrivener beta handle these system-wide preferences because my text highlight color is also graphite.

I’m glad that Keith chose to use the system settings for drawing highlights in the Binder, because I hate that squeaky-blue Toys’R’Us look of the default system appearance. But I think it would be better if Scrivener followed iTunes more closely and used the system appearance color instead of the highlight color. Graphite system appearance = graphite highlights; blue system appearance = blue highlights.

–
(Please note that I used American spelling to differentiate myself from my alter ego; though I’m afraid his posts will receive preferential treatment from the headmaster for adhering to these weird British spelling rules :slight_smile:)

10

This one is rock solid for me (ibook g4, os 10.4.10). The keyboard shortcuts for scrivenings are especially nice.

Great work.

11

I am all for using the System Prefs colour for highlighting – thank you very much! I hate that mandatory baby blue…

However.

I don’t think the gradient concept is very practical from an ergonomic POW. It looks cool for sure, but at least on my system, whatever highlight colour I select, the highlighted binder text is always white! Very difficult to read and an invitation to eyestrain, in my opinion.

Best regards,

Joey

12

I’ll add a preference for the binder selection to be blue/graphite or to use selection colour.
Best,
Keith

13

Fullscreen mode edit scrivenings “please wait” glitch with intermittent crash.

To reproduce the glitch:

  • Start an Edit Scrivenings session.
  • Switch to fullscreen mode.
  • Type in the bottom-most file.
  • Command-n to create a new file.
  • Observe the “Loading text…/Please wait…/grey swirly” dialogue box
  • To crash, continue typing small amounts and command-n’ing new files, periodically toggle fullscreen.

The only thing that shows up in the console besides the notification of a crash:

I also get a perfectly normal scroller widget when “no scroller” is selected. But the auto-hiding scroller works fine.

14

Eeek! The Auto-Hide Scroller option now seems to work again (after restarting Scrivener). The Scroller option still shows a white space that shouldn’t be there.

Paolo

15

Hi Keith,
As with mcbend above, I also experienced a crash with the project statistics.

In case it matters, this is the first time I have downloaded a beta, so the scrivener project I am using was converted directly from the previous release version to match this beta. Before the crash, I converted the project file and was more or less exploring the new menu items and preferences, and then clicked on Project Settings. It beach-balled me for quite a while, and then crashed.

Console showed up the following:

I know the first NSTableView is irrelevant, and I left my computer for a while. I would say the alerts from 19:31 onwards most likely correlate to when the hang began.

I have also attached the Crash Log (Keith - if you have control over the allowed extensions, you might want to add .log so that crash reports don’t need to be renamed to .txt).

Happy bug hunting! If you need any more info, let me know.

Thanks,
Matt
Scrivener.crash.log.txt (77.2 KB)

16

Keith, the Project Statistics also crashed to me, when I checked the “Include sub-documents” option with a rather big project. Please find my log, too.
Paolo
scrivenercrash_pt.txt (3.34 KB)

17

To avoid the project statistics crash, try turning off “No widows/orphans” in File > Page Setup > Settings… > Scrivener > Text Options.

Let me know if turning off that option fixes the crash for you. I know where the crash is happening but have no idea why. In fact, I have a sneaky suspicion (and evidence that I cannot share :wink: ) that this is an OS X Tiger bug…

Best,
Keith

18

Keith, so it does. And, when turning on that Page Setup option again, the crash is no longer there. It seems that turning the Windows/Orphans option off and then on again fixes the bug.

Restarting Scrivener resets everything: the bug reappears, and is solved again as you suggested.

Paolo

19

Thanks for improving Scrivener’s utility as a screenwriting program. Auto-complete looks very helpful, but I’m having some trouble getting it to work right.

When I make a new scene heading and type “IN,” Scrivener automatically offers me a shortcut for “INT.” (YAY!), and even adds a dash when I hit TAB after the setting. However, I can’t seem to get it to offer me the shortcuts for DAY or NIGHT.

Typing doesn’t seem to trigger it, and neither does option-esc or cmd-.

Is there a preference or other secret handshake that I need to set correctly?

20

DAY and NIGHT are there in the standard screenplay mode - just type “D” or “N” to trigger. If it’s not working, go to Text > Scriptwriting > Script Settings… and check the Auto-Complete tab to ensure that they are in the list for the element for which you wish them to appear (“Scene Heading” is where they should be).

ptram - thanks for that. It’s good to know that the widows/orphans fixes it for others, too, as it means that I do know where the bug is; fixing it is a different matter.

Best,
Keith