[Gimp-developer] internal representation of a selection
Hi, can somebody, please, point me to some information on how a selection is represented (internally) within Gimp and how one can access this. Is it represented by a matrix of bits? If the selection has many holes it's not sufficient to have a lower and upper bound for each pixel row. I need the selection exactly for my attempt at a new healing tool. Many thanks for a pointer, Helmut Jarausch. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] internal representation of a selection
On Friday 30 March 2007 13:10, Helmut Jarausch wrote: Hi, can somebody, please, point me to some information on how a selection is represented (internally) within Gimp and how one can access this. Is it represented by a matrix of bits? If the selection has many holes it's not sufficient to have a lower and upper bound for each pixel row. I need the selection exactly for my attempt at a new healing tool. Many thanks for a pointer, Hi Helmut - the selection is a matrix of bits, yes - a drawable object, with one byte per pixel, meaning the strenght of the selection at that point. the call gimp_image_get_selectin available for plug-ins can return you the selection as a drawable object. Through the UI you can simply enable the quickmask (click on the little square to the left of the hor. scroll bar on an image window), to transfer the selection to an editable image channel. js -- Helmut Jarausch. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] internal representation of a selection
Helmut Jarausch wrote: If the selection has many holes it's not sufficient to have a lower and upper bound for each pixel row. I need the selection exactly for my attempt at a new healing tool. It is good to have another person around who is interested in working on a healing tool for GIMP. Before you start, are you aware that a healing tool was added to the current development version of GIMP? It was created by Kevin Sookocheff as part of the 2006 Google Summer of Code program. The healing tool has a couple of bugs filed against it. You may find your time would be better spent fixing and polishing the existing healing tool instead of starting a new one. On the other hand, if you have an idea for a different or better approach to a healing tool that what is in the current development release, I'm sure the GIMP developers would be interested to hear about your ideas for a new version of a healing tool. -- Cheers! Kevin. http://www.ve3syb.ca/ |What are we going to do today, Borg? Owner of Elecraft K2 #2172 |Same thing we always do, Pinkutus: | Try to assimilate the world! #include disclaimer/favourite | -Pinkutus the Borg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [Gimp-Developer] One-click binary downloads via the gimp website
Sven Neumann wrote: In my opinion we should stick to this rule. It would make a lot of sense to make it easier for the user to locate our recommendations for binary packages. If user agent detection helps to remove one or two clicks, then I am fine with that. But if there's a download button on the front-page that directly instantiates the download, then we are effectively providing binary packages. It doesn't matter if the packages are hosted elsewhere. To the user it will appear as if we would provide the binaries. I think opening in a new window/tab would be a strong indication that the user is leaving the gimp site. Whether or not I agree with linking to direct downloads will depend a lot on how fool proof and reliable the said binary turns out to be. But if it does (as I'm sure it will) turn out to be solid, then I don't really see a problem. Otherwise, I agree that cutting down on clicks is still a good compromise. We already get Gimpshop users coming to the mailing lists asking for help and, far from being linked to, I don't think it's even mentioned on the website, so I'm not sure the support thing is really in issue. You could paint it in red letters on the front of the website and someone won't read them. At the end of the day, we can always remove the links if they turn out to cause a problem. Davidm ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
