<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Phil,<br>
<br>
On 23.02.21 11:08, Philip Taylor wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f8f27d39-adc7-6ceb-3516-750a3b490477@Hellenic-Institute.Uk">
<blockquote type="cite"
cite="mid:22a749db-75e4-a40f-db09-695d20f9afa2@gmail.com">
<blockquote type="cite"
cite="mid:e9c610e1-af15-4d4c-c05e-72b7c8b82a48@Hellenic-Institute.Uk">
<ul>
<li>[Requested features] Support for draggable rulers</li>
</ul>
</blockquote>
<br>
As a feature request, this is not likely to happen before this
release. That being said, what do you mean by "draggable"? (I
assume you mean rulers in the PDF preview?)<br>
</blockquote>
<br>
Draggable as in the Adobe CC suite — two rulers, one horizontal
(above the preview), one vertical (to the left of the preview, or
perhaps to the right for RTL UIs), from which one can drag guide
lines which then remain overlaying the preview to allow accurate
measurement, comparison, etc.<br>
</blockquote>
<br>
Understood.<br>
<br>
<blockquote type="cite"
cite="mid:f8f27d39-adc7-6ceb-3516-750a3b490477@Hellenic-Institute.Uk">
But two other things while I think of them —<br>
<ol>
<li>The previewer does not seem to know which source documented
generated the preview. Let there be three files, 1.tex, 1.tmp
(a text file) & 1.pdf. Let 1.pdf be the result of
compiling 1.tex. Then all the while that 1.tex and 1.pdf
remain open, hitting "Compile" in the preview window will
cause 1.tex to be compiled. But if one closes 1.tex, leaving
1.tmp & 1.pdf open (1.tmp in the source pane, of course,
being a text file), then hitting "Compile" in the preview
window causes the system to attempt to compile 1.tmp<br>
</li>
</ol>
</blockquote>
<br>
This is (currently) "by design". There are a number of ways TeXworks
internally "associates" a source file with an output file. Mostly a
source and output are associated if they share the same filename,
but there are other aspects in play as well (e.g., the %!TeX root
directive). Note that the extension does not play a role in this
(after all, you could have all sorts of possible extensions for the
source file, from .tex over .ltx to some more obscure extensions,
particularly if you use custom typesetting tools that might
preprocess your code to produce some intermediate TeX
representation).<br>
<br>
So in your case, both 1.tex and 1.tmp are initially associated with
1.pdf. Typesetting is currently always initiated from a source file,
so when the only (open, i.e. currently associated) source file is
1.tmp, that is used.<br>
<br>
That being said, this will hopefully improve in the process of
refactoring the code to support projects. But there is no quick and
easy fix for this right now, unfortunately.<br>
<br>
<blockquote type="cite"
cite="mid:f8f27d39-adc7-6ceb-3516-750a3b490477@Hellenic-Institute.Uk">
<ol>
<li>File/open in the preview window does not pre-select ".pdf"
as the extension as I would expect it to, leaving it at the
default of ".tex".</li>
</ol>
</blockquote>
<br>
This should now be fixed (hopefully without breaking anything else).<br>
<br>
Thanks for all your suggestions!<br>
Stefan<br>
</body>
</html>