Hi,
I saw that since the "custom displaypicture" feature was patched in, the dp-selector (window you get when you want to change your dp or set a custom one for a contact) has a memleak. For every contact I select, an image is created that's never deleted. I wanted to fix this immediately as it's quite easy (after a selection, delete the previous selected temporary image), but I have another codebase over here as I was doing some funky stuff with the dpbrowser widget. Mainly, I created a new snit widget that can represent files in a (if we would ever create one) filebrowser window, or, represent dp's in a dpbrowser. It can now also create "tiles" as used troughout Suse Linux Enterprise Desktop or in the newer (not yet default) gnome-menu implementations, they are like some kind of buttons with an icon on the left and text on the right to launch applications or open recent documents (I'll screenshots on demand). WIth some little tweaks, this widget could also be used as a checkbutton or sleector button in a preference window ala firefox's, or also to (but I guess there's not as much interest in this) create fully skinnable buttons. Now, in my local copy, I already have the dpbrowser use this widget (for those interested, it's named "sexytile"). It still needs some code though. Right now it works for choosing your own dp (without memleak ;)) and to set a custom dp (memleak not fixed here at this same moment). A little work is needed for the use in the "cached dps" tab on a user properties window as I don't want it to use the implementation we have now with the menu but with a dpbrowser on the left, you select a pic, and then press one of the buttons on the right (that are not yet created) A (is-this-gonna-make-me-famous?) ASCII-mockup: +-------------------------------------------- |Current dp: |+-----+ || * * | || - | |+-----+ | |Other dps of this contact: | |+------------------+ Actions: || here a dpbrowser | ------- || widget | [Set as my dp] || | [set as custom blah..] || | [copy file location] || | || | || | |+------------------+ +---------------------------------------------------- (optimised for a fixed sized font ;)) So, what I wanted to say/asks in fact; What should I do, * upload my code so I'm not the only one taming this beast (the "release early, release often" way) and it will be implemented sooner with your help. * stop smoking the wrong herbs and thinking of yet another snit widget, though I think it makes everything more flexible and coder-friendlier and thus less bug-prone and memleak-prone (Everyone has to learn, nothing personal if Christofaro (wasn't it his contribution) did this, I made more memleaks before, that's for sure (and this last sentence rhymes !) * keep my code for now, try to fill the gaps while I should be studying for my law exams and only upload when finished so all credits are for me (ego-centricism (is this english ?) is typical for Gnome-users, no ?) but problems if the svn codebase is changed too much * yet another option I forgot ? Feel free to answer honestly, Karel. PS: I don't do drugs... no, I really don't ... I mean it! ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
