Opened my screenplay project from 1.54 with the latest 2.0 and all the formatting has been changed to “General Text.”
Changing the Script Mode to Screenplay does not bring the Script Elements back to life.
Do I have to go back and tweak every single line with an individual Script Element choice, or is there a step I’m missing?
I’ve been adjusting each individual element in my current screenplay (written in 1.54) after importing into 2.0 (which turned everything into General Text)
I should add that this also happened with the last major update to Scrivener as well.
As much as I love to use this program, this is a big hassle for a 100-page script.
Hi,
I’m sorry for not getting back to you sooner - I haven’t had chance to look at this because of other bugs that have needed addressing. It is on my list, though, and I’m sorry for the problems this has caused you - it looks as though at some point changes were made to the default screenplay format to better fit with standards, although the changes are subtle and not obvious, so I want to check them.
However, you don’t need to go through every single line of text - although if you’ve started that you will need to continue for any scripts half done. But for any other projects that need updating, there is a much quicker way - instead of trying to get your script to match Scrivener’s default script settings, just change the script settings to match your script formatting. The quickest way to do this with an existing script is:
Open Format > Scriptwriting > Script Settings…
With the script settings panel open, select an element in the script element and then click into some text that is supposed to be recognised as being that element in the main window.
Click on the “Manage…” button in the lower-left corner of the script settings panel and choose “Use current font & paragraph settings”. This will change the script formatting so that recognises that text as the selected element.
Repeat for all elements.
This should take about five minutes to do, and after that you’ll be up and running again.
My sincere apologies for not getting back to you sooner, as this would have saved you some work.
All the best,
Keith
Thank you so much for getting back to me. Tried your solution and it works well. Best of luck with the updates.
Glad that helped. Apologies again for not getting back to you sooner and for these problems in the first place.
Thanks!
All the best,
Keith
A few remarks that might help at solving this bug :
I have created my own custom script format, and when i open my docs created with 1.5x, I experience the same problem, so this might not be related to changes made in the default script format.
When I reopen the texts of this older scriv files, they are no longer in script mode. I need to select the script mode with my custom format in Format -> scriptwriting. Then the style menu shows again at the bottom right of the window. However all the text is identified with the “general text” style, but the actual format attributes are preserved (the text appearance is unchanged). As I compile “as is”, the scope of the problem is limited for me. But clearly style identification is lost when opening a 1.5 doc in 2.0.
I also ran into a format loss issue when upgrading from 1.54 to 2.0. Keith’s remedy above somehow doesn’t work for me, and I can’t get a script setting panel when I choose from the format window and the script has been set to <SCREENPLAY (FINAL DRAFT)>, which is the script setting I used to create the document in 1.54.
I’ve gone through that procedure before during a previous upgrade and had no problem, but nothing happens if I try to set tags (use current postion…) using a different canned script setting… nothing changes. I’m also confused by this dialogue that appears after from the script settings panel and couldn’t locate that in the manual? What does one do with it and why?
To make matters worse, the backup saved by 2.0 upon install is no longer 1.x compatible, and if i can’t find a way to recover, I’m going to lose some work.
Now, this is the trial version install. Please tell me that if I buy the whole whiz bang, Keith’s fix-up procedure should work. I didn’t want to purchase 2.0 if I can’t use it right away.
I’m a longtime user and love the product. Keep doin’ it…
Regards,
blamby
Something I forgot to mention that may be pertinent… I’m on MAC OSX 10.4.11, a PowerPC version of the OS, not INTEL. Not sure it matters…
Thanks,
forgetful blamby
I confirm this. I also tried it on one of the BBC formats and was unable to open the settings panel. It appears some work and some do not. Console spit this out when I switched to the Screenplay-Final Draft mode:
2010-11-29 08:54:41 Scrivener[37185] -[NSCFString count]: unrecognized selector sent to instance 0x1d828000
2010-11-29 08:54:41 Scrivener[37185] HIToolbox: ignoring exception '-[NSCFString count]: unrecognized selector sent to instance 0x1d828000' that raised inside Carbon event dispatch
(
0 CoreFoundation 0x9508abba __raiseError + 410
1 libobjc.A.dylib 0x9833f509 objc_exception_throw + 56
2 CoreFoundation 0x950d78db -[NSObject(NSObject) doesNotRecognizeSelector:] + 187
3 CoreFoundation 0x950317e6 ___forwarding___ + 950
4 CoreFoundation 0x950313b2 _CF_forwarding_prep_0 + 50
5 CoreFoundation 0x95027571 -[NSDictionary initWithDictionary:copyItems:] + 65
6 CoreFoundation 0x95027521 -[NSDictionary initWithDictionary:] + 49
7 CoreFoundation 0x950274d0 +[NSDictionary dictionaryWithDictionary:] + 64
8 Scrivener 0x001050f1 +[SCRScriptSettingsSheetController bindingsCompatibleScriptElementsFromStandardElements:] + 3976
9 Scrivener 0x00101338 -[SCRScriptSettingsSheetController originalScriptSettings] + 262
10 Scrivener 0x00101837 -[SCRScriptSettingsSheetController resetToSaved] + 29
11 Foundation 0x983f91c3 _nsnote_callback + 176
12 CoreFoundation 0x950123c3 __CFXNotificationPost + 947
13 CoreFoundation 0x95011dca _CFXNotificationPostNotification + 186
14 Foundation 0x983ee090 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
15 Foundation 0x983fb46d -[NSNotificationCenter postNotificationName:object:] + 56
16 Scrivener 0x0001addd -[SCRMainDocument changeScriptSettings:] + 1571
17 AppKit 0x92c6df1e -[NSApplication sendAction:to:from:] + 112
18 AppKit 0x92c6ddd1 -[NSMenuItem _corePerformAction] + 435
19 AppKit 0x92c6dac2 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 174
20 AppKit 0x92c6d9ae -[NSMenu performActionForItemAtIndex:] + 65
21 AppKit 0x92c6d961 -[NSMenu _internalPerformActionForItemAtIndex:] + 50
22 AppKit 0x92c6d8c7 -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 97
23 AppKit 0x92c6d80b -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 336
24 AppKit 0x92c61f49 NSSLMMenuEventHandler + 404
25 HIToolbox 0x926c8f2f _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1567
26 HIToolbox 0x926c81f6 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 411
27 HIToolbox 0x926ea9bb SendEventToEventTarget + 52
28 HIToolbox 0x92716fa7 _ZL18SendHICommandEventmPK9HICommandmmhPKvP20OpaqueEventTargetRefS5_PP14OpaqueEventRef + 448
29 HIToolbox 0x9273bd1c SendMenuCommandWithContextAndModifiers + 66
30 HIToolbox 0x9273bcd1 SendMenuItemSelectedEvent + 121
31 HIToolbox 0x9273bbda _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 152
32 HIToolbox 0x9270b2e4 _ZL14MenuSelectCoreP8MenuData5PointdmPP13OpaqueMenuRefPt + 454
33 HIToolbox 0x9270aa56 _HandleMenuSelection2 + 465
34 HIToolbox 0x9270a874 _HandleMenuSelection + 53
35 AppKit 0x92c5b48a _NSHandleCarbonMenuEvent + 285
36 AppKit 0x92c3003a _DPSNextEvent + 2304
37 AppKit 0x92c2f2ca -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
38 AppKit 0x92bf155b -[NSApplication run] + 821
39 AppKit 0x92be95ed NSApplicationMain + 574
40 Scrivener 0x0000301d _start + 208
41 Scrivener 0x00002f4c start + 40
)And then this, when attempting to load Script Settings:
2010-11-29 08:55:02 Scrivener[37185] -[NSCFString count]: unrecognized selector sent to instance 0x19fb4ec0
2010-11-29 08:55:02 Scrivener[37185] HIToolbox: ignoring exception '-[NSCFString count]: unrecognized selector sent to instance 0x19fb4ec0' that raised inside Carbon event dispatch
(
0 CoreFoundation 0x9508abba __raiseError + 410
1 libobjc.A.dylib 0x9833f509 objc_exception_throw + 56
2 CoreFoundation 0x950d78db -[NSObject(NSObject) doesNotRecognizeSelector:] + 187
3 CoreFoundation 0x950317e6 ___forwarding___ + 950
4 CoreFoundation 0x950313b2 _CF_forwarding_prep_0 + 50
5 CoreFoundation 0x95027571 -[NSDictionary initWithDictionary:copyItems:] + 65
6 CoreFoundation 0x95027521 -[NSDictionary initWithDictionary:] + 49
7 CoreFoundation 0x950274d0 +[NSDictionary dictionaryWithDictionary:] + 64
8 Scrivener 0x001050f1 +[SCRScriptSettingsSheetController bindingsCompatibleScriptElementsFromStandardElements:] + 3976
9 Scrivener 0x00101338 -[SCRScriptSettingsSheetController originalScriptSettings] + 262
10 Scrivener 0x00101837 -[SCRScriptSettingsSheetController resetToSaved] + 29
11 Scrivener 0x001019cd -[SCRScriptSettingsSheetController showWindow:] + 44
12 AppKit 0x92c6df1e -[NSApplication sendAction:to:from:] + 112
13 AppKit 0x92c6ddd1 -[NSMenuItem _corePerformAction] + 435
14 AppKit 0x92c6dac2 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 174
15 AppKit 0x92c6d9ae -[NSMenu performActionForItemAtIndex:] + 65
16 AppKit 0x92c6d961 -[NSMenu _internalPerformActionForItemAtIndex:] + 50
17 AppKit 0x92c6d8c7 -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 97
18 AppKit 0x92c6d80b -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 336
19 AppKit 0x92c61f49 NSSLMMenuEventHandler + 404
20 HIToolbox 0x926c8f2f _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1567
21 HIToolbox 0x926c81f6 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 411
22 HIToolbox 0x926ea9bb SendEventToEventTarget + 52
23 HIToolbox 0x92716fa7 _ZL18SendHICommandEventmPK9HICommandmmhPKvP20OpaqueEventTargetRefS5_PP14OpaqueEventRef + 448
24 HIToolbox 0x9273bd1c SendMenuCommandWithContextAndModifiers + 66
25 HIToolbox 0x9273bcd1 SendMenuItemSelectedEvent + 121
26 HIToolbox 0x9273bbda _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 152
27 HIToolbox 0x9270b2e4 _ZL14MenuSelectCoreP8MenuData5PointdmPP13OpaqueMenuRefPt + 454
28 HIToolbox 0x9270aa56 _HandleMenuSelection2 + 465
29 HIToolbox 0x9270a874 _HandleMenuSelection + 53
30 AppKit 0x92c5b48a _NSHandleCarbonMenuEvent + 285
31 AppKit 0x92c3003a _DPSNextEvent + 2304
32 AppKit 0x92c2f2ca -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
33 AppKit 0x92bf155b -[NSApplication run] + 821
34 AppKit 0x92be95ed NSApplicationMain + 574
35 Scrivener 0x0000301d _start + 208
36 Scrivener 0x00002f4c start + 40
)Ioa, can you please simple provide steps to reproduce?
Format/Scriptwriting/Screenplay (Final Draft)
Format/Scriptwriting/Script Settings...
Should fail with just those steps. I got the second batch of console errors on step 3. To get the first batch of console errors, for a 4th step, choose “BBC Taped Drama” (probably because the sheet has been instantiated at this point; and is hidden offscreen).
My speculation: The only bug here for you to concern yourself with is not showing old script formats from 1.x. From what I can tell, this only happens with scripts that were originally installed with Extras.
To the poster that is having difficulties getting script settings, follow these steps:
You can do this while Scrivener is open; the menu should clean up considerably (you probably had duplicate entries before). If you have any formats you’ve created with 2.0, you might wish to drag them back in, but leave the old stock “Extras” out.
I’ll try it first thing tomorrow… Thank you, AmberV
Regards,
blamby
Not having any luck with AmberV’s suggestion on moving the ScriptFormats folder to the desktop. I still can’t assign tags using . I’m lost.
What happened to <Screenplay (FINAL DRAFT)> version ? What is the usage of the dialogue that appears after selecting on the SCRIPT SETTINGS PANEL? Do I use it or not?
Regards,
blamby
The old Final Draft format is no longer required. It was intended to approximate the exact RTF settings that would be needed to take an RTF file to Final Draft and have Final Draft interpret it correctly. That’s not necessary now that Scrivener can write directly to FDX (and FCF) formats. The standard screenplay format is much better.
The “Convert” dialogue should be fairly self-explanatory - if you change the script settings, this dialogue box allows you to have Scrivener update the documents in your project to use the new script formatting. You should use it if you have made changes in the script settings that you want applied to existing documents.
I’m a bit confused about what your problems are with using the “Use current formatting” setting, though - this should work fine as long as you aren’t getting the errors any more on the Console.
Thanks,
Keith
How do I get the console? I searched the manual for the word ‘console’ in the manual, and it only shows up once, in a footnote.
Just in case, I tried to enable the paid version of the product. I used the registration numbers given me in the invoice, but it won’t take it. I checked and double-checked the entry… no dice.
Maybe I’m stupid, but I’ve done this procedure before without a hitch. The plus ‘OK’ only changes the current line, not the others like it.
I’m looking for clues…
Regards,
blamby
console is an os x app. It is found in applications, utilities. Or you can use spotlight to find it.
Never mind about the serial number… I just had to wait long enough for L&L to catch up with me.
Sorry…
blamby
No errors on the console when I .
Nothing happens…
== blamby
Wait, what do you mean by this? We are talking about Manage… > Use current font and paragraph settings, right? And this changes the current script element in the Script Settings panel to match whatever the formatting is at the current insertion point in the text - are you expecting this to change the text in the editor? If so, that would be the source of your confusion - that’s not what this is for at all. The idea of the information I posted in that other thread was to change the current script settings to match all your text, not the other way around.
All the best,
Keith
Then I guess I am stupid. I was trying to mske the script settings match the format of my document. Once I do that, why doesn’t it interpret my format as tags, as it should do when you import am RTF?
How do use I use 2.0 and retain my original script format info.
I bought the product, now it seems I can’t use it.
Sorry about this trouble… the upgrade should be better explained for the daft, I guess.
Regards,
blamby