Dummy question, but that never stopped me before: will this update projects created on 1.03 and if so, can I still open them in the stable, older release if I find myself getting buggered in the beta? (So to speak)
Read on…from the read me file included with the beta download. (I also tend to try something before reading instruction manuals.)
“When you first open an older project in 1.1, you will be asked to update the project to the newer format. A backup will automatically be made of your old project, so be sure to keep it safe in case you need to roll back to an earlier version of Scrivener (projects created in 1.1 will not open successfully in earlier versions of Scrivener; earlier versions may even corrupt files made in 1.1 and later, so please be careful)…”
I came across an odd bug on my laptop. When multiple documents are selected with the Inspector open, and the Project Notes pane comes it, it is tinted bright red, not 255,0,0 per se, but a very solid vibrant red. I can not replicate this on my desktop, so I’m going to continue to try and solve where it came from. I only noticed this problem after I had defaulted the preferences, and maybe done a little minor tweaking to the colours. Index card tinting is off (which shouldn’t make a difference anyway).
Just thought I would post it before I knew how to replicate it though, just in case you might have an idea of what could cause that.
Curious. Sometimes I set a view background to red to test for bugs, as it helps show up redrawing glitches, so at first I thought I may have accidentally left some test code in there. But I have been through all instances of colour being set in Scrivener, and nowhere is there any red where it shouldn’t appear. Very strange.
Was the red in the back of the whole of the notes view, or just the lower part, after the text (which would indicate it would be the scroll view not the text view)?
At the moment, I’m going to have to put this down to a redrawing bug on your laptop…
Best,
Keith
Heresy in a Scrivener forum but sometimes a picture is worth a thousands words. FYI here is more than you ever needed to know about getting screengrabs and screenshots on Mac OS X oreillynet.com/pub/a/oreilly … crets.html
Hopefully just a small thing, but is is possible to also make the text of the selected binder document bold? Using Lucida, for example, the roman text becomes very hard to read when changed to white and a dropshadow added. (Most Apple source lists do this, I believe, but of course the font there isn’t changeable.)
I’d rather not have to use a bold font for the entire binder, that would be rather ugly 
Hi,
I updated to the latest beta, and attempted to export manuscript from novel format. Before, it had automatically put a heading on each page, but this time it didn’t have the heading. I think it happened when the beta updated the document format, because when I opened a new project in the format, the header was back. Perhaps it is a problem in the conversion?
Have I mentioned how much I love your product?
Regards,
Karl
If you mean the page header, yes, this will happen with updated projects because the way headers are done has changed - you just have to redo the header in the Export > Draft settings to get it back, I’m afraid.
Best,
Keith
P.S. Antony - source lists don’t use a bold font as far as I can see, so I think it may just be the font you are using doesn’t look so good in white… Sorry. (It would have to be a preference and the preferences are kinda full - plus I want to get 1.1 and get writing ASAP before I lose the will to live.)
Best,
Keith
Not wanting to start an argument (or distract you from The Novel), but:
Same font and size in Scriv, but without the emboldening when highlighted:
Sorry, but it was fine in the previous version. Oh, for the days of yore…
Eh, thanks, but I figured “notes background colour is bright red” was enough information.
Anyway, I meant to post a follow up on this, and it must have slipped my mind. I discovered that it was indeed a problem with the preferences. The note’s background preference was set to black, even though it came up as white normally. So I changed that back to white, and now the red is gone.
Must have been some very minor preference corruption. I’ll let you know if I come across it again–but it is probably a freak thing.
Not sure if I’m doing this right:
When I lock a page in place, the header does change color. But whenever I click anything in the binder, the editor changes to that item. Nothing stays locked.
Thanks!
I think the keyboard shortcut to create a folder doesn’t seem to work at all.
When using a split screen the name of last opened text stays highlighted in the binder even if you close the screen that has displayed it. The hightighting should jump to the name of the remaining text.
Yep, that’s a silly bug I noticed myself a couple of days ago. In fact, Lock in Place only works if you are in an Edit Scrivenings session! This is fixed for the next update, don’t worry.
It works fine - either you have something installed that is interfering with it (such as QuickSilver) or you do not have the binder, corkboard or outliner focussed whilst hitting the keyboard combination.
No it shouldn’t. This is intended behaviour. Please see the FAQ or Help file for an explanation.
Thanks and all the best,
Keith
Probably related, but I noticed that when you search for annotations in full screen with a locked E.S. session, press either next or previous immediately breaks the session. Stays locked in standard mode, though.
Hmm, not quite sure what you mean - there is no “Locked in Place” in full screen; it only applies to the main window editors.
Best,
Keith
I wondered if that was the case, but I figured I’d bring it up since it acts different in the two views. Annotation searching is restricted to the session in standard, but erases the session and goes into single document display as soon as you press ‘next’ or ‘previous’. I guess it is fine since full screen locking doesn’t make any sense otherwise.