Scrivener 2.0 "Links…" malfunction

bryankbrown · October 26, 2010, 4:32pm

When I select text in my Scrivener document, then choose Links… from the Edit menu, nothing happens. I don’t even get a smirk—it just ignores me.

Did someone forget to wire up the power to that command, or am I missing something?

This happens using the pre-release version of Scrivener 2.0.

Hugh · October 26, 2010, 4:40pm

Mysterious – it works for me. Edit > Link, and a dialogue box comes down asking for the name and type of the destination. Anything unusual about the way you’re selecting the text?

KB · October 26, 2010, 4:42pm

Could you please open the Console (~/Applications/Utilities/Console.app) and watch it as you select “Links…”? Then let me know if it spews an error. It sounds like a bug whereby an error is getting thrown - it’s certainly hooked up.
Thanks,
Keith

bryankbrown · October 26, 2010, 4:52pm

Keith,

When I do as you suggested, Console reports the following error after selecting Link… from the Edit menu while document text is selected:

2010-10-26 09:49:31.722 Scrivener[377] *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class (NSCoreUIImageRep)

bryankbrown · October 26, 2010, 4:59pm

More errors:

===== Tuesday, October 26, 2010 9:49:12 AM US/Pacific =====
2010-10-26 09:49:31.722 Scrivener[377] *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class (NSCoreUIImageRep)
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:53:59 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
Oct 26 09:54:00 BKB-PowerBook Scrivener: __CGPixelAccessLockWindowAccess: access lock failed: error 1001.
2010-10-26 09:56:38.676 GrowlHelperApp[242] Auto-discovered registration ticket in Scrivener (located at /Applications/Scrivener.app)
2010-10-26 09:57:25.838 Scrivener[665] *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class (NSCoreUIImageRep)

KB · October 26, 2010, 6:20pm

Curious. Try trashing your preferences (move ~/Library/Preferences/com.literatureandlatte.scrivener2.plist to the Trash) with Scrivener closed and restarting.
Best,
Keith

bryankbrown · October 26, 2010, 10:02pm

The problem persists even after quitting, trashing the preferences, and then restarting.

KB · October 26, 2010, 11:07pm

Okay, I think I’ve got to the bottom of this one. From searching the developer boards (okay, Google), it turns out that there’s an odd but in Interface Builder (the tool used for building interface files in OS X) whereby if a certain control type is shrunk to small size, it won’t work on Tiger. I’ve fixed it (hopefully) simply by resizing the control. Very odd.
All the best,
Keith

bryankbrown · October 26, 2010, 11:29pm

Does that mean you will have the problem fixed for the version you are officially releasing next Monday (11/1)? Or do you mean that the current pre-release build will be fixed, and I just need to re-download it now? Tomorrow?

KB · October 26, 2010, 11:48pm

The one next Monday.
Best,
Keith