On Wed, Mar 24, 2010 at 10:23 AM, Michail Vidiassov <mas...@iaas.msu.ru> wrote:
> Dear All,
>
> I notice that broken code for inserting movies uses
> node.write in codeinjections.insertmovie (in back-pdf.lua),
> while figures.checkers.mov (in grph-inc.lua) expects text return
> from codeinjections.insertmovie to feed to "texsprint(ctxcatcodes".
>
> The 3D annotation code (it also seems not to work) has
> node.write variant commented out and replaced with
> "texsprint(ctxcatcodes" with "brrrr" comment!
>
>   local annot, preview, ref = backends.pdf.helpers.insert3d {
>      ......
>    }
>  -- node.write(pdfannotation(width,-height,0,annot()))
>    texsprint(ctxcatcodes,format("\\pdfannot width %ssp height %ssp
> {%s}",width,height,annot())) -- brrrr
> --~     if ref then -- wrong ! a direct ref should work
> --~
> texsprint(ctxcatcodes,format("\\smash{\\pdfrefximage%s\\relax}",ref)) --
> brrrr
> --~     end
>    texsprint(ctxcatcodes,"\\stopfoundexternalfigure")
>
> And the question is: does it make sense to try to make the current 3D
> annotation handling code work by complaining to the maintainers and/or
> fixing it myself or nothing is supposed to work till migration to from
> "texsprint(ctxcatcodes" API to "node.write" API is complete?
I'm pretty sure that I still don't understand much , but
I have written an article for including swf in mkiv , cfr
http://wiki.pctex.com/index.php/PracTeXJournal

PracTeXJournal should be on-line next month,
and I have planned  2nd part x next issue.

I'm watching at your u3d files to maintains same style.
-- 
luigi
___________________________________________________________________________________
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
___________________________________________________________________________________

Reply via email to