Flash Pro is ignoring changes to my base class when publishing / debugging

Hi,
I hope this will be in the correct section of the forum.
I've been working with Actionscript 3 since a while now although most of the time I've just done straightforward coding using Flash Develop.
This is the first time I'm building a more or less complex project in Flash Pro.
Here's a quick outline of how the project is structured.
There is a swf file which holds a large set of components. Things like Buttons, Sliders, complex List components, etc.
All of them are written from scratch not using any existing components (reason being project requirements).
As someone with a heavy programming background I've done as little as possible in the timeline / frames, most of my code lives in classes which are attached to the components I've created in Flash Pro.
These classes handle all the functionality. These classes then usually inherit from a base class where some basic functionality lies that I need across all components.
The components outlined above are all marked for export and lateron imported into other swf files where they are used.
So far so good, all that works like a charm.
Now here's the actual problem.
Today I needed to make changes to the base class to change some fundamental behaviour across all components that inherit from said base class.
The change in itself was fairly simple.
However, every time I now try to debug or publish it will completely ignore any change I've made and use the previous version of my base class?
I can go as far as completely emptying my base class and every time I debug or publish it will do so using the base class from before. I can see at runtime that it is the previous version because of the behaviour of the inherited components.
That's what I don't get. Where does it take that version from? I tried clearing the publish cash, to no avail.
I can pace tracers, nothing. If I add code to the base class and make an error it will complain so when I try to debug or publish but once fixed, it won't use any of it. It's still behaving as if it's using a previous version.
What makes all this even weirder is that if I take that new code and place it into another class and inherit my components from this one, then the build will use that new verison with the new code. If I switch back to the old base class with exactly the same code inside it will ignore it again and once more behave as if its an older version of it.
I've been looking around the net but simply can't find what this could be caused by.
Now, sure, I could simply use a new class and inherit all my components from a different base class but that's rather unpractical.
What I would like to know is, why does Flash Pro ignore any changes to this class? Is this an issue with how I inherit my component classes from a base class? I kind of doubt it because it has been working like a charm before.
Could this be a Flash Pro issue?
This is also not the first time I've come across this problem. The previous time however, after much tinkering, it went away. Today, it didn't. I would really like to get to the bottom of this.
FYI: I'm running Flash Pro CC. I design my components in Flash Pro and do all my coding in Flash Develop.
Any help would be greatly appreciated.

Hmm, my classes live in a subfolder of where my fla files live. (This sub folder again is divided into further folders to organise the code)
I haven't actually setup any class paths. (default class path is set to .)
If I set the default class path to the folder where my code lives I get a ton of errors telling my that my package names don't reflect the location of my files.
edit: That was a mistake on my side. I've set the class path to where my code lives and made sure the package names still match up.
Unfortunately it still ignores my base class (which lives in a sub folder of the defined class path)

