Flash 8 Publish Bug?

Hi - I have a strange problem when publishing Flash movies
using Flash 8. I live in the UK, and naturally use the UK Keyboard
layout, which means among other things, that my @ key is almost
next to my Return/Enter key. In the US, the @ key is above the
number 2.
The thing is, when I publish movies in standard Window mode,
the keyboard layout is correct, and uses the UK layout that I have
my PC set-up for. However, if I publish my movie in Transparent
Window Mode, my keyboard switches to US layout, and if I need to
enter an e-mail adddress into a transparent movie, I need to use
the Shift+2 combination to get the @ sign, where normally, in
normal Window Mode, I can use the UK Shift+' combination. I can't
understand why using normal Window Mode and Transparent Window Mode
should change the way my keyboard layout works! Very strange.
Is there any kind of workaround for this bug, as I need to
publish a transparent movie that requests e-mail input, and most UK
users do not know the US Shift+2 combo to get the @ sign.
I hope this makes sense - and hope that someone can help me
on this.
Just to clarify: In published movies, In Window Mode Shift+'
gets me the @ sign in input boxes. If I publish in Transparent
Window Mode, I have to use Shift+2 to get the @ sign in input
boxes.
Thanks for any help.

I see that 'Marke' didn't get your attention for the same
thing(?) Now people will see your own answer show up as 1 answer,
they'll now assume I've had my question answered. Please mind your
own business, and go and discipline someone else please. You've
made me need to post it again now!

