I've committed some pretty heavy restructuring (although it's almost all
just moving code around) and now we have a real per-window structure for
the addressbook. This fixes lots of issues (status showing up in
multiple windows, for instance), and allows the info label to actually
show
What about just adding an id to the activate function? Since this is already called per-window.
On Wed, 2004-04-14 at 19:25 -0700, Chris Toshok wrote:
I've committed some pretty heavy restructuring (although it's almost all
just moving code around) and now we have a real per-window
isn't the activate() method a bonobo thing? Even still - if you have
two windows up you'll get two activate() calls with different id's. the
component needs a way to determine which window had the New... button
clicked.
It's sad that this can't somehow be handled by the
No, its just a local call. The user creatable items handler is created once for each component (or view, depending on how you'e done it). Each one does a bonobo query to find out which components are available and each one does a query to find out which items are available.
I'm talking about
