Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Quincey Morris
On Aug 24, 2011, at 19:24 , Graham Cox wrote: > I can't imagine how a palette would come into version browsing Admittedly I didn't spend a lot of time trying to find a convincing use case, but the example that sprang immediately to mind is if the palette is actually some kind of table of conten

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Jerry Krinock
On 2011 Aug 24, at 20:07, Graham Cox wrote: > Maybe my understanding is a little off here, but I'd assumed that the > versions "on the right side" were just snapshots (images) of the window > content rather than actual documents. Oh, I'd assumed that at first too. But in fact they are real in

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Graham Cox
On 25/08/2011, at 12:53 PM, Jerry Krinock wrote: > When user clicks "Browse All Versions", the current document window jumps to > the left side of the Star Wars screen. That document has "entered the > version browser". However, another document, the previous version, opens in > a window in

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Jerry Krinock
On 2011 Aug 24, at 18:45, Graham Cox wrote: > Can you explain what you mean by a document opening on the right hand side? I > can't seem to get that to happen. When user clicks "Browse All Versions", the current document window jumps to the left side of the Star Wars screen. That document has

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Graham Cox
On 25/08/2011, at 12:03 PM, Quincey Morris wrote: > As to why this isn't automatic, the answer is hinted at, earlier in the > video. The versions browser doesn't know what parts of your user interface > are necessary for interacting with the document window during version > browsing. It could

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Quincey Morris
On Aug 24, 2011, at 18:45 , Graham Cox wrote: > On 25/08/2011, at 11:28 AM, Jerry Krinock wrote: > >> We have NSWindowWillEnterVersionBrowserNotification and >> NSWindowDidExitVersionBrowserNotification, however I found the former is not >> received if a document *opens* on the right side of th

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Graham Cox
On 25/08/2011, at 11:28 AM, Jerry Krinock wrote: > We have NSWindowWillEnterVersionBrowserNotification and > NSWindowDidExitVersionBrowserNotification, however I found the former is not > received if a document *opens* on the right side of the version browser, i.e. > if the user "browses" to i

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Jerry Krinock
On 2011 Aug 24, at 17:17, Graham Cox wrote: > Can I get a notification that my app returned from browsing Versions (and is > entering Versions)? Terminology: "browsing versions" is called "viewing mode", as in "you can view but you can't edit". We have NSWindowWillEnterVersionBrowserNotificat

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Graham Cox
On 25/08/2011, at 10:17 AM, Graham Cox wrote: > Can I get a notification that my app returned from browsing Versions (and is > entering Versions)? I found the added window delegate methods that notify windows entering and leaving Versions. They are not called for my palettes. I like Versio

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Graham Cox
On 25/08/2011, at 1:44 AM, Kevin Perry wrote: > Right now, Versions doesn't bring back the inspectors automatically, but it > may do so in the future. For now, bringing them back manually is the right > thing. That's useless. Can I get a notification that my app returned from browsing Versio

Re: Odd error logged when coming back from 'Browse All Versions'

2011-08-24 Thread Kevin Perry
Hi Graham, Right now, Versions doesn't bring back the inspectors automatically, but it may do so in the future. For now, bringing them back manually is the right thing. As for the logging, it's a known OS bug, but is basically harmless. Thanks. On Aug 23, 2011, at 8:08 PM, Graham Cox wrote: >