After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 68281 - No PDB entries for Intelligent Scissors
No PDB entries for Intelligent Scissors
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: libgimp
git master
Other All
: Normal enhancement
: Future
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks: 101604
 
 
Reported: 2002-01-09 00:58 UTC by trefftzs
Modified: 2018-05-24 10:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description trefftzs 2002-01-09 00:58:22 UTC
I have searched in vain for PDB entries for both the Bezier 
Select and the Intelligent Scissors.  Checking the source 
reveals that there are, indeed, no such entries.  Is this 
intentional?  If not, could someone with a whole lot more 
experience in hacking the GIMP itself make the proper entries?  
I'm using GIMP-1.2.2 on Linux (RH-6.1) GIMP installed from the 
tarball.

Is this part of the HELP system, Script-Fu, or the User Interface?  Or even
the tools?

Sven suggested I post this bug report so it will be fixed in 1.4.

Thanks.
Comment 1 Raphaël Quinet 2002-01-09 08:08:21 UTC
There are several features in the GIMP that cannot be called from the
PDB.  This is a bug.  Solving this would also solve a part of bug
#51397 (implementing a macro recorder requires that most actions go
through the PDB).
Comment 2 Raphaël Quinet 2002-01-09 08:09:39 UTC
Oops!  Typo...  This should have been bug #51937, not 51397.  Sorry.
Comment 3 Austin Donnelly 2003-07-25 09:10:58 UTC
It's not clear what a PDB entry for these tools would look like, 
since they are interactive tools.  They take a series of control 
points, and generate a selection based on them.  Maybe the PDB API 
should take a list of (x,y) co-ordinates and modify the current 
selection?

I'm bumping this to milestone 2.0, but perhaps it would be best set 
to Future.
Comment 4 Sven Neumann 2003-07-25 09:21:43 UTC
I don't think it makes much sense to expose this functionality to the
PDB. The control points would have to be choosen interactively anyway.
Comment 5 Raphaël Quinet 2003-12-09 07:57:53 UTC
If the macro recorder works by intercepting PDB calls (instead of
having to insert multiple callbacks in various parts of the core), then
there should be some way to generate PDB calls from the interactive
tools.  Otherwise, some interactive actions would not be recordable.
Comment 6 Kevin Cozens 2004-12-11 01:42:47 UTC
There are other features that normally require user interaction to specify a set
of points to be used. I believe gimp-free-select is one example. There is no
reason why a gimp_bezier_select PDB call couldn't be added that would take a
list of control points in a passed array. I'm not sure what parameters one would
need to pass to intelligent scissors but an array of points could be passed if
needed.

Probably too late to do this for 2.2 but it could be put on the list for the 2.4
version of GIMP.
Comment 7 Joao S. O. Bueno 2004-12-11 03:05:47 UTC
gimp-path-set-points 
 
Actually, since gimp 2.0, the pdb-entries dealing with paths are faulty and 
incomplete, since the new modle is able to do more than the previous one. 
 
But this function allows making a single closed, or even several closed, and a 
single open component of a path - or 'bezier select', if one is not looking at 
the paths dialog. 
 
For gimp 2.4 we should have a long-delayed API for dealing with the new paths, 
and this bug should be properly addressed therein. 
 
As for comment #4 - I had actually used it to transform paths in a script - 
creating a new path with transformations of each point on a source path. 
Comment 8 Sven Neumann 2005-03-08 12:40:36 UTC
The new vectors PDB API is dealt with in bug #129598. Let's concentrate on the
IScissors in this report. Changing the summary accordingly.
Comment 9 GNOME Infrastructure Team 2018-05-24 10:39:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/16.