On 24 May 2012 07:37, Gino D wrote:

Hi.

I'm searching for the Script-Fu procedure corresponding to the "Merge Visible Paths" widget available in the "Path" context menu, but so far I have been able neither to find it nor to devise a way to do the same by using other procedures.

Have I missed something? Or the reason is that the Procedure Database doesn't currently provide this unique command yet? If so, is there anyone who can suggest or at least draft me a code snippet aimed to implement the aforesaid operation?

Indeed - there are no vectors merging calls whatsoever on the PDB - for the time being, the only way to merge vectors using a script or plug-on is to explictly adding strokes read from other vectors to another vector. (using gimp-vectors-stroke-new-from-points ).

Coding an algorithm that loops through an image vectors, cehck which are visible, and for each visible vectors object, read its strokes, and add them to the target vectors is the way to go. Other, higher level languages, can make this task easier than in scheme - like Python.

On the other hand, indeed, there should be some support for that on the PDB - could you open a bug at https://bugzilla.gnome.org/ asking for this feature?
Maybe you could even come to do some work on its developement on a nearby future, in order for it to be in gimp 2.10.

js ->

Thanks in advance.
_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

On 05/24/2012 04:05 PM, Joao S. O. Bueno wrote:

Indeed - there are no vectors merging calls whatsoever on the PDB - for the time being, the only way to merge vectors using a script or plug-on is to explictly adding strokes read from other vectors to another vector. (using gimp-vectors-stroke-new-from-points ). Coding an algorithm that loops through an image vectors, cehck which are visible, and for each visible vectors object, read its strokes, and add them to the target vectors is the way to go. Other, higher level languages, can make this task easier than in scheme - like Python.

Indeed, this is a piece of cake/SMOP in Python.

On the other hand, indeed, there should be some support for that on the PDB - could you open a bug at https://bugzilla.gnome.org/ asking for this feature? Maybe you could even come to do some work on its developement on a nearby future, in order for it to be in gimp 2.10. js ->

If the PBD emulates the current "manual" version (all paths are replaced by a single, merged one) scripts will often have to copy the paths first, so we are back to square one :)

On 25/05/2012 22.28, Ofnuts wrote:

I developped my first python scripts on Windows, but I must say that switching to Linux (which I did for other reasons) greatly eased this kind of work. In your first runs you weed out the synatx errors, but if you run the script directly in Gimp you won't see much since the syntax errors will even prevent it from registering... Take the habit to run the script outside of Gimp; "python your_plugin.py" in a command prompt, if you have blatant syntax errors they will show then and be a lot easier to fix. You can move to Gimp when it only complains about importing "gimpfu" (if it gets this far the syntax is OK).

That's interesting. I will bear these suggestions in mind. Thank you again.