Re: BonoboDockLayout and ref/sink



        To get rid of this, you could:
        
         A) Make it derive from GObject instead
         B) Make it ref/sink itself.
        
        Either way would be an API change, since you theoretically should have
        _always_ have called ref/sink on it, and A) would make that an error
        and B) would make that a memory leak.
        
        So, I suspect that there isn't much that can be done about it now,
        but I thought I'd point out the issue. (Just fixed GnomeApp to
        do the ref/sink.)
    
      Sigh.  Since only the libraries themselves use BonoboDockLayout and
    the change is trivial, I'd really rather have it fixed than keep it
    broken like this.

  So, what is the story with this?  Do we leave it broken?

-- 
Ettore



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]