Returning from a longer weekend I find 2.4a1 released (without any prior
warning) with a lot of really new features, some of which seem to
indicate the beginning of further development towards real HTML and
browser capabilities and others a new approach to handle painting and
images.

We have now - among a lot of other things - embedded pictures, linktext,
a different handling of transparent images, new visual effects, and,
indeed,  a long-awaited feature: groups that need not be backgrounds !
Congratulations, connected with the expectation that everything will
work fine after the alpha- and beta-periods are over (as Scott
mentioned: "This is an *alpha-test* release, which means lots of stuff
is still broken and/or missing.").

I hope the new helpfiles will be out soon with detailed information
about the syntax of the new features, e.g. about the new visual effects,
which I could try out only partially (where do you find the
"4CC"-abbreviations and what are the special options numbers for the QT
effects? How do I work with the saved files of the "answer effect"
substack? I tried to use them with and without their extensions ("visual
effect implode.qfx"), but no effects took place.)-

Two observations:

- rotating images

I tried to rotate an image around its axis with

"repeat with i = 1 to 360
      rotate image 1 by 1
end repeat"

which resultated in a progressively slower rotation up to i about 40,
when the rotation came practically to a standstill. Maybe this feature
is only for a single rotation with a certain angle?

- importing text or images

When trying to import text into fields or images into the stack the
import dialogs do not display files until you type in an extension (like
*.txt or *.jpg).
Also, it is impossible to import images from a subdirectory if Metacard
itself is in another subdirectory - this problem has occurred before in
earlier releases.

Regards,

Wilhelm Sanke



Archives: http://www.mail-archive.com/metacard@lists.runrev.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to