From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Forms and JavaScript
Date: Tue, 6 Oct 2015 10:34:50 +0600 [thread overview]
Message-ID: <6A17E262-6434-47B1-8477-DBD9AE07A13C@fiee.net> (raw)
In-Reply-To: <FEB76260-D021-423C-A46E-5AE205C79FE6@fiee.net>
http://wiki.contextgarden.net/Widgets
Again working with widgets, this bug or feature – JavaScript code is only copied to the PDF if it’s used in a \goto – is still open.
Additionally, I found that \setupfields (plural) doesn’t work, I need to setup all formatting in each \setupfield.
I found another issue with workaround:
http://wiki.contextgarden.net/Tabulate#Itemization_or_framed_objects_inside_a_tabulation
You need to set "\tabulatesplitlinemode \plustwo" if you put widgets in a tabulation.
Is there any reason not to set this per default?
Am 2015-04-03 um 11:06 schrieb Henning Hraban Ramm <texml@fiee.net>:
> Am 2015-04-02 um 21:07 schrieb Rik Kabel <context@rik.users.panix.com>:
>
>> On 2015-04-02 03:42, Henning Hraban Ramm wrote:
>>> while trying to create some interactive forms using latest beta (MkIV), I found that JavaScripts are only then copied into the PDF, if there’s a \goto referencing a JS function.
>>>
>>> According to the old widgets manual I thought I could set default values of fields calling JS functions or variables as [JS(MyFunc)], but that doesn’t work.
>> Greetlings Hraban,
>>
>> This appears to be a pdf reader problem. On Win 8.1, Windows Reader and Chrome both show an editable field; Firefox and Sumatra show a non-editable field.
>
> That’s not the problem, creating fields works great. Since JS works (probably) only in Adobe products anyway, I don’t care about other viewers.
>
> But JavaScript code (within JSpreamble or JScode sections) is only copied by ConTeXt into the PDF if there’s a call of \goto to one of the defined JS functions.
> Additionally, calling JS functions for default values of fields doesn’t work like it did in MkII (and like it’s documented in m-widgets.pdf).
>
> JS in PDFs is not easy to handle, but ConTeXt should at least copy my code into the PDF as it’s documented and used to work in MkII.
>
>
> Greetlings, Hraban
> ---
> http://www.fiee.net
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-10-06 4:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 7:42 Henning Hraban Ramm
2015-04-02 15:07 ` Rik Kabel
2015-04-03 5:06 ` Henning Hraban Ramm
2015-10-06 4:34 ` Henning Hraban Ramm [this message]
2015-10-06 23:18 ` Hans Hagen
2015-10-07 9:56 ` Henning Hraban Ramm
2015-10-07 11:13 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6A17E262-6434-47B1-8477-DBD9AE07A13C@fiee.net \
--to=texml@fiee.net \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).