Jim,

I'm using 1.2.0(47) and this morning, I tried to use the 'Reveal in QRecall Archive' service. It took me to the archive, but what was displayed is shown in the screenshot attachment.

I've been able to get certain portions of the display to show up by choosing different viewing methods, but never will all of the items be present at once. For instance, when I first got the blank screen, I tried a repair of the archive. After the repair was finished (not showing any problems), the layers were visible, but not the contents. After closing the archive window and reopening it, I then saw the contents, but not the layers. Clicking on the 'View deleted items' menu item caused a crash, that I sent a report in about.

Here's some console log items that might help:


10/6/11 11:25:35.152 AM com.apple.launchd.peruser.501: ([0x0-0xb80b8].com.qrecall.client[4757]) Job appears to have crashed: Segmentation fault: 11
10/6/11 11:25:37.087 AM ReportCrash: Saved crash report for QRecall[4757] version 1.2.0[47] beta (1.2.0.47) to /Users/smayer/Library/Logs/DiagnosticReports/QRecall_2011-10-06-112537_Spawn.crash
10/6/11 11:25:49.175 AM QRecall: CALayer position contains NaN: [14 nan]
10/6/11 11:25:49.177 AM QRecall: CALayer position contains NaN: [14 nan]
10/6/11 11:25:49.195 AM QRecall: CALayer position contains NaN: [14 nan]
10/6/11 11:25:49.195 AM QRecall: CALayer position contains NaN: [14 nan]
10/6/11 11:25:49.354 AM QRecall: CALayer position contains NaN: [14 nan]
10/6/11 11:25:49.354 AM QRecall: CALayer position contains NaN: [14 nan]
10/6/11 11:25:49.766 AM QRecall: *** Assertion failure in -[TimelineLayer drawInContext:], /Users/james/Development/Projects/Quantum Recall/Client/Source/Browser/Timeline/TimelineLayer.m:233
10/6/11 11:25:49.767 AM QRecall: historyRowCount==0
10/6/11 11:25:49.769 AM QRecall: (
0 CoreFoundation 0x00007fff88a9d986 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff88859d5e objc_exception_throw + 43
2 CoreFoundation 0x00007fff88a9d7ba +[NSException raise:format:arguments:] + 106
3 Foundation 0x00007fff8b78914f -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 169
4 QRecall 0x00000001000f5d1e QRecall + 1006878
5 QuartzCore 0x00007fff882a1249 CABackingStoreUpdate_ + 3221
6 QuartzCore 0x00007fff882a0158 _ZN2CA5Layer8display_Ev + 1086
7 QuartzCore 0x00007fff88297e68 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 560
8 QuartzCore 0x00007fff88296e1b _ZN2CA7Context18commit_transactionEPNS_11TransactionE + 319
9 QuartzCore 0x00007fff88296b98 _ZN2CA11Transaction6commitEv + 274
10 QRecall 0x00000001000f7ae6 QRecall + 1014502
11 QRecall 0x00000001000dd97d QRecall + 907645
12 Foundation 0x00007fff8b6d4716 __-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_1 + 47
13 CoreFoundation 0x00007fff88a4651a _CFXNotificationPost + 2634
14 Foundation 0x00007fff8b736094 postQueueNotifications + 802
15 CoreFoundation 0x00007fff88a5d647 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
16 CoreFoundation 0x00007fff88a5d5a6 __CFRunLoopDoObservers + 374
17 CoreFoundation 0x00007fff88a32976 __CFRunLoopRun + 1062
18 CoreFoundation 0x00007fff88a32216 CFRunLoopRunSpecific + 230
19 HIToolbox 0x00007fff876e04ff RunCurrentEventLoopInMode + 277
20 HIToolbox 0x00007fff876e7c21 ReceiveNextEventCommon + 355
21 HIToolbox 0x00007fff876e7aae BlockUntilNextEventMatchingListInMode + 62
22 AppKit 0x00007fff8bdc5191 _DPSNextEvent + 659
23 AppKit 0x00007fff8bdc4a95 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
24 AppKit 0x00007fff8bdc13d6 -[NSApplication run] + 463
25 AppKit 0x00007fff8c03f52a NSApplicationMain + 867
26 QRecall 0x0000000100001aa4 QRecall + 6820
)

I specifically noted the path that must have come from one of your machines for the TimelineLayer.m entry.

Thanks,

Steve

Steve,

There were a couple of subtle Lion-related bugs in the browser interface. I've plugged a couple of them. I don't know if I've gotten them all, but I can no longer reproduce what you reported (both here and in the diagnostic reports you sent).

One thing I did discover is that Lion has broken a number of QRecall features:

The Reveal in QRecall Archive service

The Capture to QRecall Archive service

Searching for an item by opening an archive from a Spotlight search

All of these features depend on information being passed to the application via AppleEvents (the technology on which AppleScripts is built on). In Lion, none of this information is getting passed to the application.

I'm looking into this situation now.

Thanks for the info James! And for getting these little issues taken care of.

Steve