Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6862603
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T02:40:52+00:00 2026-05-27T02:40:52+00:00

Running into strange behaviour with flex 3.5. Here is a minimal code: build.xml target:

  • 0

Running into strange behaviour with flex 3.5. Here is a minimal code:
build.xml target:

<target name="player">
        <mxmlc
            file="${APP_ROOT}/player.mxml"
            output="${APP_ROOT}/player_old.swf"
            keep-generated-actionscript="false"
            static-link-runtime-shared-libraries="true"
            debug="false">
            <load-config filename="${FLEX_HOME}/frameworks/flex-config.xml"/>
            <source-path path-element="${FLEX_HOME}/frameworks"/>
            <compiler.library-path dir="${APP_ROOT}" append="true">
                <include name="lib"/>
            </compiler.library-path>
        </mxmlc>
</target>

player.mxml:

<?xml version="1.0"?>
<PlayerApp
xmlns="*"
xmlns:fx="http://www.adobe.com/2006/mxml">
</PlayerApp>

PlayerApp.as:

package {
import flash.display.Sprite;
import flash.media.Video;
import flash.events.*;

    public class PlayerApp extends Sprite {
        public function PlayerApp() {
            this.loaderInfo.addEventListener(flash.events.Event.INIT, init);
        }

        private function init(e:Event):void {
            this.addChild(new Video());
            trace("loaderInfo: "+root.loaderInfo.width+"x"+root.loaderInfo.height+"\n");
            trace("root stage: "+root.stage.width+"x"+root.stage.height+"\n");
        }
    }
}

the object:

<object width="320" height="240" id="_261178285" name="_261178285" data="player_old.swf" type="application/x-shockwave-flash">
<param name="allowfullscreen" value="true">
<param name="allowscriptaccess" value="always">
<param name="quality" value="high">
<param name="cachebusting" value="true">
<param name="wmode" value="opaque">
<param name="flashvars" value="config={irrelevant}">
</object>

Running all this with a debug player produces the following trace:

loaderInfo: 500x375

root stage: 320x240

This leads to a situation where a Video(contained within a Sprite) added to the app is only displayed as 250×154 or so in size as the 500×375 is squeezed into the 320×240 element it is contained within on the page.

Onward to the question: Is it possible to avoid this bug in any way so that the swf will still work with flash version 9.0.115. I also would rather not hard-code the size in the build.xml file, as the player size could change in the near term future.

Disclaimer: I’m using flex 3.5 as flash player 9.0.115 must be supported AND flash 9.0.115 must be supported because of corporate customers (Even 9.0.115 seems to be too much asked for some.) I also noticed I can compile the .as without the .mxml, but I left it here as is.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T02:40:53+00:00Added an answer on May 27, 2026 at 2:40 am

    Have a look at Stage.scaleMode resp. the scaleproperty on object/embed tags.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm running into a strange problem. In the following sample code, if I set
I'm running into a strange problem when using unittest.assertRaises . When executing the code
I'm running into a strange result here and am not sure if it is
I'm running into a mental roadblock here and I'm hoping that I'm missing something
I've been running into this problem with Flex for nearly a year, and each
I'm running into a common pattern in the code that I'm writing, where I
I am running into an strange behavior when using NSOpeation. I am calling a
I'm running into a strange issue on Vista with the Performance monitoring API. I'm
I am running into a strange problem. I simply want to display a loading
I am running into a strange issue with 'parfor' in Matlab. Most of the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.