Sync SIGNALS doc after style updates
This commit is contained in:
Bill Kendrick
parent
799670ac24
commit
084adab616
10 changed files with 689 additions and 351 deletions
|
|
@ -5,9 +5,7 @@
|
|||
Copyright © 2019-2022 by various contributors; see AUTHORS.txt.
|
||||
https://tuxpaint.org/
|
||||
|
||||
January 20, 2022
|
||||
|
||||
----------------------------------------------------------------------
|
||||
March 31, 2022
|
||||
|
||||
Tux Paint responds to the following signals (which can be sent to the
|
||||
program's process via `kill` or `killall`, for example).
|
||||
|
|
@ -27,13 +25,13 @@
|
|||
respectively), whether or not to overwrite the existing drawing,
|
||||
or save to a new file.
|
||||
|
||||
Note: From other parts of the interface, the signal is currently
|
||||
Example: killall tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, the signal is currently
|
||||
interpreted as a request to go back (e.g., from the "New" dialog
|
||||
back to the main interface), as if a "Back" button in Tux Paint
|
||||
were clicked, or the [Esc] was key pressed.
|
||||
|
||||
Example: killall tuxpaint
|
||||
|
||||
SIGUSR1 & SIGUSR2
|
||||
|
||||
Tux Paint responds by setting its auto-save option (as if it had
|
||||
|
|
@ -47,9 +45,9 @@
|
|||
So, from the main interface, Tux Paint should quit almost
|
||||
immediately, with no questions asked.
|
||||
|
||||
Note: From other parts of the interface, unfortunately, Tux Paint
|
||||
will go back one level in the interface. Therefore, at this time,
|
||||
it may be necessary to send this signal to Tux Paint a few times,
|
||||
for it to quit completely.
|
||||
|
||||
Example: killall -s SIGUSR1 tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, unfortunately, Tux
|
||||
Paint will go back one level in the interface. Therefore, at this
|
||||
time, it may be necessary to send this signal to Tux Paint a few
|
||||
times, for it to quit completely.
|
||||
|
|
|
|||
|
|
@ -5,13 +5,81 @@
|
|||
Tux Paint Signals Documentation </title>
|
||||
<meta http-equiv="Content-Type"
|
||||
content="text/html; charset=utf-8">
|
||||
<style>
|
||||
body { font-size: large; }
|
||||
table { font-size: large; }
|
||||
div.screenshot-center {
|
||||
text-align: center;
|
||||
}
|
||||
div.screenshot-right {
|
||||
float: right;
|
||||
margin-left: 1em;
|
||||
margin-bottom: 1em;
|
||||
}
|
||||
div.screenshot-right-after {
|
||||
clear: both;
|
||||
}
|
||||
div.keeptogether { page-break-inside: avoid; }
|
||||
section h1 { font-size: 2em; }
|
||||
h1, h2, h3, h4 { font-family: sans; }
|
||||
h1 { color: #800; page-break-before: always; break-before: always; }
|
||||
h2 { color: #440; page-break-after: avoid; break-after: avoid; }
|
||||
h3 { color: #080; page-break-after: avoid; break-after: avoid; }
|
||||
h4 { color: #008; page-break-after: avoid; break-after: avoid; }
|
||||
h1 + p { page-break-inside: avoid; }
|
||||
h2 + p { page-break-inside: avoid; }
|
||||
h3 + p { page-break-inside: avoid; }
|
||||
h4 + p { page-break-inside: avoid; }
|
||||
dt {
|
||||
font-size: large;
|
||||
color: #404;
|
||||
font-family: sans;
|
||||
margin-top: 1em;
|
||||
margin-bottom: 0.25em;
|
||||
}
|
||||
dd, blockquote {
|
||||
border-left: 1px solid #888;
|
||||
padding-left: 1em;
|
||||
border-radius: 0 0 0 1em;
|
||||
}
|
||||
p.note {
|
||||
border: 1px solid #000;
|
||||
background-color: #eee;
|
||||
border-radius: 0.5em;
|
||||
padding: 0.5em;
|
||||
display: inline-block;
|
||||
margin-right: 3em;
|
||||
}
|
||||
section.outer {
|
||||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
margin-left: 0;
|
||||
}
|
||||
p + ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
@media print {
|
||||
p {
|
||||
orphans: 3;
|
||||
widows: 3;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
<body bgcolor="#FFFFFF"
|
||||
text="#000000"
|
||||
link="#0000FF"
|
||||
vlink="#FF0000"
|
||||
alink="#FF00FF">
|
||||
<section class="outer">
|
||||
<center>
|
||||
<header>
|
||||
<h1>
|
||||
<img src="../../html/images/tuxpaint-title.png"
|
||||
width="205"
|
||||
|
|
@ -26,11 +94,12 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
January 20, 2022 </p>
|
||||
March 31, 2022 </p>
|
||||
</header>
|
||||
</center>
|
||||
</section>
|
||||
|
||||
<hr>
|
||||
|
||||
<section>
|
||||
<p>
|
||||
Tux Paint responds to the following signals (which can be sent to the program's process via `<code>kill</code>` or `<code>killall</code>`, for example). </p>
|
||||
|
||||
|
|
@ -46,11 +115,11 @@
|
|||
<p>
|
||||
From the main interface, Tux Paint will prompt whether or not you wish to quit, and (unless overridden by the auto-save option, e.g. "<code>--autosave</code>") if you'd like to save the current drawing (if unsaved), and if so, and it's a modified version of an existing drawing (unless overridden by the options to save over old images, or always save new images; e.g. "<code>--saveover</code>" and "<code>--saveovernew</code>", respectively), whether or not to overwrite the existing drawing, or save to a new file. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
|
||||
|
||||
<p>
|
||||
Example: <code>killall tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
|
||||
</dd>
|
||||
|
||||
<dt>
|
||||
|
|
@ -64,12 +133,13 @@
|
|||
<p>
|
||||
So, from the main interface, Tux Paint should quit almost immediately, with no questions asked. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
|
||||
|
||||
<p>
|
||||
Example: <code>killall -s SIGUSR1 tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
|
||||
</dd>
|
||||
</dl>
|
||||
</section>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -5,9 +5,7 @@
|
|||
Copyright © 2019-2022 by various contributors; see AUTHORS.txt.
|
||||
https://tuxpaint.org/
|
||||
|
||||
enero 20, 2022
|
||||
|
||||
----------------------------------------------------------------------
|
||||
marzo 31, 2022
|
||||
|
||||
Tux Paint responds to the following signals (which can be sent to the
|
||||
program's process via `kill` or `killall`, for example).
|
||||
|
|
@ -27,13 +25,13 @@
|
|||
respectively), whether or not to overwrite the existing drawing,
|
||||
or save to a new file.
|
||||
|
||||
Note: From other parts of the interface, the signal is currently
|
||||
Example: killall tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, the signal is currently
|
||||
interpreted as a request to go back (e.g., from the "New" dialog
|
||||
back to the main interface), as if a "Back" button in Tux Paint
|
||||
were clicked, or the [Esc] was key pressed.
|
||||
|
||||
Example: killall tuxpaint
|
||||
|
||||
SIGUSR1 & SIGUSR2
|
||||
|
||||
Tux Paint responds by setting its auto-save option (as if it had
|
||||
|
|
@ -47,9 +45,9 @@
|
|||
So, from the main interface, Tux Paint should quit almost
|
||||
immediately, with no questions asked.
|
||||
|
||||
Note: From other parts of the interface, unfortunately, Tux Paint
|
||||
will go back one level in the interface. Therefore, at this time,
|
||||
it may be necessary to send this signal to Tux Paint a few times,
|
||||
for it to quit completely.
|
||||
|
||||
Example: killall -s SIGUSR1 tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, unfortunately, Tux
|
||||
Paint will go back one level in the interface. Therefore, at this
|
||||
time, it may be necessary to send this signal to Tux Paint a few
|
||||
times, for it to quit completely.
|
||||
|
|
|
|||
|
|
@ -5,13 +5,81 @@
|
|||
Tux Paint Signals Documentation </title>
|
||||
<meta http-equiv="Content-Type"
|
||||
content="text/html; charset=utf-8">
|
||||
<style>
|
||||
body { font-size: large; }
|
||||
table { font-size: large; }
|
||||
div.screenshot-center {
|
||||
text-align: center;
|
||||
}
|
||||
div.screenshot-right {
|
||||
float: right;
|
||||
margin-left: 1em;
|
||||
margin-bottom: 1em;
|
||||
}
|
||||
div.screenshot-right-after {
|
||||
clear: both;
|
||||
}
|
||||
div.keeptogether { page-break-inside: avoid; }
|
||||
section h1 { font-size: 2em; }
|
||||
h1, h2, h3, h4 { font-family: sans; }
|
||||
h1 { color: #800; page-break-before: always; break-before: always; }
|
||||
h2 { color: #440; page-break-after: avoid; break-after: avoid; }
|
||||
h3 { color: #080; page-break-after: avoid; break-after: avoid; }
|
||||
h4 { color: #008; page-break-after: avoid; break-after: avoid; }
|
||||
h1 + p { page-break-inside: avoid; }
|
||||
h2 + p { page-break-inside: avoid; }
|
||||
h3 + p { page-break-inside: avoid; }
|
||||
h4 + p { page-break-inside: avoid; }
|
||||
dt {
|
||||
font-size: large;
|
||||
color: #404;
|
||||
font-family: sans;
|
||||
margin-top: 1em;
|
||||
margin-bottom: 0.25em;
|
||||
}
|
||||
dd, blockquote {
|
||||
border-left: 1px solid #888;
|
||||
padding-left: 1em;
|
||||
border-radius: 0 0 0 1em;
|
||||
}
|
||||
p.note {
|
||||
border: 1px solid #000;
|
||||
background-color: #eee;
|
||||
border-radius: 0.5em;
|
||||
padding: 0.5em;
|
||||
display: inline-block;
|
||||
margin-right: 3em;
|
||||
}
|
||||
section.outer {
|
||||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
margin-left: 0;
|
||||
}
|
||||
p + ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
@media print {
|
||||
p {
|
||||
orphans: 3;
|
||||
widows: 3;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
<body bgcolor="#FFFFFF"
|
||||
text="#000000"
|
||||
link="#0000FF"
|
||||
vlink="#FF0000"
|
||||
alink="#FF00FF">
|
||||
<section class="outer">
|
||||
<center>
|
||||
<header>
|
||||
<h1>
|
||||
<img src="../../html/images/tuxpaint-title.png"
|
||||
width="205"
|
||||
|
|
@ -26,11 +94,12 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
enero 20, 2022 </p>
|
||||
marzo 31, 2022 </p>
|
||||
</header>
|
||||
</center>
|
||||
</section>
|
||||
|
||||
<hr>
|
||||
|
||||
<section>
|
||||
<p>
|
||||
Tux Paint responds to the following signals (which can be sent to the program's process via `<code>kill</code>` or `<code>killall</code>`, for example). </p>
|
||||
|
||||
|
|
@ -46,11 +115,11 @@
|
|||
<p>
|
||||
From the main interface, Tux Paint will prompt whether or not you wish to quit, and (unless overridden by the auto-save option, e.g. "<code>--autosave</code>") if you'd like to save the current drawing (if unsaved), and if so, and it's a modified version of an existing drawing (unless overridden by the options to save over old images, or always save new images; e.g. "<code>--saveover</code>" and "<code>--saveovernew</code>", respectively), whether or not to overwrite the existing drawing, or save to a new file. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
|
||||
|
||||
<p>
|
||||
Example: <code>killall tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
|
||||
</dd>
|
||||
|
||||
<dt>
|
||||
|
|
@ -64,12 +133,13 @@
|
|||
<p>
|
||||
So, from the main interface, Tux Paint should quit almost immediately, with no questions asked. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
|
||||
|
||||
<p>
|
||||
Example: <code>killall -s SIGUSR1 tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
|
||||
</dd>
|
||||
</dl>
|
||||
</section>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -5,9 +5,7 @@
|
|||
Copyright © 2019-2022 by divers contributeurs; see AUTHORS.txt.
|
||||
https://tuxpaint.org/
|
||||
|
||||
janvier 20, 2022
|
||||
|
||||
----------------------------------------------------------------------
|
||||
mars 31, 2022
|
||||
|
||||
Tux Paint répond aux signaux suivants (qui peuvent être envoyé au
|
||||
processus du programme via `kill` ou`killall`, par exemple).
|
||||
|
|
@ -28,14 +26,13 @@
|
|||
sauvegarder avec un nouveau nom (par ex. "--saveover" ou
|
||||
"--saveovernew") vers un nouveau fichier.
|
||||
|
||||
Remarque :Sur d'autres parties de l'interface, le signal est en
|
||||
fait interprété comme une demande de retour en arrière (par
|
||||
exemple, de la boîte de dialogue "Nouveau" pour revenir sur
|
||||
l'interface principale), comme si un bouton "Retour" dans Tux
|
||||
Paint a été cliqué, ou la touche [Esc] enfoncée.
|
||||
|
||||
Exemple: killall tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, the signal is currently
|
||||
interpreted as a request to go back (e.g., from the "New" dialog
|
||||
back to the main interface), as if a "Back" button in Tux Paint
|
||||
were clicked, or the [Esc] was key pressed.
|
||||
|
||||
SIGUSR1 & SIGUSR2
|
||||
|
||||
Tux Paint répond en définissant son option "autosave" (comme si
|
||||
|
|
@ -50,10 +47,9 @@
|
|||
Ainsi, à partir de l'interface principale, Tux Paint devrait se
|
||||
fermer presque immédiatement, sans poser de questions.
|
||||
|
||||
À partir d'autres parties de l'interface, malheureusement, Tux
|
||||
Paint ne reviendra que d'un niveau dans l'interface. Par
|
||||
conséquent, à ce moment, il peut être nécessaire d'envoyer ce
|
||||
signal à Tux Paint plusieurs fois pour qu'il s'arrête
|
||||
complètement.
|
||||
|
||||
Exemple: killall -s SIGUSR1 tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, unfortunately, Tux
|
||||
Paint will go back one level in the interface. Therefore, at this
|
||||
time, it may be necessary to send this signal to Tux Paint a few
|
||||
times, for it to quit completely.
|
||||
|
|
|
|||
|
|
@ -5,13 +5,81 @@
|
|||
Documentation sur les signaux pour Tux Paint </title>
|
||||
<meta http-equiv="Content-Type"
|
||||
content="text/html; charset=utf-8">
|
||||
<style>
|
||||
body { font-size: large; }
|
||||
table { font-size: large; }
|
||||
div.screenshot-center {
|
||||
text-align: center;
|
||||
}
|
||||
div.screenshot-right {
|
||||
float: right;
|
||||
margin-left: 1em;
|
||||
margin-bottom: 1em;
|
||||
}
|
||||
div.screenshot-right-after {
|
||||
clear: both;
|
||||
}
|
||||
div.keeptogether { page-break-inside: avoid; }
|
||||
section h1 { font-size: 2em; }
|
||||
h1, h2, h3, h4 { font-family: sans; }
|
||||
h1 { color: #800; page-break-before: always; break-before: always; }
|
||||
h2 { color: #440; page-break-after: avoid; break-after: avoid; }
|
||||
h3 { color: #080; page-break-after: avoid; break-after: avoid; }
|
||||
h4 { color: #008; page-break-after: avoid; break-after: avoid; }
|
||||
h1 + p { page-break-inside: avoid; }
|
||||
h2 + p { page-break-inside: avoid; }
|
||||
h3 + p { page-break-inside: avoid; }
|
||||
h4 + p { page-break-inside: avoid; }
|
||||
dt {
|
||||
font-size: large;
|
||||
color: #404;
|
||||
font-family: sans;
|
||||
margin-top: 1em;
|
||||
margin-bottom: 0.25em;
|
||||
}
|
||||
dd, blockquote {
|
||||
border-left: 1px solid #888;
|
||||
padding-left: 1em;
|
||||
border-radius: 0 0 0 1em;
|
||||
}
|
||||
p.note {
|
||||
border: 1px solid #000;
|
||||
background-color: #eee;
|
||||
border-radius: 0.5em;
|
||||
padding: 0.5em;
|
||||
display: inline-block;
|
||||
margin-right: 3em;
|
||||
}
|
||||
section.outer {
|
||||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
margin-left: 0;
|
||||
}
|
||||
p + ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
@media print {
|
||||
p {
|
||||
orphans: 3;
|
||||
widows: 3;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
<body bgcolor="#FFFFFF"
|
||||
text="#000000"
|
||||
link="#0000FF"
|
||||
vlink="#FF0000"
|
||||
alink="#FF00FF">
|
||||
<section class="outer">
|
||||
<center>
|
||||
<header>
|
||||
<h1>
|
||||
<img src="../../html/images/tuxpaint-title.png"
|
||||
width="205"
|
||||
|
|
@ -26,11 +94,12 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
janvier 20, 2022 </p>
|
||||
mars 31, 2022 </p>
|
||||
</header>
|
||||
</center>
|
||||
</section>
|
||||
|
||||
<hr>
|
||||
|
||||
<section>
|
||||
<p>
|
||||
Tux Paint répond aux signaux suivants (qui peuvent être envoyé au processus du programme via `<code>kill</code>` ou`<code>killall</code>`, par exemple). </p>
|
||||
|
||||
|
|
@ -46,11 +115,11 @@
|
|||
<p>
|
||||
Depuis l'interface principale, Tux Paint vous demandera si vous souhaitez quitter ou non, et (sauf si remplacé par l'option autosave, par ex. "<code>--autosave</code>") si vous souhaitez enregistrer le dessin courant (s'il n'est pas enregistré), et si c'est le cas, et c'est une version modifiée d'un dessin existant (sauf si remplacé par les options pour écraser les images anciennes, ou bien sauvegarder avec un nouveau nom (par ex. "<code>--saveover</code>" ou "<code>--saveovernew</code>") vers un nouveau fichier. </p>
|
||||
|
||||
<p>
|
||||
<b>Remarque :</b>Sur d'autres parties de l'interface, le signal est en fait interprété comme une demande de retour en arrière (par exemple, de la boîte de dialogue "Nouveau" pour revenir sur l'interface principale), comme si un bouton "Retour" dans Tux Paint a été cliqué, ou la touche <b><code>[Esc]</code></b> enfoncée. </p>
|
||||
|
||||
<p>
|
||||
Exemple: <code>killall tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
|
||||
</dd>
|
||||
|
||||
<dt>
|
||||
|
|
@ -64,12 +133,13 @@
|
|||
<p>
|
||||
Ainsi, à partir de l'interface principale, Tux Paint devrait se fermer presque immédiatement, sans poser de questions. </p>
|
||||
|
||||
<p>
|
||||
À partir d'autres parties de l'interface, malheureusement, Tux Paint ne reviendra que d'un niveau dans l'interface. Par conséquent, à ce moment, il peut être nécessaire d'envoyer ce signal à Tux Paint plusieurs fois pour qu'il s'arrête complètement. </p>
|
||||
|
||||
<p>
|
||||
Exemple: <code>killall -s SIGUSR1 tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
|
||||
</dd>
|
||||
</dl>
|
||||
</section>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -5,9 +5,7 @@
|
|||
Copyright © 2019-2022 by varios colaboradores; see AUTHORS.txt.
|
||||
https://tuxpaint.org/
|
||||
|
||||
20 de Xaneiro de 2022
|
||||
|
||||
----------------------------------------------------------------------
|
||||
31 de Marzo de 2022
|
||||
|
||||
Tux Paint responde aos seguintes sinais (que poden enviarse ao proceso do
|
||||
programa a través de «kill» ou «killall», por exemplo).
|
||||
|
|
@ -29,13 +27,13 @@
|
|||
quere ou non sobreescribir o debuxo existente ou gardalo nun novo
|
||||
ficheiro.
|
||||
|
||||
Nota: Dende outras partes da interface, o sinal interprétase
|
||||
actualmente como unha solicitude de retroceso (por exemplo, dende
|
||||
o diálogo «Novo» de volta á interface principal), coma se se
|
||||
premera un botón «Atrás» en Tux Paint ou se premera a tecla [Esc].
|
||||
|
||||
Exemplo: killall tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, the signal is currently
|
||||
interpreted as a request to go back (e.g., from the "New" dialog
|
||||
back to the main interface), as if a "Back" button in Tux Paint
|
||||
were clicked, or the [Esc] was key pressed.
|
||||
|
||||
SIGUSR1 & SIGUSR2
|
||||
|
||||
Tux Paint responde axustando a súa opción de gardar
|
||||
|
|
@ -49,9 +47,9 @@
|
|||
Así, dende a interface principal, Tux Paint debería saír case de
|
||||
inmediato, sen facer preguntas.
|
||||
|
||||
Nota: Dende outras partes da interface, por desgraza, Tux Paint
|
||||
retrocederá un nivel na interface. Polo tanto, neste momento pode
|
||||
que sexa necesario enviar este sinal a Tux Paint unhas cantas
|
||||
veces para que saia completamente.
|
||||
|
||||
Exemplo: killall -s SIGUSR1 tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, unfortunately, Tux
|
||||
Paint will go back one level in the interface. Therefore, at this
|
||||
time, it may be necessary to send this signal to Tux Paint a few
|
||||
times, for it to quit completely.
|
||||
|
|
|
|||
|
|
@ -5,13 +5,81 @@
|
|||
Documentación de sinais de Tux Paint </title>
|
||||
<meta http-equiv="Content-Type"
|
||||
content="text/html; charset=utf-8">
|
||||
<style>
|
||||
body { font-size: large; }
|
||||
table { font-size: large; }
|
||||
div.screenshot-center {
|
||||
text-align: center;
|
||||
}
|
||||
div.screenshot-right {
|
||||
float: right;
|
||||
margin-left: 1em;
|
||||
margin-bottom: 1em;
|
||||
}
|
||||
div.screenshot-right-after {
|
||||
clear: both;
|
||||
}
|
||||
div.keeptogether { page-break-inside: avoid; }
|
||||
section h1 { font-size: 2em; }
|
||||
h1, h2, h3, h4 { font-family: sans; }
|
||||
h1 { color: #800; page-break-before: always; break-before: always; }
|
||||
h2 { color: #440; page-break-after: avoid; break-after: avoid; }
|
||||
h3 { color: #080; page-break-after: avoid; break-after: avoid; }
|
||||
h4 { color: #008; page-break-after: avoid; break-after: avoid; }
|
||||
h1 + p { page-break-inside: avoid; }
|
||||
h2 + p { page-break-inside: avoid; }
|
||||
h3 + p { page-break-inside: avoid; }
|
||||
h4 + p { page-break-inside: avoid; }
|
||||
dt {
|
||||
font-size: large;
|
||||
color: #404;
|
||||
font-family: sans;
|
||||
margin-top: 1em;
|
||||
margin-bottom: 0.25em;
|
||||
}
|
||||
dd, blockquote {
|
||||
border-left: 1px solid #888;
|
||||
padding-left: 1em;
|
||||
border-radius: 0 0 0 1em;
|
||||
}
|
||||
p.note {
|
||||
border: 1px solid #000;
|
||||
background-color: #eee;
|
||||
border-radius: 0.5em;
|
||||
padding: 0.5em;
|
||||
display: inline-block;
|
||||
margin-right: 3em;
|
||||
}
|
||||
section.outer {
|
||||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
margin-left: 0;
|
||||
}
|
||||
p + ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
@media print {
|
||||
p {
|
||||
orphans: 3;
|
||||
widows: 3;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
<body bgcolor="#FFFFFF"
|
||||
text="#000000"
|
||||
link="#0000FF"
|
||||
vlink="#FF0000"
|
||||
alink="#FF00FF">
|
||||
<section class="outer">
|
||||
<center>
|
||||
<header>
|
||||
<h1>
|
||||
<img src="../../html/images/tuxpaint-title.png"
|
||||
width="205"
|
||||
|
|
@ -26,11 +94,12 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
20 de Xaneiro de 2022 </p>
|
||||
31 de Marzo de 2022 </p>
|
||||
</header>
|
||||
</center>
|
||||
</section>
|
||||
|
||||
<hr>
|
||||
|
||||
<section>
|
||||
<p>
|
||||
Tux Paint responde aos seguintes sinais (que poden enviarse ao proceso do programa a través de «<code>kill</code>» ou «<code>killall</code>», por exemplo). </p>
|
||||
|
||||
|
|
@ -46,11 +115,11 @@
|
|||
<p>
|
||||
Dende a interface principal, Tux Paint preguntará se quere ou non saír e (a non ser que sexa anulado pol a opción de gardado automático, p. ex.: «<code>--autosave</code>x) se quere gardar o debuxo actual (se non está gardado) , e se é así, e é unha versión modificada dun debuxo existente (a non ser que sexa anulado polas opcións de gardar sobre imaxes antigas ou gardar sempre imaxes novas; por exemplo, «<code>--saveover</code>« e «<code>--saveovernew</code>», respectivamente), se quere ou non sobreescribir o debuxo existente ou gardalo nun novo ficheiro. </p>
|
||||
|
||||
<p>
|
||||
<b>Nota:</b> Dende outras partes da interface, o sinal interprétase actualmente como unha solicitude de retroceso (por exemplo, dende o diálogo «Novo» de volta á interface principal), coma se se premera un botón «Atrás» en Tux Paint ou se premera a tecla <b><code>[Esc]</code></b>. </p>
|
||||
|
||||
<p>
|
||||
Exemplo: <code>killall tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
|
||||
</dd>
|
||||
|
||||
<dt>
|
||||
|
|
@ -64,12 +133,13 @@
|
|||
<p>
|
||||
Así, dende a interface principal, Tux Paint debería saír case de inmediato, sen facer preguntas. </p>
|
||||
|
||||
<p>
|
||||
<b>Nota:</b> Dende outras partes da interface, por desgraza, Tux Paint retrocederá un nivel na interface. Polo tanto, neste momento pode que sexa necesario enviar este sinal a Tux Paint unhas cantas veces para que saia completamente. </p>
|
||||
|
||||
<p>
|
||||
Exemplo: <code>killall -s SIGUSR1 tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
|
||||
</dd>
|
||||
</dl>
|
||||
</section>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -5,9 +5,7 @@
|
|||
Copyright © 2019-2022 by various contributors; see AUTHORS.txt.
|
||||
https://tuxpaint.org/
|
||||
|
||||
2022年1月20日
|
||||
|
||||
----------------------------------------------------------------------
|
||||
2022年3月31日
|
||||
|
||||
Tux Paint responds to the following signals (which can be sent to the
|
||||
program's process via `kill` or `killall`, for example).
|
||||
|
|
@ -27,13 +25,13 @@
|
|||
respectively), whether or not to overwrite the existing drawing,
|
||||
or save to a new file.
|
||||
|
||||
Note: From other parts of the interface, the signal is currently
|
||||
例：killall tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, the signal is currently
|
||||
interpreted as a request to go back (e.g., from the "New" dialog
|
||||
back to the main interface), as if a "Back" button in Tux Paint
|
||||
were clicked, or the [Esc] was key pressed.
|
||||
|
||||
例：killall tuxpaint
|
||||
|
||||
SIGUSR1 & SIGUSR2
|
||||
|
||||
Tux Paint responds by setting its auto-save option (as if it had
|
||||
|
|
@ -47,9 +45,9 @@
|
|||
So, from the main interface, Tux Paint should quit almost
|
||||
immediately, with no questions asked.
|
||||
|
||||
Note: From other parts of the interface, unfortunately, Tux Paint
|
||||
will go back one level in the interface. Therefore, at this time,
|
||||
it may be necessary to send this signal to Tux Paint a few times,
|
||||
for it to quit completely.
|
||||
|
||||
例：killall -s SIGUSR1 tuxpaint
|
||||
|
||||
💡 Note: From other parts of the interface, unfortunately, Tux
|
||||
Paint will go back one level in the interface. Therefore, at this
|
||||
time, it may be necessary to send this signal to Tux Paint a few
|
||||
times, for it to quit completely.
|
||||
|
|
|
|||
|
|
@ -5,13 +5,81 @@
|
|||
Tux Paint Signals Documentation </title>
|
||||
<meta http-equiv="Content-Type"
|
||||
content="text/html; charset=utf-8">
|
||||
<style>
|
||||
body { font-size: large; }
|
||||
table { font-size: large; }
|
||||
div.screenshot-center {
|
||||
text-align: center;
|
||||
}
|
||||
div.screenshot-right {
|
||||
float: right;
|
||||
margin-left: 1em;
|
||||
margin-bottom: 1em;
|
||||
}
|
||||
div.screenshot-right-after {
|
||||
clear: both;
|
||||
}
|
||||
div.keeptogether { page-break-inside: avoid; }
|
||||
section h1 { font-size: 2em; }
|
||||
h1, h2, h3, h4 { font-family: sans; }
|
||||
h1 { color: #800; page-break-before: always; break-before: always; }
|
||||
h2 { color: #440; page-break-after: avoid; break-after: avoid; }
|
||||
h3 { color: #080; page-break-after: avoid; break-after: avoid; }
|
||||
h4 { color: #008; page-break-after: avoid; break-after: avoid; }
|
||||
h1 + p { page-break-inside: avoid; }
|
||||
h2 + p { page-break-inside: avoid; }
|
||||
h3 + p { page-break-inside: avoid; }
|
||||
h4 + p { page-break-inside: avoid; }
|
||||
dt {
|
||||
font-size: large;
|
||||
color: #404;
|
||||
font-family: sans;
|
||||
margin-top: 1em;
|
||||
margin-bottom: 0.25em;
|
||||
}
|
||||
dd, blockquote {
|
||||
border-left: 1px solid #888;
|
||||
padding-left: 1em;
|
||||
border-radius: 0 0 0 1em;
|
||||
}
|
||||
p.note {
|
||||
border: 1px solid #000;
|
||||
background-color: #eee;
|
||||
border-radius: 0.5em;
|
||||
padding: 0.5em;
|
||||
display: inline-block;
|
||||
margin-right: 3em;
|
||||
}
|
||||
section.outer {
|
||||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
margin-left: 0;
|
||||
}
|
||||
p + ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
@media print {
|
||||
p {
|
||||
orphans: 3;
|
||||
widows: 3;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
<body bgcolor="#FFFFFF"
|
||||
text="#000000"
|
||||
link="#0000FF"
|
||||
vlink="#FF0000"
|
||||
alink="#FF00FF">
|
||||
<section class="outer">
|
||||
<center>
|
||||
<header>
|
||||
<h1>
|
||||
<img src="../../html/images/tuxpaint-title.png"
|
||||
width="205"
|
||||
|
|
@ -26,11 +94,12 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
2022年1月20日 </p>
|
||||
2022年3月31日 </p>
|
||||
</header>
|
||||
</center>
|
||||
</section>
|
||||
|
||||
<hr>
|
||||
|
||||
<section>
|
||||
<p>
|
||||
Tux Paint responds to the following signals (which can be sent to the program's process via `<code>kill</code>` or `<code>killall</code>`, for example). </p>
|
||||
|
||||
|
|
@ -46,11 +115,11 @@
|
|||
<p>
|
||||
From the main interface, Tux Paint will prompt whether or not you wish to quit, and (unless overridden by the auto-save option, e.g. "<code>--autosave</code>") if you'd like to save the current drawing (if unsaved), and if so, and it's a modified version of an existing drawing (unless overridden by the options to save over old images, or always save new images; e.g. "<code>--saveover</code>" and "<code>--saveovernew</code>", respectively), whether or not to overwrite the existing drawing, or save to a new file. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
|
||||
|
||||
<p>
|
||||
例：<code>killall tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
|
||||
</dd>
|
||||
|
||||
<dt>
|
||||
|
|
@ -64,12 +133,13 @@
|
|||
<p>
|
||||
So, from the main interface, Tux Paint should quit almost immediately, with no questions asked. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
|
||||
|
||||
<p>
|
||||
例：<code>killall -s SIGUSR1 tuxpaint</code> </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
|
||||
</dd>
|
||||
</dl>
|
||||
</section>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue