A Flash Developer Resource Site

Results 1 to 4 of 4

Thread: About 4.9.8.4 and backward compatibility

  1. #1
    Senior Member kusco's Avatar
    Join Date
    Nov 2001
    Posts
    681

    About 4.9.8.4 and backward compatibility

    For a number of years, until early 2007 when 3FDA adopted Actionscript 3, the following properties were used to control position and scale ...

    element.position.x
    element.position.y
    element.scale.x
    element.scale.y

    3DFA now uses the Actionscript 3 properties ...

    element.x
    element.y
    element.scaleX
    element.scaleY

    ... and also allows Actionscript 2 properties ...

    element._x
    element._y
    element._xscale
    element._yscale

    The older style properties were still allowed for the sake of compatibility with older projects. Unfortunately, the old property names now clash with some third party Actionscript 3 class libraries, and so they've been abandoned in 4.9.8.4.

    If you have an old project that still uses these properties, you can easily update your project using Menu/Edit/Replace ...

    Set the "Replace in all elements" option and replace ...

    .position.x with .x
    .position.y with .y
    .scale.x with ._xscale
    .scale.y with ._yscale

    Actionscript 2 scales need to be used here because they range from 0 to 100 like the old properties did. Actionscript 3 scales range from 0 to 1 and are recommended for all new projects.
    Cheers,
    kusco
    (3DFA Support Team)

  2. #2
    3DFA hobby scripter LewxX²'s Avatar
    Join Date
    Jul 2006
    Location
    Germany, Karlsruhe
    Posts
    198
    hmm .destroy() don't work anymore, too

    is there a new function for that?
    sorry for my bad school English
    btw. visit my Page: projects.lewxx.de
    or lewxx.de (<= German)

  3. #3
    Senior Member kusco's Avatar
    Join Date
    Nov 2001
    Posts
    681
    .destroy() is still there. For some time it has required the "Cloning options" feature. Look at the Clones sample.
    Cheers,
    kusco
    (3DFA Support Team)

  4. #4
    Member
    Join Date
    Jun 2007
    Location
    Germany
    Posts
    76
    Why doesn't the .clone() function require the "Cloning options" feature? Is it just a bug or is there a reason for it?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  




Click Here to Expand Forum to Full Width

HTML5 Development Center