Similar Messages

  • Compiler ignores changes in a java class

    Hi,
    I made changes to the java class code, compiles correctly and not execute this new java code. The new code is ignored for the jdeveloper. I tried with several version like jdk1.4.2_06, jdk1.4.2_12,jdk1.4.2_13,jdk1.4.2_17. I need to work with 1.4.2.
    Thanks in advance.

    Hi,
    too many missing information make it hard to give any useful answer to this
    - which version of JDeveloper
    - what is the java code you compile
    - in which context do you execute the code ?
    Frank

  • Cannot compile Library project in Flash builder 4: Unable to locate specified base class

    I am migrating from Flex builder 3 to Flash builder 4, during that process I found that Flash builder could'nt compile Flex Library projects which contains components in the form of mxml files. Compiler throws "Unable to locate specified base class".
    I have narrowed it down to by creating a flex library project named test library, below its screenshot with its package structure
    ControlA is based on componentA
    when i compile this project, mxml compiler throws this error
    Unable to locate specified base class 'components.componentA' for component class 'ControlA'.
    I cannot upload project code because file uploads are disabled on this forum so I am going to paste the code for both componentA and controlA
    componentA
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Canvas xmlns:mx="http://www.adobe.com/2006/mxml" xmlns:local="*" width="400" height="300">
    </mx:Canvas>
    ControlA
    <?xml version="1.0" encoding="utf-8"?>
    <components:componentA xmlns:mx="http://www.adobe.com/2006/mxml" xmlns:components="components.*" width="400" height="300">
    </components:componentA>
    To further test it, I have made another library project with same package structure using pure AS3, and it compiled without errors

    It might be this happens and other errors if you forget to Run Flash Builder 4.5 Buritto and startup the other version FB4.
    It uses the same project listings and that can be confusing since you're not expecting the old version to be aware of new Buritto (MobileApplications) projects you added (thinking) only to the BETA version installed elseware no doubt.
    Well it might not be your problem but worthy of noting for other's I'm sure.
    Otherwise you've double checked you're using SDK 4.5 Hero with it too! right?

  • Cannot find Super class/Base class when extending VO

    I am extending a SQL based VO and when I select the extends in the VO Wizard step 7. I am unable to find the base class for the object and rowimpl. I have copied them in the class path and still they don't show up (but can see other classes) ? Could you please tell where am I going wrong?
    Thanks,
    Hari

    Well here is the deal - I have the whole of $JAVA_TOP/per directory in my class path and also under myprojects/oracle/apps/per directory. I have created a BC4J abc.oracle.apps.per.selfservice.appraisals.finalrate. Here is where I will be creating the new SQLVO. In the step 7 of VO Wizard there is extends button when I select and navigate through oracle.apps.per.selfservice.appraisals.server I don't see my FinalCompListVORowImpl class although I could see it in the navigator. Do I need to navigate to this level for step7 of VO Wizard or default it to oracle.jbo.server.ViewRowImpl? Also I have included the Java and xml files in my project. Your help is appreciated.
    Thanks,
    Hari

  • Why NTFS ignores changes in server side classes

    Hi,
    Following the developers guide I 'have some change to archive PublicObjects before freeing.
    All what I did, was to implement a extendedPreeFree method for a SubClass of S_TieFolder.
    When such a Folder is deleted, a copy is created and this copy will foldered in an other place.
    It works at expected for WEBDaV , WebUI , CUP, but the NTFS server seems to ignore it completely.
    Why the things go a other way vi a NTFS server and possibly (not tested yet) via SMB Server.
    Thanks in advance
    Regards
    Gunther

    Chris,
    Are you are talking about the Chapter 17 examples for Replacing the Server (S_TieFolderRelationship) and Bean (TiePublicObject) Tie Classes. If so, that is where I started out, but it never seemed to have any effect at all within the IFS NTFS Share. Therefore, I switched the implementation to S_TieDocument, overriding the extendedPreUpdate and extendedPreInsert functions. This is also, where I made a few discoveries.
    One is that if I placed my jar file before the repos.jar (as described in Chapter 17 Deploying Custom Tie Classes in the Jdeveloper IFS "library" class path along with my source directory. I was able to get system print messages, and debug inside my code in S_TieDocument.
    Two is that when you update the ACL of a Document, it automatically calls the update function to save that change. Therefore, I had to add a flag to disable my code in the extendedPreUpdate function to prevent a infinite loop.
    Even though my code works perfectly well when executed via the Jdeveloper IFS, the NTFS share still doesn’t act as if it is ever finding the code.
    Then I tried overriding the bean side (TieDocument) update function. Once again, the code worked perfectly well in Jdeveloper, but when we deployed it to the IFS server, it didn’t do anything. That is the frustrating part of this, is that I know my code works, but NTFS doesn’t give my any indication or output that my code is even being ran.
    I followed the deployment steps described in chapter 17. We even tried variants.
    We have tried variants on deployment, using a jar file; this was what got Jdevedoler wraith. We also attempted using the class path to oracle directory instead of the class directory. We also tried placing the classpath as the very first entry in the classpath list. Placing our path to just the oracle directory thinking that the class loader might be attempting to build “oracle\ifs\beans” off the directory in the class path instead of using the class object in the class path; modifying the ifsclasspath.cl (This is apparently that configures the default classpath for ifs classpath Nothing worked.
    The steps I used from Chapter 17 deploying Tie Classes to ifs. First, you compile the code. Secondly, you then your class file into following directory
    (“ifs_home\custom_classes\TieClassesoracle\ifs\beans”)
    Modify the evironment classpath, and finally shutdown and restart IFS to refresh the classpath. From what I have read, this should redirect ifs to use your new class instead of the original Tie Class.
    Mark Daly

  • Flash CS 5.5 Professional requires 32-bit JVM when publishing for iOS

    When trying to publish my file to AIR for iOS I get the following error:
    Error: This Java instance does not support a 32-bit JVM.Please install the desired version.
    I'm on Mac OS (Mavericks) and have both java 6 (which supports 32-bit) and 7 (which does not) installed. I've verified I can launch a 32-bit jvm from the terminal with "java -d32".
    Interestingly, it publishes to AIR with no problems when it's not to iOS.
    How can I get Flash to use the correct version of Java? I've tried setting JAVA_HOME to point to version 6 in /etc/profile with still no luck.
    Thanks for reading, I will really appreciate the help!!

    Ok, found the answer thanks to Christopher Caleb. Needed to upgraded CS5.5's bundled AIR from 2.6 to the current one, and it compiled with no errors. Directions are here for anyone that winds up having the same issue:
    http://www.yeahbutisitflash.com/?p=2949

  • Flash Pro Doesn't See Ipad - Debugging

    Hi. I have both Flash Pro CS6 and CC. For some reason, under the debug heading the option "on device via USB" is always greyed out, completely unselectable. This is strange because I am able to publish perfectly fine from flash builder. Do I need to do something extra to make flash pro aware that I am connecting an ipad?

    can you see your usb connected device in a file browser?
    have you ticked install application on connected ios device in the air for ios settings panel?
    with flash cc, did you click the refresh device list debug>debug movie>on device via usb?

  • Flash Pro CS6 - not enough JVM memory - change 128 to 256, flash doesn't start.

    Hi,
    working on very large projects, I often get the "flash ran out of memory for the jvm" error.
    Restarting flash does the trick for another couple of hours, until I get that error again.
    It opens the jvm.ini file to let me increase Xmx memory value.
    I change it from -Xmx128m to -Xmx256m
    I restart flash, get the error: "Error initializing Java Runtime environment. You may need to reinstall Flash"
    I change it back to -Xmx128m, and flash starts again.
    But obviously, I again get the "not enough memory" error.
    Am I doing something wrong?
    Also,
    after installing Flash Pro CS6, previously installed Flash Pro CS5.5 does not start, gives me the JVM initialization error all the time, regardless of which Xmx value I put for CS5.5

    back to square one again. The error message just popped up. So annoying.
    update:
    I removed some of the images I embed using the '[Embed tag'. And now it publishes again without the error. Weird because the published swf is only 1.8MB. Nothing crazy. So the problem seems related to embedding images using the [Embed tag...
    update 2 / FIX:
    Instead of using the embed tag to embed images I now have an 'assets' folder that I add to the AIR project (publish settings) that contains my images. Then I load the various images using the Loader. After an image is loaded I convert it to a Texture to use in Starling like so:
    var bitmap:Bitmap = new Bitmap(new BitmapData(currentBigTextureLoader.width, currentBigTextureLoader.height, true, 0x00000000));
    bitmap.bitmapData.draw(currentBigTextureLoader);
    bigTextures[aBigTexturesToLoad[nCurrentBigTextureToLoad]] = Texture.fromBitmap(bitmap);
    You can then use these Textures to display an image in Starling like so:
    var base:Image = new Image(bigTextures["CollectionBase"]);
    Bit of a workaround but al least I don't get the Java Error anymore

  • I need to change the height of a Captivate playbar using Flash Pro

    I need to change the height of a playbar in Adobe Captivate.  I have Flash Pro. I am very new to Flash Pro. I read.. "To change the height of the playbar, adjust the height of pbcBk_mc movie clip inside cpPlaybar symbol in Library".  The problem is I CAN'T FIND pbcBk_mc anywhere.  I see the cpPlaybar attrbute.  When I click on it and look at the timeline I am not seeing an attribute for pbcBk_mc or height.  Where in the world is it??

    You start with a source / authoring file for the "static" content (e.g., Name, Last:). Say this is an MS Word file.
    You master the "static" content..
    You keep this authoring file and have a backup of this file.
    You output a PDF and use Acrobat to build and fine tune the "form" (form = the form fields, not the "static" content).
    The authoring file  and output PDF (with form fields) gives you "rev 00".
    Now, you must change something in the "static" content.
    Open the authoring file and save as to a new version (e.g., "wordfile_v00"  becomes "wordfile_v01).
    Output this to "pdffile_v01".
    Use Acrobat to open the PDF form file "pdffile_v00". Save As to a new file name ("pdffile_v00update").
    Using Acrobat XI Pro the click-path Tools - Pages - Replace lets you replace a page or pages of "pdffile_v00update" with a page or pages from "pdffile_v01".
    This replaces the "static" PDF page content and does not affect the form fields on the page.
    (you may have to adjust position of form fields)
    Save "pdffile_v00update" to "pdffile_v01" to reflect the revised status of the PDF form file.
    Be well...

  • BUG - saving with both flash pro CS6 and CC causes library symbol names to change

    Concise problem statement:
    If you save with flash pro CC and then save with CS6, in the library panel, symbol names are changed.
    Specifically, pipes | and trailing spaces ("|Divider", "Divider ") get replaced by escape sequences ("&#124Divider", "Divider&#032" ...) Ampersands & and number signs # also get replaced, such that symbol names grow exponentially if you continue to save with both flash pro CC and CS6 ("Divider&#032", "Divider&#038&#035032", "Divider&#038&#035038&#038&#035035032" ...) This makes it difficult to transition a team from CS6 to CC.
    Sometimes, the original-name symbol remains, and an escaped-name symbol is also created. In this case, the children are removed from the original-name symbol, so it doesn't render anything to the screen; a mysterious, silent failure.
    Steps to reproduce bug:
    1. Create a library symbol named "|", save an xfl with flash pro CC, and close.
    2. Open, save, and close with flash pro CS6.
    3. Open, save, and close with flash pro CC.
    Results:
    A library symbol named "&#124".
    Expected results:
    A library symbol named "|".
    I submitted this bug with the bug form, and also with adobe bugbase (in case it isn't obsolete) - I'm just trying to maximize my chances of getting a fix.  Has anyone else encountered this bug?

    Hi,
    We are aware of this issue and its open for investigation internally. This issue is observed when you have certain special characters in your symbol names and try to open that file in Flash CS6. This happens due to a change in the way symbol naming is handled in Flash CC and in Flash CS 6.
    As a workaround, request you to use only Underscore or Hyphen as special characters while naming symbols or library layers etc.
    We shall update you as soon as this has been fixed.
    Thanks,
    Nipun

  • Flash ignoring changes to AS files

    weird problem with flash pro 8 - when I test project or test
    movie, changes to my .as files are not reflected. Doesn't matter
    whether I delete ASO files. To get the changes show, I have to
    either run it in debug mode (after which the changes show up when I
    run normally) or close and reopen Flash. This didn't always happen
    with my project, though I cannot pinpoint when it started. Any idea
    what's going on?
    thanks.

    BUMP

  • Flash Pro changes filename in app-descriptor, causing an error.

    How do I prevent Flash Pro from changing the <filename> in my app-descriptor? It's currently updating this node with the name of the application I'm compiling (to Android, iOS) which is throwing an error.
    Thank you.

    Simply because the schema, support and features of AIR are updated at a rapid pace to keep compliant with Google and Apple.
    There's been many old apps I've had that broke entirely during the OS6 update that were fixed in the next version. When I say broke, I mean shattered. Being the XML schema is updated so rapidly the interfaces for creating them in the apps themselves (especially relics like CS5.5) can't keep pace. Believe me, you want AIR to be updated as much and fast as possible to address potentially serious issues and open new long awaited features.
    How you're doing it now is probably the best way. I wait for FlashDevelop to tell me it's been updated, deny updating it, add/subtract whitespace and resave..
    I think the best possible thing would be for Adobe to consider breaking off the XML-specific portions of the interface into a separate panel. The destination of the IPA, signing credentials, etc all can be in a different panel so the XML isn't overwritten every time you set them at export. Then simply get used to the very verbosely commented XML file and hand-edit it from then on. It's a really simple file to learn anyhow and I gut mine of all unneeded settings and comments so it's 1/8th the size. If people are making apps, this file shouldn't scare them at all. The Apple developer section, references and provisioning portal? Now that's scary..

  • Adobe Flash Pro CC incompatible with windows 8.1

    Hi,
    I've installed adobe Flash Pro CC on windows 8.1 and it doesn't work  ! The program crashes...Does Adobe will correct this with a fix ?

    If Photoshop opens that pretty much rules out the GPU drivers being an issue (unless for some reason you disabled it which I doubt).
    I think you're right about 8.1. The tech requirements page hasn't been updated to say 8.1 yet at least:
    http://www.adobe.com/products/flash/tech-specs.html
    However the upgrade to 8.1 is mostly centered around user experience (having now read them). I honestly see nothing in the list of changes that has to do with graphics or audio which is usually the culprit.
    That leaves storage. One thing I do note is desktop booting (no user/password). I wonder if this has changed something permissions-based. More specifically if there's more (mostly unncecessary) security under the hood on a file basis now that computers can boot to desktop. I don't have 8.1 so I can't say. To find out, just right-click on Flash and start it as Administrator and it would answer that question (no permission issues).

  • Why is Flash Pro being deprecated??

    It seems like Adobe is blowing off Flash Pro more and more and I find it disturbing. 
    I develop prototypes for Android apps.  Flash is SOOOOO much better for prototyping and rapid, X-platform conceptualization than ANY other product out there. 
    Nothing else (e.g. Edge Animate, Axure, Proto.io, etc...) even comes close for designers to use! 
    I can create fully functional prototypes of anything at all, in 1/10th the time and with 10x the level of flexibility that can be achieved with a prototype built by some engineer in native Android. (As for the wonderful HTML5 that Adobe keeps pushing - give me a break!  Maybe in 5 years it'll catch up, but for now it doesn't compare to the power of Flash to meet the needs of a rapid, iterative design process.)
    The Flash Pro forum isn't even listed on the main page of Adobe Communities?  You have to search for it.  :-(

    I'm going to weigh in here as someone is both a designer and developing enterprise-level apps in Flash. I'd write a book about the concepts I use, which I call "semantic Flash" if I thought there were enough people interested in learning a whole new way of developing Flash to make it worth investing the time.
    I personally think the AS3 version of Flash is beautiful and elegant and the changes had to happen to make Flash a viable product for as long as it has lasted. However, what happened is that Macromedia dropped the ball when it came to Flash 9/AS3. I say Macromedia because the decisions that were made happened prior to the acquisition. For whatever reason, someone decided that large-scale development couldn't be done in Flash using the timeline, so they put all of their eggs in the Flex basket for that side of things. And really everything. If you recall, Flash Player 9 didn't actually work very well with the timeline, because Macromedia focused so many resources on making it work for Flex they didn't have much left for in Flash.
    Just seeing how the timeline actually does function, though, I believe there originally was someone on the team who had a vision of how this could work amazingly well with the timeline. I think that person probably left unfortunately before this vision could be conveyed to anyone else for whatever reason. So we were left with a dichotomy where "real developers" don't use the timeline and "designers" are completely intimidated by the code side. And this was something originated by how Adobe documented Flash and Flex in 2007. We now have very few people who can cheerfully marry both sides, mainly because many people see doing this as a little bit "icky."
    When I spot someone on these forums who I think has the ability and the interest to learn to do that, I'll try to coach them, but I know that I'm asking them to take a huge risk. In part that risk is because there are no resources on how to do it other than ones I wrote (and some of those resources are lost to the winds of history), but in part it's asking people to pick up parts of the functionality that haven't been fully beta tested because nobody does this. And you have to be really really good at this to even figure out what's going wrong, much less figure out a fix or a workaround.
    No, I don't know what it would take to fix this situation. I sort of doubt that it's worthwhile trying to change it at this point. My experience with Adobe is if you try to change their direction, even if it would benefit them to change, at best they'll ignore you.

  • Issues with Flash Pro CS5 on Mac

    Hi,
    I recently bought a MacBookPro 15", 2.4 GHz Intel Core i5, 4GB 1067 MHz DDR3 and CS5 Creative Suite. Built in Intel HD Graphics and NVIDIA GeForce GT 330M.
    Hi have some issues with Flash Pro:
    - when objects on the stage are quite big (for example a 800x3000 movie clip), it start showing strange colors and wrong position, however when double clicking the movie clip to edit it, it looks correct. Also no problem when publishing. See images attached, the first one is correct, the second one shows the problem, when editing the mc in the 2nd image i get the third image that is correct.
    Correct:
    Wrong:
    After entering editing mode:
    - after a while, when making a change in the stage or in the time line (deleting frames for example), it doesn't show it immediately, but i need to refresh the page. This happens more when opening many fla in the same time. Closing and restarting Flash fixes it, for a while.
    - after a while it doesn't show when selecting an object, the object looks like is not selected, however i can see that it is in the properties panel.  This happens more when opening many fla in the same time.  Closing and restarting Flash fixes it, for a while.
    Hi have been using CS3 and CS4 with less powerful computers before (always mac) and i never encountered these issues.
    Removing preferences and Application support files didn't help. I also updated Flash  to v. 11.0.1, but no joy.
    Does anyone know what's the problem?
    Thanks a lot.
    Mike

    Based on some searching and testing, it seems that if you redirect ~/Library/Application Support/Adobe/Flash CS5 to a location on the local hard drive, rather than the network account storage, the problem ceases.
    I hope this helps anyone else who may run into this problem.
    Take care,
    Branden

Maybe you are looking for