1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>8.2. Using Plugins</title>
<link rel="stylesheet" href="gimp-help-plain.css" type="text/css" />
<link rel="stylesheet" href="gimp-help-screen.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.66.1" />
<link rel="start" href="index.html" title=" " />
<link rel="up" href="ch02s08.html" title="8. Plugins" />
<link rel="prev" href="ch02s08.html" title="8. Plugins" />
<link rel="next" href="ch02s08s03.html" title="8.3. Installing New Plugins" />
</head>
<body>
<div xmlns="" class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center" id="chaptername">8.2. Using Plugins</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="ch02s08.html">Prev</a> </td>
<th width="60%" align="center" id="sectionname">8.2. Using Plugins</th>
<td width="20%" align="right"> <a accesskey="n" href="ch02s08s03.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="id3315332"></a>8.2. Using Plugins</h3>
</div>
</div>
</div>
<p>
For the most part you can use a plugin like any other Gimp tool,
without needing to be aware that it is a plugin. But there are
a few things about plugins that are useful to understand.
</p>
<p>
One is that plugins are generally not as robust as the Gimp
core. When Gimp crashes, it is considered a very serious
thing: it can cost the user a lot of trouble and headache. When
a plugin crashes, the consequences are usually not so serious.
In most cases you can just continuing working without worrying
about it.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25">
<img alt="[Note]" src="../images/note.png" />
</td>
<th align="left">Note</th>
</tr>
<tr>
<td colspan="2" align="left" valign="top">
<p>
Because plugins are separate programs, they communicate with the
Gimp core in a special way: the Gimp developers call it
"talking over a wire". When a plugin crashes, the communication
breaks down, and you will see an error message about a "wire
read error".
</p>
</td>
</tr>
</table>
</div>
<div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;">
<table border="0" summary="Tip">
<tr>
<td rowspan="2" align="center" valign="top" width="25">
<img alt="[Tip]" src="../images/tip.png" />
</td>
<th align="left">Tip</th>
</tr>
<tr>
<td colspan="2" align="left" valign="top">
<p>
When a plugin crashes, Gimp gives you a very ominous-looking
message telling you that the plugin may have left Gimp in a
corrupted state, and you should consider saving your images and
exiting. Strictly speaking, this is quite correct, because
plugins have the power to alter almost anything in Gimp, but for
practical purposes, experience has shown that corruption is
actually quite rare, and many users just continue working and
don't worry about it. Our advice is that you simply think about
how much trouble it would cause you if something went wrong, and
weigh it against the odds.
</p>
</td>
</tr>
</table>
</div>
<p>
Because of the way plugins communicate with Gimp, they do not
have any mechanism for being informed about changes you make to
an image after the plugin has been started. If you start a
plugin, and then alter the image using some other tool, the
plugin will often crash, and when it doesn't will usually give a
bogus result. You should avoid running more than one plugin at
a time on an image, and avoid doing anything to the image until
the plugin has finished working on it. If you ignore this
advice, not only will you probably screw up the image, you will
probably screw up the undo system as well, so that you won't
even be able to recover from your foolishness.
</p>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="ch02s08.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="ch02s08.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="ch02s08s03.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">8. Plugins </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> 8.3. Installing New Plugins</td>
</tr>
</table>
</div>
</body>
</html>
|
