Broken JSFL Commands

Anyone at Adobe I could use your help!
I'm an experienced JSFL developer, and there's a few serious
bugs in the CS3 version of JSFL.
1. The library.updateItem() command causes the Flash
Authoring environment to completely crash. In my search for
information, I saw a post from another JSFL developer out there
with a
Text
similar
experience.
Even the most simple use of this command, such as this
one-line piece of code, crashes Flash:
fl.getDocumentDOM().library.updateItem("nameOfItemInLibrary.png");
2. The new fl.findObjectInDocByName() command and
fl.findObjectInDocByType() command don't work. Any attempt to use
them results in the error that the command is "not a function."
I'd like to know what is going on with this... Does Adobe
know about this? Are there any plans to fix this? Am I crazy? Is
there something wrong with my particular installation of CS3? If
the updateItem() command works fine in Flash 8... but not in CS3,
is this an indicator that Adobe has no intention to maintain JSFL
in future versions of Flash?
Also, here's one other question which is slightly
off-topic... Is there any chance of adding a JSFL command that will
tell you the location or pathname to a library bitmap's source file
on the hard-drive? This is a significantly useful bit of
information that cannot be accessed through JSFL in any other way.
Thanks for any information!

I'm also having problems with CS3 JSFL. In particular: this
doesn't work for me anymore.
fl.getDocumentDOM().library.itemExists("linkageID")

Similar Messages

How to export low quality png while using exportToPNGSequence jsfl command ?

how export low quality png while using exportToPNGSequence jsfl command ?

