bug in filling fields and Acrobat Reader XI?
Dear list, I have the following sample: \usemodule[fields] \starttext This is a \fillinfield[name]{text that defines field length}. \stoptext I’m afraid that Adobe Reader XI (in Windows 10) isn’t able to keep the text in the field after the pointer moves outside the field. Could anyone confirm the bug or explain me what I’m doing wrong? Many thanks for your help, Pablo -- http://www.ousia.tk
Am 2017-03-14 um 18:05 schrieb Pablo Rodriguez
Dear list,
I have the following sample:
\usemodule[fields] \starttext This is a \fillinfield[name]{text that defines field length}. \stoptext
I’m afraid that Adobe Reader XI (in Windows 10) isn’t able to keep the text in the field after the pointer moves outside the field.
Could anyone confirm the bug or explain me what I’m doing wrong?
Your example is missing \setupinteraction[state=start], but I can confirm the problem with latest beta and Acrobat Pro 9 on OSX. The problem is that the field is setup with a validation script 'CheckFillInField("name")', and that doesn’t exist. I also don’t know why the text is red. Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net GPG Key ID 1C9B22FD
Am 2017-03-14 um 18:22 schrieb Henning Hraban Ramm
Am 2017-03-14 um 18:05 schrieb Pablo Rodriguez
: Dear list,
I have the following sample:
\usemodule[fields] \starttext This is a \fillinfield[name]{text that defines field length}. \stoptext
I’m afraid that Adobe Reader XI (in Windows 10) isn’t able to keep the text in the field after the pointer moves outside the field.
Could anyone confirm the bug or explain me what I’m doing wrong?
Your example is missing \setupinteraction[state=start], but I can confirm the problem with latest beta and Acrobat Pro 9 on OSX.
The problem is that the field is setup with a validation script 'CheckFillInField("name")', and that doesn’t exist. I also don’t know why the text is red.
I was wrong. The validation script is stored as document level script, because it’s within JSpreamble. And it sets the value to "", regardless of the content. See http://source.contextgarden.net/tex/context/modules/mkiv/m-fields.mkiv?searc... Better don’t use this module, it’s just an example. If you need exactly this functionality, copy the code. Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net GPG Key ID 1C9B22FD
On 03/14/2017 06:36 PM, Henning Hraban Ramm wrote:
[...] I was wrong. The validation script is stored as document level script, because it’s within JSpreamble. And it sets the value to "", regardless of the content. See http://source.contextgarden.net/tex/context/modules/mkiv/m-fields.mkiv?searc...
Better don’t use this module, it’s just an example.
If you need exactly this functionality, copy the code.
I need it, because it is the simplest way to create a fill-in field. I have two questions: Does it make any sense to have a module that doesn’t retain the content of the fill-in fields? How should I define the new \fillinfield command? Would it work removing validation from the command? I’m sorry, I’m not running Windows and I have no way of testing it. Besides the fact that JavaScript is beyond my knowledge. \usemodule[fields] \definefieldcategory [fillinfield] [n=1024, height=\strutht, depth=\strutdp, align=middle, color=red, fieldframecolor=blue, fieldbackgroundcolor=white, validate=] \setupinteraction[state=start] \starttext This is a \fillinfield[name]{text that defines field length}. \stoptext It works fine with evince (it retains the contents of the fill-in field). But I need to know whether this works in Windows. Many thanks for your help, Pablo -- http://www.ousia.tk
On 03/14/2017 06:22 PM, Henning Hraban Ramm wrote:
Am 2017-03-14 um 18:05 schrieb Pablo Rodriguez:
[...] I’m afraid that Adobe Reader XI (in Windows 10) isn’t able to keep the text in the field after the pointer moves outside the field.
Could anyone confirm the bug or explain me what I’m doing wrong?
Your example is missing \setupinteraction[state=start], but I can confirm the problem with latest beta and Acrobat Pro 9 on OSX.
Sorry, I checked it at work and I couldn’t copy the code from my usb memory.
The problem is that the field is setup with a validation script 'CheckFillInField("name")', and that doesn’t exist. I also don’t know why the text is red.
Text is red and border is blue. These are the defaults set in http://source.contextgarden.net/tex/context/modules/mkiv/m-fields.mkiv. There you have the validation script, but I’m afraid this is Greek to me. I’m experiencing another issue, but I need to check it in the code first. Pablo -- http://www.ousia.tk
Am 2017-03-14 um 18:44 schrieb Pablo Rodriguez
Text is red and border is blue. These are the defaults set in http://source.contextgarden.net/tex/context/modules/mkiv/m-fields.mkiv.
There you have the validation script, but I’m afraid this is Greek to me.
But guessing from your homepage you understand Greek ;)
Am 2017-03-14 um 18:57 schrieb Pablo Rodriguez
Does it make any sense to have a module that doesn’t retain the content of the fill-in fields?
No ;)
How should I define the new \fillinfield command? Would it work removing validation from the command? I’m sorry, I’m not running Windows and I have no way of testing it. Besides the fact that JavaScript is beyond my knowledge.
\setupinteraction[state=start]
\usemodule[fields] \definefieldcategory [fillinfield] [n=1024, height=\strutht, depth=\strutdp, align=middle, color=red, fieldframecolor=blue, fieldbackgroundcolor=white, validate=] \setupinteraction[state=start] \starttext This is a \fillinfield[name]{text that defines field length}. \stoptext
Yes, that works. You can leave out most of the parameters.
It works fine with evince (it retains the contents of the fill-in field). But I need to know whether this works in Windows.
It works with evince because that probably doesn’t run JavaScript functions from PDFs. Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net GPG Key ID 1C9B22FD
On 03/14/2017 07:06 PM, Henning Hraban Ramm wrote:
Am 2017-03-14 um 18:44 schrieb Pablo Rodriguez:
Text is red and border is blue. These are the defaults set in http://source.contextgarden.net/tex/context/modules/mkiv/m-fields.mkiv.
There you have the validation script, but I’m afraid this is Greek to me.
But guessing from your homepage you understand Greek ;).
Na ja, auf Spanisch sagte ich auch »das kommt mir Spanisch vor«. Es klang sehr komisch (ich bin selber Spanier), aber genau diese ist die unverstándliche Sprache auf Deutsch ;-).
Am 2017-03-14 um 18:57 schrieb Pablo Rodriguez:
Does it make any sense to have a module that doesn’t retain the content of the fill-in fields?
No ;)
Maybe it would make sense to implement it with no default validation. Does it make sense to you, Hans? It would help a lot to newbies, since the wiki has \fillinfield as a simple way to add these fields.
How should I define the new \fillinfield command? Would it work removing validation from the command? I’m sorry, I’m not running Windows and I have no way of testing it. Besides the fact that JavaScript is beyond my knowledge. [...] Yes, that works. You can leave out most of the parameters.
Many thanks for testing it. I have another issue with the width, but I have to find the conde first. Many thanks for your help, Pablo -- http://www.ousia.tk
On 03/14/2017 07:27 PM, Pablo Rodriguez wrote:
On 03/14/2017 07:06 PM, Henning Hraban Ramm wrote:
Am 2017-03-14 um 18:44 schrieb Pablo Rodriguez: [...]
There you have the validation script, but I’m afraid this is Greek to me.
But guessing from your homepage you understand Greek ;).
Na ja, auf Spanisch sagte ich auch »das kommt mir Spanisch vor«.
Da meinte ich »auf Deutsch sagte ich...«. (Natürlich war das ein Felher.)
I have another issue with the width, but I have to find the conde first.
No “conde”, but code. Just a typo. Here is my code: \starttext \setupinteraction [state=start] \usemodule[fields] \setupfieldcategory[fillinfield] [fieldbackgroundcolor=yellow,validate=] En \fillinfield[lugar]{vamos a dar un gran lugar}, a \fillinfield[dia]{99} de \fillinfield[mes] {febreromarzo} de \fillinfield[anyo]{9999}. \blank[big] En \fillinfield[lugarfirma]{vamos a dar un gran lugar}, a \fillinfield[diafirma]{99} de \fillinfield[mesfirma] {febreromarzo} de \fillinfield[anyofirma]{9999}. \stoptext My question is the command syntax: \fillinfield[tag]{text} I have just accidentally discovered that the width of the fill-in field is set from {text}. But if [tag] is wider, the field will be wider and wrong positioned. I have tried to understand this in m-fields.mkiv, but I don’t get anything there. Is this a bug or what am I missing? Many thanks for your help, Pablo -- http://www.ousia.tk
participants (3)
-
Henning Hraban Ramm
-
Henning Hraban Ramm
-
Pablo Rodriguez