rd Lisse a écrit :
Jean-Pierre
I just use the 'PDF Form' Module (which requires/loads hyperref) and the
Insert->Custom Insets
offers a number of choices such as
TextField.
Then you can put stuff like
width=9cm, charsize=9pt, bordercolor={0.94 0.97 1.0},
backgrou
Le 02/07/2021 à 12:40, Dr Eberhard Lisse a écrit :
Jean-Pierre
I just use the 'PDF Form' Module (which requires/loads hyperref) and the
Insert->Custom Insets
offers a number of choices such as
TextField.
Then you can put stuff like
width=9cm, charsize=9pt, bord
Jean-Pierre
I just use the 'PDF Form' Module (which requires/loads hyperref) and the
Insert->Custom Insets
offers a number of choices such as
TextField.
Then you can put stuff like
width=9cm, charsize=9pt, bordercolor={0.94 0.97 1.0},
backgrou
Dear Developers
A French user draw my attention on the fact that the dynamic forms documented in
section 5 of the PDF_Form.lyx manual (in examples/Modules) did not work as
described.
After installing insdljs.sty, I could display the examples in the output. It
took me a while to understand th
Am Dienstag, 18. April 2017 um 01:43:30, schrieb Uwe Stöhr
> El 17.04.2017 a las 22:04, Kornel Benko escribió:
>
> > It may be that the python output is not in the messages pane, only messages
> > created by lyx executable.
> > I am in favour of bug report.
>
> I reported a bug:
> http://www.ly
On Mon, Apr 17, 2017 at 08:33:04AM +0200, Kornel Benko wrote:
> Am Montag, 17. April 2017 um 05:04:29, schrieb Uwe Stöhr
> > El 17.04.2017 a las 04:40, Scott Kostyshak escribió:
> >
> > > I tested just "PDF-form" tests and the ones that were failing pa
font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format pdf2
\output_sync 0
\bibtex_command bibtex
\index_command default
\paperfontsize 12
\spacing single
\use_hyperref true
\pd
t;
> lyx -e lyx16x PDF-form.lyx
> lyx -batch PDF-form.16.lyx
>
> In only got the Lexer.cpp warnings which led me to the track of the
> issue. Strange.
> I also wonder why LyX does not output these messages in the messages
> pane when opening a file. Should I report this as
El 17.04.2017 a las 19:41, Kornel Benko escribió:
Confirmed. Thanks Uwe.
Thank you. I'll send the patch for LyX 2.2 now.
Nevertheless I could not get all the errors/warnings you got with
lyx -e lyx16x PDF-form.lyx
lyx -batch PDF-form.16.lyx
In only got the Lexer.cpp warnings which l
Am Montag, 17. April 2017 um 19:20:32, schrieb Uwe Stöhr
> El 17.04.2017 a las 18:14, Uwe Stöhr escribió:
>
> > There is however an error in a conversion routine from 1.6.x to 2.0x
> > because the length \totalheight is mangled. Therefore the opened file
> > fails to compile to a PDF.
>
> This
El 17.04.2017 a las 18:14, Uwe Stöhr escribió:
There is however an error in a conversion routine from 1.6.x to 2.0x
because the length \totalheight is mangled. Therefore the opened file
fails to compile to a PDF.
This bug is now also fixed:
http://www.lyx.org/trac/changeset/bc0591a2/lyxgit
N
s
> >> senseless.
> >
> > Makes sense.
>
> Therefore I opt to remove the test for LyX 1.6x and 2.0x for PDF-form
> and also PDF-comment.
>
> > I can open it too, but the error messages seen by Scott are still there.
> > We are not testing lyx1.6. W
El 17.04.2017 a las 08:33, Kornel Benko escribió:
LyX is made for users. It is impossible to use PDF forms in LyX < 2.1 so
there won't be users. Therefore testing this file export to LyX 1.6 is
senseless.
Makes sense.
Therefore I opt to remove the test for LyX 1.6x and 2.0x for
Am Montag, 17. April 2017 um 05:04:29, schrieb Uwe Stöhr
> El 17.04.2017 a las 04:40, Scott Kostyshak escribió:
>
> > I tested just "PDF-form" tests and the ones that were failing pass now.
> > Thanks for the fixes.
>
> Thanks. I'll send the patch for bran
El 17.04.2017 a las 04:40, Scott Kostyshak escribió:
I tested just "PDF-form" tests and the ones that were failing pass now.
Thanks for the fixes.
Thanks. I'll send the patch for branch then.
In the above, what does "a valid document which can be read by an
older LyX
now:
> www.lyx.org/trac/changeset/5b4cc6b6/lyxgit
>
> In fact I had to rewrite the whole colorbox routine and extend the box
> features routine.
>
> Attached is my test file and the output I get.
I tested just "PDF-form" tests and the ones that were failing pass now.
outine and extend the box
features routine.
Attached is my test file and the output I get.
Kornel, if it works now for you as well I want to backport the fix also
to branch.
Testing lyX2lyx further than LyX 2.1.x makes no sense because the PDF
form module is not available for LyX < 2.1.
El 16.04.2017 a las 23:41, Uwe Stöhr escribió:
I'll have a look.
My today's change in PDF-form.lyx where I use 2 nested colored boxes
bring the new warning you see. I'll fix this lyx2lyx issue.
regards Uwe
El 16.04.2017 a las 19:12, Kornel Benko escribió:
Should we ignore this messages?
No because this means there is a bug in the lyxl2yx conversion routine.
You get this when creating the 21 file and then opening with LyX 2.3,
right? Do you also get the same error when opening with LyX 2.2?
I
On Sun, Apr 16, 2017 at 07:12:23PM +0200, Kornel Benko wrote:
> #ctest export/examples/PDF-form_lyx21
> shows this message on stderr:
>
> -- check structures of PDF-form.21.lyx
> -- Executing /BUILD/BUILDMint17/BuildLyxGitQt5.9alpha-gcc6.2/bin/lyx2.3
> -userdir &
#ctest export/examples/PDF-form_lyx21
shows this message on stderr:
-- check structures of PDF-form.21.lyx
-- Executing /BUILD/BUILDMint17/BuildLyxGitQt5.9alpha-gcc6.2/bin/lyx2.3
-userdir "/BUILD/BUILDMint17/BuildLyxGitQt5.9alpha-gcc6.2/Testing/.lyx" -E
lyx21x PDF-form.21.21.lyx &q
21 matches
Mail list logo
