Diagnosing this was confusing, because the build actually runs Flash Debug 
Player in two ways (on Windows):

1.  Directly, from FLASHPLAYER_DEBUGGER.  i.e. %FLASHPLAYER_DEBUGGER% 
...\Test.swf

2.  Default file association.  i.e. rundll32 url.dll,FileProtocolHandler 
...\Test.swf

So when some projects ran it using #1, it would work (my FLASHPLAYER_DEBUGGER 
points to Flash Debug Player 13).  But when other projects ran it using #2, it 
would require manual intervention (my default file association was Flash Debug 
Player 32).

For some reason, my Flash Debug Player 32 won't run the file from command-line, 
at all.

I finally gave up and changed my default file association to use Flash Debug 
Player 13, as well.



On 7/10/2021 1:49 PM, ?Yishay Weiss? wrote:
Is the swf extension associated with your standalone flash player? As I recall, 
on Windows it needs to be.

My CLT-L09. On O2.


-------- Original message --------
From: Edward Stangler
Date: Sat, 10 Jul 2021, 04:36
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Some tests require manual intervention in Flash Player?
Sometimes, while running "ant" to do a full build, and during a project
test (especially Basic), it will open Adobe Flash Player 32 and wait for
me to manually open the given FlexUnitRoyaleApplication.swf before the
test runs.

Is this normal, or a race condition?  It gets old quickly when doing a
full build and many projects.

(ant basictests works fine.)

Here's an example:

test:
    [mkdir] Created dir:
c:\somewhere\royale-asjs\frameworks\projects\Network\src\test\royale\out
[royaleunit] Validating task attributes ...
[royaleunit] Generating default values ...
[royaleunit] Using the following settings for the test run:
[royaleunit]    ROYALE_HOME: [c:\somewhere\royale-asjs]
[royaleunit]    haltonfailure: [true]
[royaleunit]    headless: [false]
[royaleunit]    display: [99]
[royaleunit]    localTrusted: [true]
[royaleunit]    player: [flash]
[royaleunit]    port: [1024]
[royaleunit]    swf:
[c:\somewhere\royale-asjs\frameworks\projects\Network\src\test\royale\FlexUnitRoyaleApplication.swf]
[royaleunit]    timeout: [90000ms]
[royaleunit]    toDir:
[c:\somewhere\royale-asjs\frameworks\projects\Network\src\test\royale\out]
[royaleunit] Setting up server process ...
[royaleunit] Starting server ...
[royaleunit] Opening server socket on port [1024].
[royaleunit] Waiting for client connection ...
[royaleunit] Entry
[c:\somewhere\royale-asjs\frameworks\projects\Network\src\test\royale]
already available in local trust file at
[C:\Users\myuser\AppData\Roaming\Macromedia\Flash
Player\#Security\FlashPlayerTrust\royaleUnit.cfg].
[royaleunit] Executing 'rundll32' with arguments:
[royaleunit] 'url.dll,FileProtocolHandler'
[royaleunit]
'c:\somewhere\royale-asjs\frameworks\projects\Network\src\test\royale\FlexUnitRoyaleApplication.swf'
[royaleunit]
[royaleunit] The ' characters around the executable and arguments are
[royaleunit] not part of the command.
[royaleunit]

And then it hangs until I switch to the Adobe Flash Player 32 window
(that it spawned) and I manually open:


c:\somewhere\royale-asjs\frameworks\projects\Network\src\test\royale\FlexUnitRoyaleApplication.swf


Reply via email to