<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
<blockquote type="cite">
<div class="moz-cite-prefix">But if I work successively on 5
projects, A, B, C. D and E<br>
</div>
<div class="moz-cite-prefix">I currently feel it is not guaranteed
that the tabs in A will have always been preserved when I return
from E to A</div>
<div class="moz-cite-prefix">(using "reopen project")</div>
</blockquote>
AFAIK, if you are using the same version (build does not matter) and
keep switching the project, the editing state will persist.<br>
If you do encounter the issue again, please contact us directly on
our support email address, <a class="moz-txt-link-abbreviated" href="mailto:support@oxygenxml.com">support@oxygenxml.com</a>.<br>
<br>
<blockquote type="cite">I should add that I work on multilingual
texts [with 50% of the content in Tamil script) which rely heavily
on bidirectional support,...</blockquote>
<br>
<blockquote type="cite">
<div class="moz-cite-prefix">The most acrobatic is of course when
I occasionally have to edit (in text mode) a file which is
beyond the limit where bidirectional support is disabled,</div>
<div class="moz-cite-prefix">because in any line containing Tamil
I cannot rely on what I see on screen</div>
<div class="moz-cite-prefix">and have to edit BLINDLY, on the
basis of what I know of the position where the cursor SHOULD BE</div>
<div class="moz-cite-prefix">;-)</div>
<div class="moz-cite-prefix"><br>
</div>
</blockquote>
I would recommend trying to stick with the Author mode in such
cases. The BiDi support for Author mode is implemented in house and
has been optimized by our developers to work even with larger texts.
If there's something not visible in Author mode, perhaps have an
alternate CSS which can be easily switched within Author mode.<br>
The problem with BiDi support in Text mode is that it relies on the
default Java support which has some performance issues once the
document exceeds a certain size. This is the reason we enforce that
size limit and disable the support once a threshold has been
reached. The alternative would be to let the application slow down
to a crawl.<br>
<br>
<blockquote type="cite">Can progress be expected in that direction?</blockquote>
We have considered rewriting the default Java BiDi support from Text
mode, but unfortunately it is more complicated than initially
anticipated to optimize someone else's code. This will be considered
in the long term.<br>
<br>
Regards,<br>
Adrian<br>
<br>
<div class="moz-cite-prefix">On 01.08.2019 19:34, Jean-Luc
Chevillard wrote:<br>
</div>
<blockquote type="cite"
cite="mid:45a50dc9-d5be-f1d4-e67f-6306c7b19019@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">
<blockquote type="cite">What version of Oxygen are you using? Or
are there multiple versions?<br>
</blockquote>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Hello Adrian,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Thank you for your answer.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I am using the latest version</div>
<div class="moz-cite-prefix">(and also the latest build [which you
announced on 19th july on this list])</div>
<div class="moz-cite-prefix">but many of the tabs inside my
(virtually) open projects</div>
<div class="moz-cite-prefix">were opened at the time when I was
using the previous builds</div>
<div class="moz-cite-prefix">(or the previous versions).</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Oxygen has mostly behaved for me in
the expected manner</div>
<div class="moz-cite-prefix">(as described by you)<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I have never lost open tabs
information simply when alternating between 2 projects A and B</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">But if I work successively on 5
projects, A, B, C. D and E<br>
</div>
<div class="moz-cite-prefix">I currently feel it is not guaranteed
that the tabs in A will have always been preserved when I return
from E to A</div>
<div class="moz-cite-prefix">(using "reopen project")<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I should add that I work on
multilingual texts [with 50% of the content in Tamil script)
which rely heavily on bidirectional support,</div>
<div class="moz-cite-prefix">and that when the size of my files
grow, the time needed for switching between "Text Mode" and
"Author mode" can become rather long</div>
<div class="moz-cite-prefix">(it can sometimes take 40 seconds for
"computing the layout")</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The most acrobatic is of course when
I occasionally have to edit (in text mode) a file which is
beyond the limit where bidirectional support is disabled,</div>
<div class="moz-cite-prefix">because in any line containing Tamil
I cannot rely on what I see on screen</div>
<div class="moz-cite-prefix">and have to edit BLINDLY, on the
basis of what I know of the position where the cursor SHOULD BE</div>
<div class="moz-cite-prefix">;-)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Can progress be expected in that
direction?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">(I have always hesitated to encourage
my colleagues using the same environment as me</div>
<div class="moz-cite-prefix">because I cannot stomach the idea
that they would find themselves stuck in a BLIND EDITING
situation of the type that I have just described ...</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Nevertheless, Oxygen in a great
software for me,</div>
<div class="moz-cite-prefix">which I use for several hours every
day<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">;-)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Best wishes</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">-- Jean-Luc</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><a class="moz-txt-link-freetext"
href="https://twitter.com/JLC1956" moz-do-not-send="true">https://twitter.com/JLC1956</a><br>
<br>
<a class="moz-txt-link-freetext"
href="https://univ-paris-diderot.academia.edu/JeanLucChevillard"
moz-do-not-send="true">https://univ-paris-diderot.academia.edu/JeanLucChevillard</a><br>
<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 01/08/2019 16:01, Oxygen XML
Editor Support (Adrian Buza) wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5b974e4b-7cfe-3f56-0805-6a09a421a600@oxygenxml.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
Hello,<br>
<br>
What version of Oxygen are you using? Or are there multiple
versions?<br>
<br>
<blockquote type="cite">-- is there a limit in the number of
open tabs which can be remembered? (or in the number of
virtually open projects between which one can smoothly
navigate) </blockquote>
There is no limit for the number of opened tabs that are
remembered (we call it "<b>project editing state</b>"). Only one
project is open at any given time, the rest are just history.
Even if they are lost from the project history their opened tabs
are still remembered.<br>
<br>
<blockquote type="cite">-- can discontinuities [in remembering]
be caused by the installation of a new build (or a new
version)? </blockquote>
Yes, that is possible because of version changes. <br>
Since v21.0 the mechanism for keeping the project editing state
has changed, a distinct file is used for each version of Oxygen.
When updating versions (from an old version to a newer version)
the project editing state of the older version is imported in
the newer one the first time you run the new one.<br>
<b>If you go back to an old version (e.g. v21.0), you will not
see any changes in project editing state made with the new
version (e.g. v21.1).</b> Also, after the initial import
(first time a new version is run), if you make changes with an
older version (v21.0) in the project editing state, they will
not be imported again when you start the newer version (v21.1).<br>
<br>
Regards,<br>
Adrian<br>
<pre class="moz-signature" cols="72">Adrian Buza
oXygen XML Editor and Author Support
</pre>
<div class="moz-cite-prefix">On 31.07.2019 11:42, Jean-Luc
Chevillard wrote:<br>
</div>
<blockquote type="cite"
cite="mid:74430ff8-176c-6b16-cc0c-589824b23083@gmail.com">Dear
members of the Oxygen support team and of the user group, <br>
<br>
I have a question concerning the IMPERMANENCE of open tabs in
Oxygen projects. <br>
<br>
Mor precisely, I am currently working on several ancient
texts, for which I am preparing electronic editions (in a
progressively changing XML format) and each text has its own
project. <br>
<br>
When I exit Oxygen, I usually leave several tabs open in the
currently open project, and I expect to find themselves still
open when I restart Oxygen (and I can see that Oxygen reloads
the open files, whih can take time because many files are
bulky and contain complex structures with possibly tens of
thousands of elements. <br>
<br>
When I switch from one project to another one (using the
"Reopen project" in the "Project" menu) I have also come to
expect that I shall find the same open tabs as I had left open
during the previous editing session for the same project
(which is therefore "virtually open") <br>
<br>
Howevever, I have recently noticed that this does not always
happen. <br>
<br>
On several occasions, I have had to individually reopen files,
after using the "Reopen project" <br>
(which currently lists 29 projects in its menu) <br>
<br>
This being said, <br>
I can now restate my question. <br>
<br>
-- is there a limit in the number of open tabs which can be
remembered? (or in the number of virtually open projects
between which one can smoothly navigate) <br>
-- can discontinuities [in remembering] be caused by the
installation of a new build (or a new version)? <br>
<br>
<br>
Thanks for clarifications <br>
<br>
-- Jean-Luc <br>
<br>
<br>
<a class="moz-txt-link-freetext"
href="https://twitter.com/JLC1956" moz-do-not-send="true">https://twitter.com/JLC1956</a>
<br>
<br>
<a class="moz-txt-link-freetext"
href="https://univ-paris-diderot.academia.edu/JeanLucChevillard"
moz-do-not-send="true">https://univ-paris-diderot.academia.edu/JeanLucChevillard</a>
<br>
<br>
_______________________________________________ <br>
oXygen-user mailing list <br>
<a class="moz-txt-link-abbreviated"
href="mailto:oXygen-user@oxygenxml.com"
moz-do-not-send="true">oXygen-user@oxygenxml.com</a> <br>
<a class="moz-txt-link-freetext"
href="https://www.oxygenxml.com/mailman/listinfo/oxygen-user"
moz-do-not-send="true">https://www.oxygenxml.com/mailman/listinfo/oxygen-user</a>
<br>
</blockquote>
<br>
</blockquote>
<p><br>
</p>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Adrian Buza
oXygen XML Editor and Author Support
Tel: +1-650-352-1250 ext.2020
Fax: +40-251-461482
</pre>
</body>
</html>