[tslarkin]

I have managed to put together the code to create a tabbed inspector with the views I need. I have implemented the OIInspectableController protocol in one of the objects in the responder chain.

I don't, however, understand how to trigger the updating of the inspector contents. I tried [OIInspectorRegistry updateInspector], but this doesn't seem to do what I thought it should.

So what causes the inspection system to think that the selection has been changed?

[Tim Wood]

Calling +updateInspector should do the trick. Perhaps the update is breaking down further on (in the build of the inspection set in your inspectable controller or in the -inspectObjects: method on your inspector)?

[tslarkin]

There were two non-obvious things I had to do to get the inspector going. I added an Inspector menu with an menu item of type OIDynamicInspectorMenuItem, titled "Inspectors Placeholder". This caused my inspector windows to show up. Then I posted a OIInspectorSelectionDidChangeNotification whenever my application's selection changed. This keep the inspected object up to date.

[Tim Wood]

Creating the global inspector menu is definitely helpful (for the UI at least), but posting the notification should be optional. When that notification fires, OIInspectorRegistry will get called with:

- (void)_selectionMightHaveChangedNotification:(NSNo tification *)notification;
{
[self _inspectWindow:[NSApp mainWindow] queue:YES onlyIfVisible:YES updateInspectors:YES];
}

But, if you look at +updateInspector, it does the same thing (in fact, maybe one should call the other...).

Perhaps registering the menu item cause setup to happen earlier than it would have otherwise and that alone would be sufficient. Or perhaps some other change made the selection change code start firing.

Anyway, hopefully all is working well for you now! Thanks for the update!