Similar Messages

  • Publish bug Cap4 (0KB)

    We have observed a publishing bug which results in .htm files of 0KB on multiple machines publishing different projects.
    Often, Cap4 simply does not complete the publishing operation and just hangs w/o ever show the "View Ouput" option and green checkmark.
    Reboots don't fix it, but if I keep at it, eventually I can get a project to publish after multiple reboots. I typically use Flash 8 but I have the bug with 8, 9, or 10.
    We'll keep recording this bug in our logs, but we have only ever observed it in Cap4.
    thanks,
    Jon

    I believe I spoke too soon.  After further testing, I encountered the problem again and am unable to figure out the root cause of the problem.  The problem may be due to the webkit-tap-highlight being added to the div tag.  I am still seeing the problem when nesting text inside a square inside edge animate.  However, I don't see it consistently and I have no idea where the webkit-tap-highlight is originating from.
    Has anyone else encountered this issue when publishing in Edge Animate?

  • Actionscript 2 and Flash Publish Settings

    Hi Everyone,
    I have posted a couple questions as of late and received fantastic support from other members (Thanks K-Glad).
    I do have what I'm assuming to be a basic question however I cannot find an answer for it.
    I added some login script to a page as listed below.
    stop();
    eval("$version");
    appname="mikesapp"
    loadVariablesNum("http://bars.bevinco.com/mike/newlogin.php", 0, "POST");
    //This verifys the users status and forwards them to the portion of the website they are authorized to access. Frame 100 = Regional Access, Frame 200 = Franchise Access, Frame 300 = Employee Access and Frame 400 = Denied Access and Back Button
    this.onEnterFrame = function () {
        if(_root.checklog == 100){
            _root.gotoAndStop(5);
        if(_root.checklog == 200){
            _root.gotoAndStop(10);
        if(_root.checklog == 300){
            _root.gotoAndStop(15);
        if(_root.checklog == 999){
            _root.gotoAndStop(20);
    My Question
    When testing this movie, I found that it was not moving to the section of the flash file that is relative to their "authorization level". I.E. I manually had my PHP echo back to flash, advising that REGIONAL ACCESS was used therefore it should be move this user to FRAME 5 of the file.
    I found that it was staying stuck on the first frame and not moving beyond the 1st frame which I thought had something to do with the stop(); that is listed at the top of the actionscript.
    However, when I changed the FLASH PUBLISH settings from Flash Player 8 to Flash Player 6, it works flawlessly.
    I attempted to publish using Flash 7 however it appears FLASH 6 is as high as I can go without loosing it's functionality.
    I'm curious WHY and will this limit our users from using the site if they have a lower version of Flash installed on their CPU?
    I have attached the project FLA file and the PHP file, being used on the server to manually tell this file that a REGIONAL has signed in or someone with "100" level status.
    As always, thanks in advance to anyone that has taken the time to read this post.
    Cheers,
    Mike

    checklog is a string (even though it looks like a number to you).  flash 6 allowed quite a bit more code sloppiness than later versions.  so, it's very common for users to find publishing for fp6 works, while publishing for fp's higher breaks their code.
    you should use:
    this.onEnterFrame = function () {
        if(_root.checklog == "100"){
    delete this.onEnterFrame
            _root.gotoAndStop(5);
        if(_root.checklog == "200"){
    delete this.onEnterFrame
            _root.gotoAndStop(10);
        if(_root.checklog == "300"){
    delete this.onEnterFrame
            _root.gotoAndStop(15);
        if(_root.checklog == "999"){
    delete this.onEnterFrame
            _root.gotoAndStop(20);

  • Firefox Flash Plugin bug?

    Hi everyone,
    I have multiple Flex Applications (wrapped as portlets in
    Liferay) working on the same page at the same time in separate
    flash players, of course.
    When I access the page by Mosilla Firefox browser, all page
    portlets get reloaded after the last one is initialized.
    And the worst - each of them gets initialized again - it
    means that all data gets loaded again. This is proved by log
    records: in case of Firefox each portlet loads data twice, in case
    of using IE - once.
    Have you ever faced the same problem? Is it a Firefox Flash
    plugin bug or what?
    Thanks in advance.

    Updates:
    I've opened a bug with Adobe regarding this issue:
    http://bugs.adobe.com/jira/browse/FP-4362
    Also, the Cancel operation on a FileReference causes the same issue to happen as does loading.  I really think it's an operating system focus issue.
    UPDATE:
    Looks like this has already been tracked and is scheduled to be fixed:
    https://bugs.adobe.com/jira/browse/FP-2785

  • Flash MX to Flash 8 bug??

    Hello. I am trying to update a file (~5 MB) built in Flash MX
    using Flash 8. Everything works fine with the file until I open the
    actionscript window. The file totally slows down to the point the
    hour glass shows up everytime I pick an object in the main stage or
    select a cell in the timeline. Is there a bug in Flash 8? Is there
    a bug in my actionscript? What can I do to solve this?
    I do not want to rebuild the file or use MX since there is
    some upgrades in 8 that solves some publishing issues I had with
    MX. Thanks in advance.

    Big fla files generally are potential problems unless they
    might just contain a single asset like a large image -- but still.
    Try save as
    Try save and compact
    Perhaps the AS can be moved to a external AS file and you can
    use #include
    If your scene 1 timeline is not too involved, then copy
    library items to a new fresh Flash 8 fla and recreate the scene 1
    timeline.

  • Flash CS4 Bug saving to external drive?

    I discovered last week when teaching my Flash class that in saving FLAs to my USB drive, and THEN testing/publishing, the AS3 code was ignored in the resulting SWF?EXE files.  I duplicated the situation with multiple computers, mutliple external drives and multiple FLA files. I even tried it at differnt locations (home and campus). The problem is only related to CS4 with Actionscipt 3.  Both CS3/AS3 and CS4/AS2 test/compile as one would expect. Save the CS4/AS3 file to the internal C: drive and then test/publish everything works fine. Go figure! WHy would the save location make any difference? I thought perhaps it was a PATH environment variable issue, but putting the external drive path in the PATH statement caused no effect.
    Here's the information I'm providing to my class tonight. Anyone else encountering the same? BTW, I upgraded to release 10.0.2 but to no avail.
    THE PROBLEM:
    I think I discovered a pretty major bug in Flash CS4. When creating an ActionScript 3 file (with scripts written on the timeline) and saving the FLA source to an external drive (such as a USB thumb drive) and then testing (Control > Test Movie) or publishing (File > Publish), the AS3 code is ignored in the resulting SWF or EXE. If you save the file to the C: drive and then test/publish, it works fine. I tried this on several computers with several different FLA files and differing script, with several devices including a network drive – all with the same result.
    I posted the problem to the ActionScript forum at adobe.com and contacted tech support (via email) but have yet to receive any useful feedback.
    SOLUTIONS:
    OPTION 1: Save your FLA to the hard drive before testing. You can create a temporary folder on the desktop of the campus computers or should have access to C:\TEMP. So save your files there and at the end of you session, be sure to copy the files (both the FLA and any published files) to your USB for safekeeping. When updating your FLA, first copy it to the internal C: hard drive, then make changes and test, etc.
    OPTION 2: AS3 code written to an external .AS file does work when compiled. But this really is beyond the scope of this class and adds a lot of complexity.
    OPTION 3:  Use Flash CS3 – works fine in CS3, but of course you can’t use any of the cool new CS4 features such as new motion tweening, and inverse kinematics (IK bone structures).

    Susan,
    Would the File > Archive Project do what you want?
    Don S.

  • Is This a CS4 Flash Remoting Bug?

    I think I have discovered a bug, but am looking for others to comment and maybe somebody knows of somebody else that has experience with this issue.
    I have a very large flash app I am working on for a multi-user RPG game, it relies heavily on flash remoting via AMFPHP so that flash clients logged into the game may communicate with each other and the main game server which handles database storage, the game heartbeat functions,etc.
    I have been developing the app on Flash CS4 for Windows and never have had any trouble, it works fine in the IDE environment when testing the movie and the published version works fine as well.
    Now I have a Mac version of CS4 and I am getting some crazy problems running the app in Test Movie mode in the IDE.
    After I start the app in Test Movie mode and run it for a few seconds all flash remoting stops working, the game continues to run and no error messages are generated but all of the NetConnection calls do no do anything, they do not connect, they generate no errors. Ok, thats strange enough but now, if I kill the Test Movie and rerun it via Test Movie no NetConnection calls are made and the initial .connect call does not go through, I have watched the server logs on the other end and no attempts to reach the gateway.php are made. This continues until I unload all of the .fla and .as files associated with the project and then reload them, and then it starts again, works the first time for 5 seconds or so and then all NetConnections stop completely.
    So to summarize what I think is a bug specifically for the Mac platform of Flash CS4 Professional:
    1. Projects works fine in Flash CS4 for Windows
    2. In Flash CS4 for Mac, the project runs for about 5 seconds in Test Movie Mode and then all NetConnection activity stops
    3. No errors are generated for the NetConnection
    4. Continues to fail even restarting the project until I close the files and re-open them in the IDE
    Sounds like a bug, does anybody know of others with this problem, or does anyone have anything I can try?
    Thanks,
    Andy

    The application doesn't hang but the TextBlock ends up on top the Button when you set its Text property. That's why you cannot click on the Button.
    If you set the Text property of the TextBlock in the XAML markup you won't be able to click the Button when you run the app because of the same reason:
    <TextBlock x:Name="OutputMsg" Text="sample text"
    Margin="0,200,0,0"
    HorizontalAlignment="Center"
    FontSize="18" />
    The solution is, like you have already discovered, to put the TextBlock in the StackPanel so it ends up
    below the Button and not on top of it in the same Grid.
    Please remember to mark helpful posts as answer to close your threads and then start a new thread if you have a new question.

  • Help - Publishing Bug

    Hi there! Wondering if any of you could give some advice to
    me about a bug when I'm publishing. I'm new to Captivate (I've only
    used it for 10/15 days)
    and you might know the solution.
    The Problem
    Whenever I seem to publish a Captivate SWF file and it has a
    button linking to a page on the internet, it won't work. You can
    click it a million times, but it just makes a "click" and doesn't
    do anything.
    However, when you use the built-in "preview" function in
    Captivate it works fine, so there's not a problem with me editing
    the button incorrectly.
    If you could help me
    ASAP
    then I would be more than please.
    Regards,
    Jakey

    Hi Jakey and welcome to our community
    I know you said you published this file, but are you running
    it locally? If so, maybe you need to visit the Flash settings page
    and add the folder where your .SWF is stored to the list of
    locations. Following is a link to a tutorial I created on what to
    do.
    Click
    here
    Cheers... Rick

  • Flash Player bug still not fixed yet ?

    I had to do a system restore to get back to a working version
    of adobe flash player - i put up with no flash for a week, but my
    sister thinks I've downloaded a bug onto her machine because there
    is obviously something up with this latest version of flash.
    it says it's successfully installed, shows the little moving
    picture etc. then you go on to myspace or jibjab or anything cool
    with flash in it and it doesn't work.
    Like I said I've had to use a system restore for the first
    time in years as I guessed it was a flash bug pretty quick as I
    monitor my updates.
    Anyone know if adobe are ackwoledging & fixing this bug ?
    - it would be handy to know when it is safe to install the latest
    flash player that works.
    I'm not a techie so have no intention of poking inside my
    machine or it's settings - just wierd how adobe haven't told
    website that use the product that services may be affected - so
    they can warn customers not to download the latest player until
    adobe have fixed the problem!

    The same thing happened to me. I've tried so many things -
    but nothing works.
    Just like you, I download flash, it installs successfully -
    it seems - then I go to other sites and it doesn't work anymore.
    Now I have to install flash everytime before I open up my browser,
    then it works for a website or two - then it fails again.
    Is this happening to anyone else?
    I have a brand new Mac intel 15 inch laptop - newest
    operating software.
    I have all my updates, etc,... updated & this is
    ridiculous.
    -mcgrafx

  • Another Flickr Publish Bug?

    I have no objection to the images I upload to Flickr being accessbile to public searches.
    Yet every time I publish or republish a photo, Flickr's setting ... "It is hidden from public searches" seems to get set for each image - even if I manually override for an individual image using the Flickr Web interface and then republish from LR it gets set back to this state - see below...
    I have set my Flickr user profile with ...
    so I don't think this behaviour is being caused by Flickr...
    and I cannot see any settings at the LR Flickr Publishing settings which would cause this ...
    Any help in either correcting my lack of understanding or confirming it a bug would be appreciated.
    Many thanks
    Alan.

    I can confirm the bug in LR 3.0, it happens every time I republish.
    There is at least one other annoying problem caused by republishing. If you have posted the photo into a group thread (by copying and pasting the HTML), the link from the thread back to the photo gets broken when you republish. It shows up as "This photo is currently unavailable".
    I haven't downloaded LR 3.2RC yet to see if these issues have been fixed.

  • Flash CS5 bug

    My new installation of Flash CS5 acts very buggy.  Keyboard shortcuts stop working, and I can pick fill colors but not text or line colors - just have a gray box with a few horizontal/vertical lines.  Is this a known bug?  Is there an easy fix?  Closing and reopening the app fixes the keyboard shortcut problem, but then it returns.  Color choosing problem is persistent even after restarting app.

    Hi,
    Regarding picking colors - it sounds like you have the alpha value for text/stroke color set to 0%.  When you open the color picker, please check that the alpha field is at 100% (or anything but 0%).
    Regarding the keyboard shortcut problem - are all keyboard shortcuts not working or only some?
    Thanks,
    Nivesh

  • Flash audio bug on Firefox Mozilla on PC

    - Quoted from Bugzilla@mozilla:
    https://bugzilla.mozilla.org/show_bug.cgi?id=289873
    To see the problem, go to
    http://www.spellingcity.com
    User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
    rv:1.7.6)
    Gecko/20050317 Firefox/1.0.2
    Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1;
    en-US; rv:1.7.6)
    Gecko/20050317 Firefox/1.0.2
    When using flash players to play audio files, using 15
    players works, but more
    don't:
    WORKS =>
    http://freesound.iua.upf.edu/flashtest.php?x=15
    DOESN'T WORK =>
    http://freesound.iua.upf.edu/flashtest.php?x=16
    DOESN'T WORK =>
    http://freesound.iua.upf.edu/flashtest.php?x=20
    DOESN'T WORK =>
    http://freesound.iua.upf.edu/flashtest.php?x=40
    etc...
    This number is a GLOBAL number: if you open more tabs or more
    instances (making
    the count of flash players larger than 15) the player fails.
    Checked on about 4
    different computers and both OSX and Windows XP.
    Internet Explorer doesn't seem to have problems with more
    than 15 players, and
    using up to 100 players (or more) doesn't impose any
    problems.
    guess: problem is not related to audio, as it works in
    Internet Explorer and
    isn't OS-dependent.
    Reproducible: Always
    Steps to Reproduce:
    1.
    http://freesound.iua.upf.edu/flashtest.php?x=15,
    works
    2.
    http://freesound.iua.upf.edu/flashtest.php?x=16,
    doesn't work

    https://bugbase.adobe.com/index.cfm?event=bug&id=3539635
    https://bugbase.adobe.com/index.cfm?event=bug&id=3541557
    https://bugbase.adobe.com/index.cfm?event=bug&id=3541576
    Please add your vote. We're dying because of this issue.

  • Publishing Bug

    I have set up several shows that can be successfully rehearsed, recorded, and reviewed with VC 3. However, longer shows (3-5 minutes) freeze during publishing. I have used pack and go and tested the show on three different computers. I have even uninstalled and reinstalled VC 3. The problem will not go away and is predictable. The bug happens when a video clip avi or wmv is inserted into the show. In fact the freeze h happens when such clips are triggered. Is there a way to bypass VC 3s publisher? Can I extract the files and use a different program to publish? Does anyone know how to fix this bug?

    This sounds like a problem. I just purchased VC3 upgrade.
    I have been using an early version of Visual Communicator Plus. I have read about this problem a few other times on this forum. Only being able to publish three minutes of video, before it freezes, don't sound good. I'm curious, it sounds like a processor problem. What kind of processors are you using?

  • FLash 8 Bug using getURL

    I have created a Flash 8 button runnig in a menu frame that
    is supposed to open an html in the mainframe. Without regard to
    whatever fix I attempt it doesn't work. Finally I published it as
    Flash MX 2004 and it works exactly as it is supposed to.
    Three days I have been messing with this! Fix Flash 8 you
    morons!

    Yeah, I know. I was just venting and frustrated.
    I am stuck using frames because that what the customer has in
    place. I sent everything to another developer who doesn't have
    Flash 8, so I had to save it in MX for him. It ran on his system
    without problems. I then did a couple of experiements in publishing
    as both Flash 8 and Flash 7. Sure enough it works without problems
    published for the Flash 7 Player.
    No it is not my misunderstanding of how to do a getURL. It is
    a problem with Flash Player 8 (see threads on "mainFrame").
    Anyway... my apologies to the forum.

  • Lightroom 3 - Flickr Publish Bug

    I am experiencing an issue where when I publish images to Flickr they immediately show up as "Modified Photos to Re-Publish" and will not ever move to the "Published" section even though I have not changed a thing.
    Anyone have any ideas as to what I am missing?
    Thanks!

    Although not related to the original post – “Stuck in republish”, which I think is now fixed; here is my take on the situation you are describing -
    I suspect there is a bug in the LR software which is still present in LR 3.4RC.
    I believe this bug manifests itself in two ways when an attempt is made to republish an existing published photo …
    1)      If you are privately publishing and attempt to republish an existing photo, then LR sends a parameter (“Hidden” from public searches) incorrectly and out of bounds in accordance with the Flickr API, and Flickr quite rightly rejects it.   I suspect LR is sending values of 1 or 2 (Hidden or not) for this “hidden” parameter when it should be sending 0 or 1 to the set safety level function.
    2)      Probably related to the same technical reason as point 1 - if a non-private photo is republished then instead of the photo continuing to be made available in public searches it is now erroneously made hidden from public searches when it reaches Flickr – again 1 or 2 instead of 0 or 1.   This is somewhat annoying if you go through a re tagging exercise for the benefit of public searching only to find that they are now hidden from searches once re-published.
    I have seen no confirmation from any other user of point 2 above despite posting the question here ...   http://forums.adobe.com/thread/796350
    Further points …
    Since the Lightroom Software Development Kit contains a sample of the Lua code which is used for publishing, I have pointed to the actual lines of code I suspect are in error in this thread which also contains some technical dialog with Matt Dawson a Community Professional …
    http://forums.adobe.com/thread/821148?tstart=0
    I have raised a bug report with this technical detail, and raised a bug report for each of the two cases I mentioned above.     Hopefully this may result in some action, but I would suggest that if this important to you that you also raise a bug report, as there appears to be, to some an extent, a principle of - they who shout loudest or most often will get priority.
    As a side note … to cure the problem for the moment, although I don’t want to use third party software long term, I have adopted a Flickr publishing plugin by Friedl for my private publishing until this is fixed.    If you Google “Friedl Flickr” you will find it.     I have not yet decided to adopt this plugin for my public publish due to concern about the possibility of losing all comments and favourite tagging by other Flickr members – I simply do not know at this point.
    It is also interesting that the change log for this Friedl plugin on his web site also describes being tripped up by the same peculiarity present in the Flickr API which probably gave rise to this mistake by Adobe.    The Flickr API may have its peculiarities, but it is well defined and this is a Lightroom bug in my opinion.
    Alan.

Maybe you are looking for