I’m having some weird behavior. When I chose “Print…” from the File menu, nothing happens. Cmd-P however works fine. Anyone else having this problem. (Just upgraded from 1.01. This is a new problem, as far as I can tell.)
I can replicate: the Print menu command does not work for me either, but the keyboard shortcut does work.
–Bryce
I tried also the menu: did not work.
Command P: not the first time but yes at the second try.
Again with the menu: it works now…
enigma 
Verified. It took three tries with command-P to get a print dialogue box. No worries. Keith will fix it!
Sorry, but I can’t fix it if I can’t reproduce it - and I can’t reproduce it. I need more info. Check out Console.app (in the Utilities folder of Applications) to see if any errors are getting writting out when you click on Print.
Thanks,
Keith
Okay, weird. Here’s what I did. I opened the Console app and tried Print from the menu again. Nothing. No printing. No errors. I tried different files and after two attempts, voila, the print command started working every time, even on the two files I had initially used the command on.
I closed Scr. entirely, reopened the program and it took 4-5 (I didn’t count exactly) tries to get the print command via the menu to work. It worked every time once it started working the first time.
I closed Scr., reopened it, and it took four tries to get the print command to work. Leaving Scr. open, I went to another project file and tried there. It took two tries to get the print command to work.
Here’s the messages from the console:
2007-03-28 09:38:46.740 Scrivener[272] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:38:46.746 Scrivener[272] Uninitialized rectangle passed to [View initWithFrame:].
2007-03-28 09:39:21.207 Scrivener[272] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:39:21.214 Scrivener[272] Uninitialized rectangle passed to [View initWithFrame:].
2007-03-28 09:42:28.404 Scrivener[987] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:42:28.505 Scrivener[987] Uninitialized rectangle passed to [View initWithFrame:].
2007-03-28 09:42:35.422 Scrivener[987] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:42:35.429 Scrivener[987] Uninitialized rectangle passed to [View initWithFrame:].
2007-03-28 09:43:17.792 Scrivener[987] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:43:17.892 Scrivener[987] Uninitialized rectangle passed to [View initWithFrame:].
2007-03-28 09:45:08.066 Scrivener[1002] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:45:08.071 Scrivener[1002] Uninitialized rectangle passed to [View initWithFrame:].
2007-03-28 09:45:12.528 Scrivener[1002] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:45:12.629 Scrivener[1002] Uninitialized rectangle passed to [View initWithFrame:].
2007-03-28 09:45:17.286 Scrivener[1002] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:45:17.303 Scrivener[1002] Uninitialized rectangle passed to [View initWithFrame:].
2007-03-28 09:46:11.156 Scrivener[1002] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 09:46:11.171 Scrivener[1002] Uninitialized rectangle passed to [View initWithFrame:].
Let me know if you need me to try something else.
Alexandria
Added: sorry, forgot: iBook running 10.4.9
Will not print from File>print menu, but it will with command-P. Not a big deal, just a glitch. This is with OS 10.4.9 by the way. Excellent set of revisions to application, Keith.
Question, unrelated to printing: any way to get a page count from a single document or Scrivenings multi doc?Or is it only with project stats for now?
Just to show its not all doom and gloom, File > Print works quickly and as expected on my computer - Scrivener 1.02, 10.4.9, 2GHz Core Duo.
Are all the people experiencing problems running PPC perhaps?
It works as expected for me too, after several efforts with no results. No gloom and doom. Just a bug. Those of us who are experiencing it can just report what we find, as I have done.
It takes four tries to print on a dual g4 10.4.9
2007-03-28 15:25:09.343 Scrivener[875] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 15:25:09.346 Scrivener[875] Uninitialized rectangle passed to [View initWithFrame:].
etc.
Dave
It takes four tries to print on a dual g4 10.4.9
2007-03-28 15:25:09.343 Scrivener[875] *** Assertion failure in -[NSTextView initWithFrame:], AppKit.subproj/NSView.m:710
2007-03-28 15:25:09.346 Scrivener[875] Uninitialized rectangle passed to [View initWithFrame:].
etc.
Dave
No problem with my Intel MacBookPro, spotty on my G5 PPC, every dog has his 10.4.9
jean-louis
Yeah, after three Command P’s I tried the fourth print via the file command and it worked. Who knows. It wasn’t the end of the world.
Can anyone tell me how I can include some header other than just “PROJECT NAME.scriv. - date time/page number” so I can have a chapter title up on each page, too?? mjscox@gmail.com
Just thought I’d chime in on this. No problems on my MacBook Core 2 Duo running 10.4.9.
Chris
If you want to modify the page headers or footers you have to export your draft, then import the resulting file into a word processor that does header and footer formatting. Scrivener just prints the header required to put your manuscript back in order if you drop it on the floor!
Count me on the “no worries” side – both menu and cmd-P work fine (MacBook 10.4.9)
Count me in with those having problems… Any way I try to print (command-p, print toolbar, file>print) I have to press print twice for it to work… not a huge deal considering everything that is new (and great) in 1.02, just wanted to let you know!
Printing from the Menu works fine on my Mini - 1.83 Intel Core Duo, OS X 10.4.9… I’ll have to check on my G4 Powerbook and G3 iBook.
So far everyone reporting no problems has said they are running an intel processor, whereas those reporting the problem are neglecting to say what sort of machine they are running (always helpful when reporting a bug). It would be interesting to see if this is a PPC only bug.
I think it is PPC - I tested on my old iBook G4 and can recreate something similar. Still don’t understand it, though - am looking into it.
Best,
Keith