var mat=fl.getDocumentDOM().library[0].matrix;
mat.a=.5;
mat.d=.5;
fl.getDocumentDOM().library[0].exportToPNGSequence(file:///yourfile.png,startframe,endfram e,mat);

JSFL commands slow in CS5

The execution of JSFL files seems to have slowed down in Flash CS5. Or, at least, the updating of the display has been severely slowed down. I have a command I use all the time -- so much that I don't even think about it -- that worked fine in CS4 and earlier, but in CS5 it seems to execute too slowly. My command is a replacement for the "Step Forward One Frame" and "Step Backward One Frame" commands in the control menu (the "<" and ">" keys). I wrote them so that the selected symbols remain selected when going to a new keyframe. Of course, I use this all the time just like I did with the original "<" and ">" keys, and they need to run fast enough that I don't notice their execution time. They don't do that much processing at all, so it really shouldn't be a problem.
I also wrote some functions for profiling, and they indicate that the command is actually running in a reasonable amount of time (around 50ms). When I run it again immediately, though, the execution time balloons to about 300ms. Not only that, but in both cases the display takes its sweet time updating itself. It seems to wait until all activity is finished, and then updates. This means that when I execute the command repeatedly (keyboard-scrubbing the timeline) I don't get to see the current state of the stage until I stop completely and wait for it to update.
As I said before, I never had trouble with this in CS4 and earlier. So my question is: is there any way to tell Flash to update its display in a command, so that I don't have to wait for Flash to get around to it? Relatedly, is there any way to give the javascript interface a higher priority so it'll execute commands faster?

I can confirm this claim that JSFL code is running slower in CS5.
I've recently downloaded a trial version of CS5 to see if it be worth updating from CS3. I use my JSFL script to batch swf building, which include separating assets like jpgs into a separate swf file.
Now the JSFL code (which ran perfectly fine in CS3) takes significantly more time to execute in CS5, even to the point of crashing the Flash IDE quite consistently.
Are there more people who have similar JSFL problems out there? Are there any alternatives to get around this problem?

Broken sudo command

In an Adobe forum, while trying to find out why my latest Acrobat Pro XI was failing to install a user said it's possible the sudo was broken. To test go to Terminal and type sudo and it the message
"sudo: can't open /private/etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting"
showed they said to call Apple. I'm wondering what's up. Do I need a clean install of Lion (10.7)? Or is this something deeper?
Tom

Niel wrote:
Open the Disk Utility in the /Applications/Utilities/ folder and run repair permissions.
(78771)
Repair Permissions was tried many times, and even though it did change/fix the permissions on the said file, the issue of installing apps (in particular Adobe, but not limited to them) was still there.
I did do a clean intall (actually just a reinstall - not an erase/install/etc.) of Lion (10.7) then updated to the current (10.7.5) - along with all the other installs to bring up to date. And the test in Terminal resulted in the proper response. And installs went as they should - to completion with no "Failed to install."
Tom

Broken Keybinding - Command-Option-Right Arrow

Somehow, my system lost the ability to recognize cmd-alt-right. Yesterday it worked fine in Firefox and TextMate, where it was the 'move to next tab' command.
Today, something I did caused it to stop working completely. Most likely it was the mouse drivers I was trying to experiment with - Steermouse and USB Overdrive X.
I know it is not a hardware problem, because when I go to System Prefs -> Keyboard Shortcuts, it is recognized when I map it to a command. However, if I try to use that command, even through a mouse mapping, it fails.
Does anyone know where to start looking for something like this? I even thought about trying to search all files looking for \UF702 (right arrow key code), but I'm not sure how to do that.
It is really annoying, but obviously not that critical. Not worth waiting 3 hours for a Genius, or losing my machine for a week.

Apple Genius showed me that binding that key didn't work on his 10.5.2 iBook either. However, my friends MacBook Pro, which is the same as mine uses that key to switch tabs in applications (Firefox/TextMate) just fine. So something DID break, but it is hard to say what.

JSFL - Commands working in CS3, not in CS4 / CS5 (library.selectItem / library.expandFolder)

Hi there,
I have a script that works perfectly fine in CS3, but does not work in CS4 and CS5.
This script is called "selectInLibrary".
You guessed it, what it does is select/highlight in library the symbols selected on the stage.
My issues are with the "library.selectItem" and "library.expandFolder" methods. They are simply not working in CS4 / CS5.
If anyone can help me with this, it would be awesome.
Code goes as follow:
function selectInLibrary(){}
var _proto_ = selectInLibrary.prototype;
_proto_.aAlreadyDone = new Array();
_proto_.DOM = fl.getDocumentDOM();
_proto_.oXMLUI;
_proto_.Init = function(){
          fl.trace("==== selectInLibrary v2.0 (for CS4) ====")
     var _aSelection;
     if (this.DOM == undefined){
          alert ("You need to open a Flash File First!");
     }else{
          this.CheckSelection();
_proto_.CheckSelection = function(){
     //     Make sure at least 1 stage element is selected
     if(this.DOM.selection.length <= 0){
          alert ("You need to Select a elements on the Stage");
     }else{
          //     Clear library selection
          this.DOM.library.selectNone();
          //     Loops through selected stage items...
          for(var i = 0; i < this.DOM.selection.length; i++){
               //     ...if selected elementType is "instance"...
               if(this.DOM.selection[i].elementType == "instance"){
                    fl.trace("Element " + this.DOM.selection[i].libraryItem.name + " already processed? " + this.ElementExist(this.DOM.selection[i].libraryItem.name));
                    //     ...if selected element has not been processed...
                    if(this.ElementExist(this.DOM.selection[i].libraryItem.name) == false){
                         fl.trace("Processing: " + this.DOM.selection[i].libraryItem.name);
                         //     ...adds selected element to array aAlreadyDone.
                         this.aAlreadyDone.push(this.DOM.selection[i].libraryItem);
                         //     ...select the item in the library.
                         this.DOM.library.selectItem(this.DOM.selection[i].libraryItem.name, false, true);
                         //     ...deploy item's folder.
                         this.deployFolder(this.DOM.selection[i].libraryItem.name);
                         fl.trace("----");
                    } else {
                    fl.trace("Skipping " + this.DOM.selection[i].libraryItem.name + ": Already processed");
                    fl.trace("----");
*     This Remove the name of a movie clip from the path
_proto_.catPath = function(_sText){
     var _nLastPosition;
     fl.trace("catPath: " + _sText);
     for(var i = 0; i < _sText.length; i++){
          if(_sText[i] == '/'){
               _nLastPosition = i;
     fl.trace("catPath return: " + _sText.substring(0, _nLastPosition));
     return _sText.substring(0, _nLastPosition);
*     This will deploy the folder contaning the Folder
_proto_.deployFolder = function(_sText){
     fl.trace("deplyFolder: " + _sText);
     if(this.PathExist(_sText) == true){
          _sPath = this.catPath(_sText);
          fl.trace("new _sPath: " + _sPath);
          this.DOM.library.expandFolder(true, false, _sPath);
          this.deployFolder(_sPath);
*     This methode return if this is a path
_proto_.PathExist = function(_sText){
     for(var i = 0; i < _sText.length; i++){
          if(_sText[i] == '/'){
               return true;
     return false;
*     Check if the element already been modified.
_proto_.ElementExist = function(_sElement){
     _ret = false;
     for(i = 0; i < _proto_.aAlreadyDone.length; i++){
          if(_sElement == _proto_.aAlreadyDone[i]){
               _ret = true;
     return _ret;
/****** END CLASS DEFINITION *****/
var oSelectInLibrary = new selectInLibrary();
oSelectInLibrary.Init();

var succes = fl.getDocumentDOM().library.expandFolder(true,false);
// traces "success : true"
fl.trace("success : " + success);
But folder does not expand
flash 11 on a selected folder
tried with third arg as path without success
Seems like another fl.blackmagic trick
I you found something ?
Regards

Workaround for JSFL shape selection bug?

There seems to be a bug in the document selection reporting in JSFL in CS4 (haven't tested earlier versions). I submitted it as a bug to Adobe but I'd really like to find a workaround for it. I've included my bug report below. Has anyone else encountered this? If so, have you figured out a workaround? It's pretty annoying, making the tool I'm working on really difficult to manage.
******BUG******
After performing a publish preview, fl.getDocumentDOM().selection reports an incorrect selection of raw shapes.
Steps to reproduce bug:
1. Create a JSFL command with the following contents:
doc = fl.getDocumentDOM();
fl.trace("there are " + doc.selection.length + " items selected");
2. Start the authoring environment fresh, with a new document.
3. Draw several shapes on the stage, not touching each other, all in the same frame and layer.
4. Select one of those shapes but leave the others unselected.
5. Run the previously created JSFL command. It will send the following text to the output panel, as one would expect:
"there are 1 items selected"
6. Do a publish preview (either Flash or HTML).
7. When it comes up, close the preview window.
8. Deselect all and then select one of the shapes (again, keeping the others unselected).
9. Run the JSFL command again. This time, it will say that there are n items selected (where n is the number of shapes you drew in step 3). So if you drew three shapes, it will print out the following:
there are 3 items selected
Note that this result will be the same even if you go to a different document, do a publish preview on that document, then return to the original. It seems that simply doing a publish preview alters Flash's state to report the selection incorrectly.
Results: The JSFL command reports that all the shapes are selected, despite the fact that only one of them is. The only way I've found to get Flash back to its normal behavior is to restart the authoring environment.
Expected results: In the steps above, the JSFL command should always print out that there is one element selected. There's no reason that doing a publish preview should change that.

When selected all shapes in selection are treated as one. You can see it if you run this script with selected multiple shapes:
fl.trace( fl.getDocumentDOM().selection[0].contours.length );
It will output you twise bigger number then selected shapes (because each Shape has two contours - one clockwise, other counterclockwise).
Of course this. implementation is strange for me too. Thats how i found your post

Broken - Doesn't work. Javascript error.

Nice Idea. Doesn't work though.

I think it only works with Flash CS5.5. Looks like in 5.5 they've implemented new JSFL command : "fl.getDocumentDOM().getSizeReportXML" that doesn't exist in previous versions.. Which is quite sad for us since we we have version 5 and would have to fork out 550 bucks for an .5 upgrade upgrade that should realy be free .

JSFL reg point move does not save correctly

I have come across an issue in flash pro while using commands written in jsfl.
I have a jsfl command that moves registration points on a selected library instance. A snippit of the command that does the moving is:
fl.getDocumentDOM().enterEditMode('inPlace');
var ele = fl.getDocumentDOM().getTimeline().layers[0].frames[0].elements[0];
ele.x = 0;
ele.y = 0;
ele.x = -ele.left;
ele.y = -ele.top;
ele.x += newRegX;
ele.y += newRegY;
fl.getDocumentDOM().exitEditMode();
After running the command everything looks good. The reg point has been moved to where I want it to be.
However, if I save and reload the fla the registration points show back up where they were before the move command.
It seems like the jsfl move values are not being saved correctly. Is this something others have seen before? Is there a fix to this issue?
Thanks.

Yes I have also found the saving bug when messing with the transform point and jsfl.
I was trying to move the registration point to the current transform point.
First version of the code it all worked fine but after saving and opening again only the first frame had moved.
Second version of the code I went through all the frames and selected then deselected all alements on each frame - this seemed to fixed the issue. - manually doing it did.
However I then noticed I was still haveing some issues - this could be fixed by manually entering the symbol and moving the transform point - saving and opening then worked.
I could not however do that step with code (well I could but it didnt fix the issue)
Am Going to look for other thisng that might help - adding a new layer - or something that will force flash to realise that things have changed.
But this is definately a flash bug - when everything looks and works fine but the reverts to something else after a save and reopen - suggests a much larger bug with saving.

JSFL or SWF Panels and the ActionScript Editor

Howdy, I'm hoping to be able to write JSFL commands or make swf panels for the Flash IDE that will work with the ActionScript Editor. Mind you, not the ActionScipt panel that is open with a .fla, but with the Flash text Editor that edits .as files directly. I've been able to get it going with the actions panel, but don't know if it's possible with the .as editor. Any ideas on how to accomplish this?
Essentially I'm hoping to create a panel that generates getters/setters automagically, like FlashBuilder does, but with some additional features, like ASDoc commenting etc. Also, I want to have it generate empty functions for any event listener callbacks as I code the listeners.
Thanks in advance!
-Ted

Never heard of that, and not sure if the hot fix addresses that, but make sure you have it - your Flash version should be 10.0.2 in Help > About
You can get the update from: http://www.adobe.com/support/flash/downloads.html

Flash pro cc xul controlls jsfl need help

Hello all
i had used flash cs for a while and was using lots of downloaded jsfl commands that would help me speed up work
Switched to cc lately and those commands do not work
heres a code of one of not working commands.
dialog buttons="accept, cancel" title="Search and Replace v1.0">
<grid>
<columns>
    <column />
    <column />
</columns>
<rows>
    <row>
    <label control="searchFor" value="Search For:" />
        <textbox id="searchFor" value="" />
    </row>
    <row>
    <label control="replaceWith" value="Replace With:" />
        <textbox id="replaceWith" value="" />
    </row>
    <spacer />
        <radiogroup id="searchType"/>
            <radio label="Search All Items" selected = "true" />
            <radio label="Search Selected Items" />
        </radiogroup>
</grid>
</dialog>
Could you tell me what to modify so i can run this command under CC
Thanks in advance

sorry that was only the xml window code for the command
the real code for the command is this:
var doc = fl.getDocumentDOM();
var lib = doc.library;
var allItems = lib.items;
var selItems = lib.getSelectedItems();
var searchItems;
var nameList
var oldname;
var newname;
var xml = doc.xmlPanel(fl.configURI + "XULControls/SearchReplace.xml");
if(xml.dismiss == 'accept'){
    var searchFor = xml.searchFor;
    var replaceWith = xml.replaceWith;
    if(xml.searchType == "Search Selected Items"){
        searchItems = selItems;
        nameList = removePath(true);
    }else{
        searchItems = allItems;
        nameList = removePath(false);
    if(searchItems.length == 0){
        alert("No Library items selected");
    }else{
        for(i = 0; i < searchItems.length; i++){
            oldname = nameList[i];
            newname = oldname.replace(searchFor, replaceWith);
            searchItems[i].name = newname;
function removePath(bSelItems){
    if(bSelItems){
        libSelPath=fl.getDocumentDOM().library.getSelectedItems();
    }else{
        libSelPath=fl.getDocumentDOM().library.items;
    itemNames = new Array();
    for (a = 0; a < libSelPath.length; a++){
        charStart = libSelPath[a].name.lastIndexOf("/") + 1;
        itemNames[a] = libSelPath[a].name.substring(charStart);
    return itemNames;
thx

Features I would very much like to see in Flash CS5

Just a preface: I'm coming at this from the perspective of a professional Flash character animator. I've worked on two TV shows and one big-budget online virtual world/game and I've been using Flash professionally since MX 2004. I've also written a lot of JSFL commands and done a little actionscript programming (I used to be a software engineer, so the programming comes pretty maturally to me).
So with that said, here are some of the things that I'd really like to see in the next version of Flash, approximately in order from more to les important:
3. Stability and user friendliness. Please, guys, spend a little more time on polish and leave off the one or two extra cool features that you were thinking about throwing in.
13. Color management. I can't emphasize this one enough. COLOR MANAGEMENT! Take a look at Toon Boom Studio for what I'm talking about. Particularly in large projects, the ability to have a real color palette, rather than just having each shape have an RGBA value, would be incredibly useful. That way if I decide I don't like the color of a character's shirt I could just change the shirt color palette entry and it would automatically update every shape in the file that used that palette entry. An extra bonus, though less important, would be to be able to control it from Actionscript -- to be able to change a palette entry dynamically at run-time.
5. non-affine transforms for symbols. Particularly, we want trapezoidal/perspective skew! I've heard SO many people talk about wanting this. I was hoping that the 3D stuff in CS4 would allow it, but no such luck. While it's theoretically possible the controls just aren't set up to allow it.
1. Make EVERYTHING in the Flash authoring environment scriptable. Currently there are a number of things that can be neither scripted nor given a keyboard shortcut, (for instance the onionskinning controls).
2. Make Flash remember its maximized status from the previous session (this is a problem in many Adobe products).
4. Real hardware 3d acceleration.
6. Refine the JSFL API to be more thorough and consistent (see also #1). Make it so that everything you can do in JSFL happens in a way that makes sense. For instance, a couple problems I had recently: delete a shape from the stage and then draw a new one with Path.makeShape() and the new shape is created as if the old one were still there (with extra vertices at edge intersections); and Path.makeShape() won't create cubic paths -- it automatically converts cubic contours to quadrilateral ones.
7. Speaking of types of paths: Make the distinction between quadrilateral and cubic paths clearer to the user. Most people I talk to don't have any idea what the difference is, or that cubic paths are likely to produce more vertices than they expect in the final SWF. In fact, I think you should consider ditching the distinction entirely, at least from the user's perspective. Make every path in the authoring environment cubic, and just convert them to quadrilateral (if you must) on export. This'll relieve a lot of annoyance from users unexpectedly finding that their shape they just created very frugally suddenly has three times as many vertices.
8. Make bones work better on raw shapes. In fact, make them work more like Maya: each bone should affect each vertex to a degree decidable by the user. Currently bones affect each vertex either 0% or 100%, which means that, for instance, it's nearly impossible to get a smoothly curving snake.
9. Add at least one new fill style: we have radial blending, but the major one we're missing is the OTHER kind of radial -- with rays shooting our from a center. Perhaps less realistically, I can't tell you how much it would rock to be able to use a path-based color blend -- where the blend actually follows an arbitrary path (like what you can do in Synfig -- www.synfig.org).
10. Add precision to the stage. Currently it's very hard to position things when zoomed in close, and display artifacts are show up on curves, where they get flattened out for no apparent reason. I think the display artifacts are new to CS4, so perhaps it's just a bug that needs to be worked out in the new display engine? But the current situation is a real pain -- where any symbol that's created relatively small will unavoidably contain rendering and positioning issues.
11. A feature that's been missing (and sorely missed by TV animators) since Flash 8 is the ability to smoothly copy and paste from Flash to Illustrator. There's absolutely no reason this shouldn't be an easy task, and I'm still confused as to why it disappeared from MX 2004 to Flash 8. It's extremely useful for applying art brushes to paths or animating 3D door swings in Illustrator and then bringing the art back into Flash.
12. For that matter, what about art brushes in Flash? I realize they would be heavy in the SWF -- either in rendering time or in space used -- but you've already got stipled brushtrokes, and aren't those just as heavy? Art brushes would be INCREDIBLY useful to animators and designers.
14. Engage with the people who use Flash. Get some dialogue going on between users and developers. Most Flash users I meet (admittedly mostly character animators and character rig builders/designers) have very specific wishes for Flash, and for the most part they coincide very nicely. Yet release after release we don't see any of the changes, features, or bugfixes, that seem the most obvious.

Hi there,
I can assure you that the wishlist is monitored by our team. It does not go into a black hole or shredder - the messages are read by the Flash team, and forwarded as needed, and non-duplicate/legitimate bugs are filed.
Some of the things on your list are known. I'll go through the items, and encourage you to send some messages along these lines (I'd recommend one submission per item, but this is up to you).
* Stability and performance: This is definitely still being worked on. You'll see a lot of that work in the Flash 10.0.2 update, and I can assure you it's still a priority.
* Color management improvements: We do have bugs in this area filed, I believe very similar or the same as you have below, but please feel free to your ideas in this area if you'd like to ensure they're covered.
* Transforms for symbols (3D), and hardware acceleration: Should submit this to the Flash Player wishform (which is external, enabling votes) - if they support it, that support can be transferred to the authoring tool. http://bugs.adobe.com/flashplayer/
* Keyboard shortcuts and JSAPI: Please submit any specific requests (exact areas that are missing). For the keyboard shortcuts for UI where they cannot yet be assigned, this would be a separate request (I'm not sure about the feasibility of buttons as opposed to menu items).
* Cubic vs quadratic paths: This is known and is a difference between the authoring tools/UI and Flash Player, and it's the reason for "10" (more precision to the stage). It's not really about artifacts or precision, but about how Flash Player renders curves in general. If you draw in an AS2 document, you won't see the change from curves to flat edges. If you export that document to the Player in AS2, you'll see the "artifacts" you see on the stage in AS3 documents. This is a known issue of the authoring UI and drawing tools, and making this better is really really high priority in my books too.
* Bones: Many issues are known and presently being worked on.
* Fill style: Please feel free to file this enhancement request, I'm not sure if it has been requested.
* Cross-product copy/paste (Illustrator): This is known, but if you have some specific issues or workflows you've encountered and want to make sure its rectified, please send that along.
* Brushes: Definitely requested/known. I'd love to see that too, in particular.
* Engaging with users: Definitely covered too! That's why we have betas (which do include prominent animators), why I hang out here, and so on. We do have designers (I went to art school) and animators on the team too. I know how it feels though - many of the features I'd most like to see can't be added yet, as Flash covers such a broad user base from coders to animators (many releases have left the coders feeling the same way). All I can say is please submit your feedback to the wishlist, and continue to voice up about what you'd most like to see in Flash with the specifics.
Great feedback!
Thanks.

Tiff's suddenly showing generic icon instead of image preview

All of a sudden I have begun having an intermittent problem with Bridge (CS3) not displaying a preview thumbnail for a very few number (not all) TIFF files- instead I just get a thumbnail showing a TIFF logo rather than the picture itself. I would normally think it was just something about those particular files but it's happened with some files from two other sources all within a few days of one another- on several occasions it has happened to a TIFF that previously had a preview and then once I did additional work and had to save over it, it lost the preview and had the generic icon.
Is anyone familiar with this issue and how to fix it? I already tried purging the cache for the folder, then I tried restarting Bridge while holding down the option key and reset the Cache database. I did not reset the Preferences yet, I have a lot of things set up just so and would like to avoid it if it isn't necessary. The only change I have made is I installed the newest version of Camera Raw, though I am not implying it had anything to do with this.

Purge the cache for the offending folder(s) through the Tools menu in Bridge, NOT through the broken global command in Bridge prefs.

Extending flash: how do I set default values for filenames

Hi,
I am trying to set default values for filenames
<choosefile> and <popupslider>s that will show up when
my XMLpanel first loads in my jsfl extension file. It seems that I
can only set default values for textbox items.
How do I do this for filenames and popups?
As a workaround, I also tried using a flash object dialog box
to look like a <choosefile>, or any jsfl command, but then
how do I return those values back to the XMLpanel that calls them.
and pass the data back to my jsfl script.
lemme know if you know a way,

Create two constants for the Allocate Mode input (right click > create > constant). Place one in the true case of the case structure, and place the other one in the false case. Wire them to the same tunnel (border of the case structure), then wire the tunnel to the Allocate Mode terminal of the AO Config. I don't have Traditional DAQ installed, but that should do it.
Misha

Display bug in the Flash update (10.0.2)

So I installed the Flash CS4 update that was released in May and for the most part I'm happy with the changes. There's at least one huge bug, though: the display doesn't update correctly when the start frame is changed on a graphic symbol via any means other than by typing it into the "first" box in the properties panel. This may not seem like a problem -- how else would you change it, after all? Well, by hitting "undo", for instance, after you changed it via the "first" box. Or via JSFL. That's the biggest problem for me: I have a bunch of JSFL commands I wrote that are pretty much integral to my animation process that changed the start frame of a graphic symbol, but the display no longer updates correctly when I use those.
So my question is: has anyone else run into this problem? I've encountered it on multiple installations so I'm pretty sure it's integral to the update. Has anyone figured out a way to fix it, or at least a workaround? Perhaps a way in JSFL to force a display update?
-David

Hi David,
Thank you very much for letting us know about this one. I hate to hear about this, and have reproduced both problems and filed them internally.
As for the JSFL, a workaround could be to manually select the Stage in JSFL:
document.setSelectionRect({left:0, top:0, right:0, bottom:0});
You could select an area of the Stage that contains the instance instead if you want it to remain selected.
Hope that helps, and thanks again for reporting,
Jen.

Broken JSFL Commands

Similar Messages

Maybe you are looking for