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 159686 - IWarp plugin preview zoom and scroll
IWarp plugin preview zoom and scroll
Status: RESOLVED DUPLICATE of bug 162014
Product: GIMP
Classification: Other
Component: Plugins
unspecified
Other Windows
: Low enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-11-28 03:27 UTC by bigmtnskier89
Modified: 2004-12-23 00:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description bigmtnskier89 2004-11-28 03:27:40 UTC 
There really needs to be zoom and scroll functionability on the preview image 
for a plugin that has a preview (ex. iwarp) It is impossible currently to use 
iwarp precisionly because the preview is resisized smaller so you cannot 
manipulate fine details.
Comment 1 Sven Neumann 2004-11-28 11:13:54 UTC 
IWarp still uses the old preview and it should actually be merged into the core
as a brush. Having this functionality in a plug-in is useless.
Comment 2 Pavel Antokolsky aka Zigmar 2004-12-22 18:51:50 UTC 
It would be a grate if the this plug-in will be usable as brush. For example, I 
miss the option of seeing actual brush size, when doin iwarp. But is it a good 
idea to merge it completely into a core? Working on large image would be slow, 
and will require huge undo history - wrapping usually consists of many 
"strokes", that create the final image. I think it should look somehow like gfig 
looks now - an editor inside editor. 

BTW, I recently intalled Photoshop, to compare it to Gimp, and found out that 
the photoshop's analog of IWrap (don't remember the name) - is also implemented 
in such approach - and "editor inside editor".
Comment 3 weskaggs 2004-12-22 21:34:38 UTC 

*** This bug has been marked as a duplicate of 162014 ***
Comment 4 Sven Neumann 2004-12-23 00:16:46 UTC 
The plug-in is supposed to die and to be replaced by a tool in the core.