Javascript Different in CS3 vs. CSX?

Hi, is JavaScript different for acrobat verison CS3 Version 8 vs. X PRO - version 10?  I use online forms that users submit for clearance access.  I have been using Acrobat verison CS3, version 8, however, I recently updated to Acrobat X Pro and the script that I have doesn't work now.  The form itself still is fine, just the script for the textbox doesn't work.  The textbox indicates authorized signer status.  The form is locked after signing, except for this textbox which should be able to change...
I'm stumped..
Here is the script:
var digSig = event.target.getField("topmostSubform[0].Page1[0].AUTHORIZED_APPROVERS_SIGNATURE[0]");
var sigInfo = digSig.signatureInfo();
if (digSig) {
var status = digSig.signatureValidate();
var message = "";
switch (status) {
case 0:
case 1:
message = "NOT SIGNED";
break;
case 2:
message = "INVALID SIGNATURE";
break;
case 3:
message = "VALID BUT IDENTITY OF SIGNER CANNOT BE VERIFIED";
break;
case 4:
message = "VALID SIGNATURE";
break;
default:
message = "ERROR";
break;
this.rawValue = "SIGNATURE STATUS: " + message;
And here is the error message I receive when loading the form within acrobat.
Thank you kindly.

Hi,
to fix this problem you can do the following:
Delete the script in the exit event of the field "SPECIAL_NOTES" and add this script to it's change event.
$event.change = Upper($event.change)
Hope this helps.

Similar Messages

  • Do paragraph style overrides work differently in CS3 vs CS4?

    Hi All-
    I’m in the process of moving a workflow from CS3 to CS4, and have run into an unexpected problem. In the existing CS3 workflow, we receive copyedited text with Word paragraph styles applied, then import this text into our InDesign template. This template has all the same paragraph style names as the Word file, so we tell InDesign to use the InDesign style definitions in the Import options. So, for instance, the Word style for Para_Text is Times New Roman 12pt, and the InDesign style for Para_Text is Helvetica Neue 8pt, and on Import InDesign automatically changes it to Helvetica Neue 8pt. This is as we want it.
    Things fall apart, however, when we import the same text into the same template in InDesign CS4. It still applies the InDesign style definition, but has additional overrides to make it look like the Word style definition. So, it recognizes that the underlying paragraph style should be Helvetica Neue 8pt, but it then preserves Times New Roman 12pt as an override. If I select the text and do Clear Overrides, it’ll revert to the Helvetica Neue 8pt we want it in, but for other reasons that solution is less than ideal.
    I think I can come up with a rather kludgy way around this, but I’m trying to understand exactly why we’re getting the different behavior in CS4. It seems like paragraph style conflicts are being handled in a different way in CS3 than CS4 – in CS3, if the InDesign paragraph style specifically spelled out a font, that would dominate on import; now, in CS4, it’s allowing the Word paragraph style to seep through as an override. Any thoughts as to why this is happening?
    Thanks,
    -Nate

    Hi Chris.
    Good news. I cant tell you how happy i am for all your help ;-) and you other guys.
    The latest Eizo 5.2.1 software fixed the problem on all 3 Eizo monitors.. Weeee
    I'm back to normal.
    Now i just have another damn problem started not long ago ;(
    My Photoshop CS3 and CS4 keeps crashing on me after a wile of work ???
    I tried everything. Deleted preffs etc. etc.
    It have been working for long long time but suddenly it keeps crashing all the time.
    I tried to remove some new plug-ins, but it was not that.
    Only thing i did also was to install new ram.
    Upgraded from 10GB to 14GB in all our Mac Pro.
    So after i tried to switch the ram around to check if some was bad.
    Also run some memory software but everything came out right.
    So now the only thing left is that Photoshop dosent like ram between 14GB & 16GB.
    Under was fine and i never tried over 16 gigs.. weird
    Any ide what could corse this ?

  • Why are my PMS colors different in CS3 & CS6?

    I originally created a label in CS3, and just had to make a new one a different size. When I did the new art in CS6, the PMS colors are way different! I basically copied and pasted the old art into the new file. I have replaced all PMS colors, but they still do not match the old version. What's up?? Can anyone shed some light on this? The original version (in CS3) is on the left and the new art in CS6 is on the right. Thanks!

    Thanks Monika, but, OMG, I feel a headache coming on! =(  So, is it better to stay with the new Pantone Plus colors, or convert to the older version? How will this effect reprinting of jobs, if the client makes changes and I resave the file in CS6? Will the color be different now, if saved in the Pantone Plus? Maybe I need to do more reading up on this!

  • CC Cylinder aligns differently in CS3

    Just opened a project that I originally created in AE7 that is using CC cylinder to create a simple odometer-like effect. In CS3 the discs are being created at a different aspect (almost as though its interpreting as sq pixel). Is there something that changed in CC's implementation in CS3?
    As a side note along the same lines, I have always used 2D nulls to break the intersection between 3D layers when necessary. As of CS3 that no longer works. What has changed with this? Adjustment layers still work for the same purpose (I just have hundreds of nulls scattered about lots of projects that will have to be swapped if this is something that is not considered a 'bug')

    >For a list of the layer types that break 3D intersections and shadow casting, see the "How render order and collapsed transformations affect 3D layers" section of After Effects CS3 Help on the Web.
    Does that page even say anything about this change to the 2D/3D layer interaction rules? I can't see any mention of nulls, only 2D and 3D layers (both of which categories encompass nulls). Am I missing something?
    >It was a bug. People were clamoring.
    I stand corrected. It certainly was a useful bug, and it being fixed breaks old projects that depended on this predictable behavior.
    >If you're linking other layers' properties to those of a null layer that you're using as a control layer, it's a lot easier if the null has the same layer properties as the other layers.
    I can see that for, say, opacity, but are people really linking to the colors of null layers? That's not a simple pick-whip operation, and anyone conversant enough in expressions to know how to do this is going to also know about Expression Controls, which are much more convenient. Are you saying these things aren't just an artifact of nulls' heritage as solids? You are obviously in a much better position to know these things, but I find this a bit surprising.

  • [JS] Items on page vs pasteboard move differently in CS3 vs CS4/CS5

    I'm trying to move all the items on all the pages in a document (including the master pages), regardless of what layer they are on and I want to retain their locked/unlocked states. In trying to figure this out I came across Adobe's AdjustLayout Sample script. This was quite helpful and I adapted it to move all the items a specified amount (the modified script is shown below). There may be a better way, but this was pretty much working.
    Except one problem:
    - In CS4 and later all items move, those on or off the page (in the pasteboard).
    - In CS3 though, only the items on a page move, and NOT the ones on the pasteboard (which I do also want to move).
    I have searched this forum and read a lot, but still haven't figured out how to get CS3 to also move the pasteboard items. Can anyone help? Below is the script I adapted, but I am open to other ways if there's something better. I used this because it seemed close to what I was looking for.
    Thanks, in advance.
    Dan
    //Moves the content by specified amounts
    //based on sample script by Adobe, but this moves objects by same amount regardless of even or odd pages
    myDisplayDialog();
    function myDisplayDialog(){
              var myLabelWidth = 70;
              var myDialog = app.dialogs.add({name:"Adjust Layout"});
              with(myDialog.dialogColumns.add()){
                        with(borderPanels.add()){
                                  with(dialogRows.add()){
                                            with(dialogColumns.add()){
                                                      staticTexts.add({staticLabel:"Offset Amount:", minWidth:myLabelWidth});
                                                      staticTexts.add({staticLabel:"Horizontal:", minWidth:myLabelWidth});
                                                      staticTexts.add({staticLabel:"Vertical:", minWidth:myLabelWidth});
                                            with(dialogColumns.add()){
                                                      staticTexts.add({staticLabel:""});
                                                      var myXField = measurementEditboxes.add({editValue:-12, editUnits:MeasurementUnits.points});
                                                      var myYField = measurementEditboxes.add({editValue:0, editUnits:MeasurementUnits.points});
              var myResult = myDialog.show();
              if(myResult == true){
                        var myX = myXField.editValue;
                        var myY = myYField.editValue;
                        myDialog.destroy();
                        myAdjustPages(myX, myY);
              else{
                        myDialog.destroy();
    function myAdjustPages(myX, myY){
              var myPage;
        //Set the transform content property to true so that content will move with frames.
        //myOldTransformContent = app.transformPreferences.transformContent;
        //app.transformPreferences.transformContent = true;
        var usersXUnits = app.activeDocument.viewPreferences.horizontalMeasurementUnits;
        var usersYUnits = app.activeDocument.viewPreferences.verticalMeasurementUnits;
        //Set the measurement units to points.
        app.activeDocument.viewPreferences.horizontalMeasurementUnits = MeasurementUnits.points;
        app.activeDocument.viewPreferences.verticalMeasurementUnits = MeasurementUnits.points;
        //Save the old page numbering
        var myOldPageNumbering = app.generalPreferences.pageNumbering;
        app.generalPreferences.pageNumbering = PageNumberingOptions.section;
        //Set page numbering to absolute
        app.generalPreferences.pageNumbering = PageNumberingOptions.absolute;
        for(var myCounter = 0; myCounter < app.activeDocument.pages.length; myCounter++){
            myPage = app.activeDocument.pages.item(myCounter);
            var myPageValue = myPage.documentOffset;
            myAdjustPage(myPage, myX, myY);
        for(var myMasterPageCounter = 0; myMasterPageCounter < app.activeDocument.masterSpreads.length; myMasterPageCounter++){
            myMasterPage = app.activeDocument.masterSpreads[myMasterPageCounter].pages[0];
            var myPageValue = myMasterPage.documentOffset;
            myAdjustPage(myMasterPage, myX, myY);
        }    //Reset the transform content and measurement units to their original values.
        app.activeDocument.viewPreferences.horizontalMeasurementUnits = usersXUnits;
        app.activeDocument.viewPreferences.verticalMeasurementUnits = usersYUnits;
        //app.transformPreferences.transformContent = myOldTransformContent;
        app.generalPreferences.pageNumbering = myOldPageNumbering;
    function myAdjustPage(myPage, myX, myY){
              var myPageItem;
              for(var myCounter = 0; myCounter < myPage.pageItems.length; myCounter ++){
                        var myResetItemLock = false;
                        var myResetLayerLock = false;
                        myPageItem = myPage.pageItems.item(myCounter);
                        if(myPageItem.locked == true){
                                  myPageItem.locked = false;
                                  myResetItemLock = true;
                        if(myPageItem.itemLayer.locked == true){
                                  myPageItem.itemLayer.locked = false;
                                  myResetLayerLock = true;
                        myPageItem.move(undefined, [myX, myY]);
                        if(myResetItemLock == true){
                                  myPageItem.locked = true;
                        if(myResetLayerLock == true){
                                  myPageItem.itemLayer.locked = true;

    No.
    You'll need to loop through all pageItems and move them individually (checking if they're locked as you go...)
    Harbs

  • Resizing objects and groups in CS4 - different from CS3

    Hi all,
    In CS3 I used to be able to resize objects or groups of objects by just using the solid select tool and just grabbing a corner or side of the object and resizing it.  That doesn't work in CS4.  Doing the same thing only moves the image around.  I have to actually use the scale pop-up.
    I can still do the same thing an anchor or path at a time with the outline select tool.
    I'm sure there's a way to do this in CS4 and there's probably a switch buried deep in some menu to allow this, but darned if I can figure it out.

    I'm still on CS3 so I don't know for sure, but I don't think so.  It's always been a pretty easy key shortcut to hit by accident though. 

  • Fonts different between CS3 and CS5 on Win7 system using the same fonts directory

    I have several files created in Fireworks CS3 that work fine. Fonts are all  installed in the system directory on my Win7 box.  This used to be a WinXP Pro  box.
    I can load a file into Fireworks CS3 without a single issue and the text all  looks perfect. The way it should.  Close CS3, open CS5 and load the same file  and CS5 tells me I have to update my fonts.  Why?  Same system, same fonts in  the same fonts directory. Only thing that's changed is that I'm opening the  file(s) in CS5.
    The fonts do not look the same in CS5.  Am I going to have to redo every  Fireworks CS3 file so that it looks correct in CS5? If so, why?
    -- Bob
    Here's a sample image the way it's supposed to look. The Swift gets hosed. PlazaDUtil is the font. I'd hate to have to redo all my logo files.

    Prior to CS4 Fireworks used the Macromedia type engine. From CS4 forward, adobe introduced the adobe type engine to improve text handling/integration between FW AI and PS. As a result moving CS3 files over to cs4 forces FW to update the fonts.

  • Why are previews different in CS3 and CS6

    I can't see a separation between process colors and the black on pdfs in CS6. The black plate appears to be printing on all 4 plates. In CS3, the black doesn't appear on all plates. We're using OS 10.8.
    CS3 is the first image; CS6 is the second image

    The 2 samples I originally attached show the difference between Output Preview in Acrobat 8 and Acrobat 11. Acrobat 8 shows how the image prints - nothing but black on the horse image. Acrobat 11 is not how our image prints. Here is the sample in a smaller size. Of course, we're working with pdfs, not jpgs.

  • CS5 Indents Different From CS3? Help Please

    I'm completely stumped.
    I recently switched over from dreamweaver cs3 to cs5 because it had been running slow. As soon as I made the switch I noticed that in design view EVERYTHING is indented weird. I know this doesn't explain much, but please see the images below. As soon as I publish and check the page live, the indents vanish. I have been searching for a way (maybe in preferences) to remove the weird indents from the design view in cs5 for the sole fact that it irritates me. If it helps, each item is seperated by <dd>. Anyone know what is going on here?
    CS3 View
    http://i42.tinypic.com/xq9a14.png
    CS5 Views
    http://i41.tinypic.com/i1ljyg.png
    http://i41.tinypic.com/1494aqf.png
    Thanks so much!
    Brian

    Unfortunately screenshots don't tell us much other than there's apparently a problem.
    Hard to comment without seeing the code.

  • Margins, div tags displaying differently on different monitors CS3 DW

    I am working on a class website on three, maybe four computers all running DS3.  My work computer is a 17" 4:3 ratio monitor running at, maybe 1280 - 1024.  The page in DESIGN view displays fine, and looks fine in IE and Firefox.  My class computer is a 19" 4:3 ratio monitor running the same resolution, and it looks fine.
    My home computer is a 24" monitor running 1900 x 1200  16:9  widescreen ratio resolution. And what looks good at school and work goes to pot at home. All the div tags shift around, margins, screw up in Design view but look okay in IE or Firefox when I preview them.  What is up?  Is there a setting I've missed. If it helps, know that I am NOT using AP divs or AP  -- I want the pages to float center.   Thanks in advance.
    W!

    Thanks for your concern regarding the class instructor!
    The instructor was very clear about what the course would not cover --- DIVs, behaviors, Sprys, templates, etc.  It covers DW commands, tables, formatting, linking, posting sites to the web, and beginning flash.  In fact, the final project is only supposed to be 1 landing page and two supporting pages. And to be fair, it's one of those classes where you've got people like myself with previous exposure to HTML combined with folks who don't know how to use Windows Explorer to navigate to a directory. .  .
    Before taking the class, I had purchased one of those TOTAL TRAINING DVD instruction sets -- DW instructor Janine Warner did the two disc instruction set and did a really good job explaining the difference between regular divs and AP divs.  Which is why I'm not using AP divs right now.  I wasn't able to control spacing or formatting the way I wanted using tables, so I decided to use DIVs instead.   Building a Nav Bar using "Insert -- Nav Bar" didn't provide submenus and the graphics I created for rollovers took to long to load (even though I took pains to create small graphic buttons in Photoshop as 3 KB gifs), I was pointed in the director of Spry widgets, etc.  My class instructor is good enough to say, "We're not doing that in this class. But why don't you research. . ."
    I think it's all good.  I appreciate having this forum as a resource.

  • Can you tile windows from Javascript in CS3?

    I have a javascript that will open 2 images in Photoshop from different directories based on a single filename, so that the users can view them side by side. They need this to be able to compare the colour correction from an automated process against the original image.
    The trouble is that even though I can open the images, I cannot invoke the "window/arrange/tile vertically" menu item, as I can with InDesign.
    Does anyone know of a neat trick to get around the missing tile vertically command within Javascript for Photoshop CS3.
    (I've trawled the web and found that most answers are for 4 or more windows, where the images are pasted into one doc. But here I need to keep the windows separate.)

    One way to do this in CS3 is with an action. Make a new action then stop recording. There should be no steps in the action. From the action panel's flyout menu choose insert menu item. Then choose the "window/arrange/tile vertically" menu item. You now have an action that you can call from a scipt to tile the two images.
    Another way is to use Xbytor's doMenuItem function
    // adatped from Xbytor's xtools stdlib.jx
    doMenuItem = function(item, interactive) {
       var ref = new ActionReference();
       ref.putEnumerated(charIDToTypeID("Mn  "), charIDToTypeID("MnIt"), item);
       var desc = new ActionDescriptor();
       desc.putReference(charIDToTypeID("null"), ref);
       try {
         var mode = (interactive != true ? DialogModes.NO : DialogModes.ALL);
         executeAction(stringIDToTypeID("select"), desc, mode);
       } catch (e) {
         if (!e.message.match("User cancelled")) {
           throw e;
         } else {
           return false;
       return true;
    doMenuItem(stringIDToTypeID('tileVertically'));
    Note newer version of Photoshop have a app method named runMenuItem that can be used instead of a custom function.

  • Pics view differently in CS4 v CS3

    Has anyone noticed that images in CS4 view differently to CS3.  Using calibrated monitors with exactly the same icc profiles, pics in PS CS4 seem to be a lot flatter, lacking colour depth. (open the same image in both apps side by side and compare)
    It has been suggested that CS4 talks directly to the graphics card, bypassing color sync, to improve speed.
    Is this causing issues in colour critical operations and if so how is it fixed.

    I have disabled OpenGL but there is still a difference between the two.
    Did you restart Photoshop after disabling Open GL? With Open GL off altogether Photoshop CS4 will display colors the same as CS3. Any differences must be to do with monitor profiles, as far as I'm aware CS3 and 4 also behave the same in these respects.

  • [CS3 JS] How to force XMP metadata update for a thumbnail?

    Hi Folks,
    In a JavaScript in Bridge CS3, I'm updating a value in the XMP metadata for a Thumbnail. Later in the script I want to read the updated XMP metadata information from the Thumbnail, but often Bridge hasn't updated the metadata by the time I read it. In other words, my script reads the value prior to the update. I'm guessing there's a caching issue going on.
    I'm new to Bridge scripting, and I am hoping someone here can offer suggestions on how I can (or, even *if* I can) force Bridge to update the XMP metadata cache for a file so that when I read it later in the script it will reflect the recent changes. I've tried using Thumbnail.refresh(), but that doesn't seem to do the trick. I don't mind a slower script, I just want to be able to read the correct value.
    Thanks in advance for any help!
    -- Jim

    Hi David,
    I'm running this script on a MacBook Pro, 2.5GHz, 4GB RAM.
    Here is a sample JSX that shows the issue I'm having:
    #target "bridge-2.0"
    main();
    function main() {
        if( xmpLib == undefined ) {
            var pathToLib = Folder.startup.fsName + "/AdobeXMPScript.framework";
            var libfile = new File( pathToLib );
            var xmpLib = new ExternalObject("lib:" + pathToLib );
        var myValue = "Headline Test";
        var myFilePath = "~/Desktop/TestFile.tif";
        var curHeadlineStr = XMPGetHeadline(myFilePath);
        $.writeln("Headline value: \"" +  curHeadlineStr + "\"");
        XMPWriteHeadline(myFilePath, myValue);
        // *** I would like to refresh the cache here ***
        curHeadlineStr = XMPGetHeadline(myFilePath);
        $.writeln("Headline value: \"" +  curHeadlineStr + "\"");
    function XMPGetHeadline(theFilePath) {
        var thumb = new Thumbnail(File (theFilePath) );
        md = thumb.synchronousMetadata;   
        xmp = new XMPMeta(md.serialize());
        var myHeadlineXMPProp = xmp.getProperty
            (XMPConst.NS_PHOTOSHOP, "Headline", XMPConst.STRING);
        return myHeadlineXMPProp;
    function XMPWriteHeadline(theFilePath, theTextStr){
        var thumb = new Thumbnail(File (theFilePath) );
        md = thumb.synchronousMetadata;   
        xmp = new XMPMeta(md.serialize());
        var myOrigHeadlineXMPProp = xmp.getProperty
            (XMPConst.NS_PHOTOSHOP, "Headline", XMPConst.STRING);
        xmp.deleteProperty(XMPConst.NS_PHOTOSHOP, "Headline");
        xmp.setProperty(XMPConst.NS_PHOTOSHOP, "Headline", theTextStr, 0, XMPConst.STRING);
        var updatedPacket = xmp.serialize
            (XMPConst.SERIALIZE_OMIT_PACKET_WRAPPER | XMPConst.SERIALIZE_USE_COMPACT_FORMAT);
        thumb.metadata = new Metadata(updatedPacket);
    To run this script, in main(), set the myFilePath variable to the path of a file that has an "IPTC Code" "Headline" property.
    This script, when run, sets the "Headline" property value to the value of myValue. After runing the script for the first time, take a look at the console log. You should see that Headline value displayed does not change between the two console entries. My log looks like this after the first run:
      Headline value: "undefined"
      Headline value: "undefined"
    The thing is, the second entry in the console listing, above, was created after the Headline value was set by XMPWriteHeadline(). The two values should be different between the two console entries.
    If you run the script a second time against the same file, you will see that the Headline value does contain the value that was written in the first run of the script--it just took some time to update the cache, I'm guessing. Here's the second run's log:
      Headline value: "Headline Test"
       Headline value: "Headline Test"
    So, what I'm looking for is a way to insert code (where the comment line "//*** I would like to refresh the cache here ***" appears), to force Bridge CS3 to refresh its cache so that when I call XMPGetHeadline() after calling XMPWriteHeadline(), the Headline value will return the value that was just written.
    I hope this is clear enough...
    Thanks!!!!
    -- Jim

  • CS3 upgrade to CS6.

    I've been using CS3 for years and would like to upgrade to CS6. Can't find it on this very difficult to navigate site anywhere.
    If the only option is the monthly cloud, I will not be using Adobe software anymore.
    I have no idea where this topic is going to land, what a difficult forum.

    Bobby Minnich wrote:
    Is there a comparison somewhere between CS3 and CS6?
    How much is the cloud stuff different than CS3? Entire new learning curve?
    I think the most important differences between CS3 and CS6 are the introduction of Live View and significant improvements to support for PHP (but only for hand-coding, not for using server behaviors). Live View renders the page as you would see it in a standards-compliant browser, using an embedded WebKit rendering engine. However, CS6 was released three years ago, so that version of WebKit is now out of date.
    If you look at the What's New in CS6 PDF that Nancy linked to, Fluid Grid Layouts, Multiscreen Preview, and PhoneGap integration would not justify upgrading from your current version. Fluid Grid Layouts were a good idea, but poorly implemented. Some improvements were made after CS6, but I couldn't honestly recommend their use. As for Multiscreen Preview and PhoneGap integration, they have both been removed from Dreamweaver CC. Multiscreen Preview is OK, but not a must-have. The PhoneGap integration was very flaky. It worked for a while, but changes to PhoneGap rendered it useless.
    Dreamweaver CC looks very familiar. It is, after all, still an HTML/CSS editor with strong support for JavaScript and PHP. However, the workflow has changed considerably. Live View is kept up to date, and you can now edit directly in Live View. The other big change is the introduction of the CSS Designer panel with support for media queries. Some people love the CSS Designer, others don't. I imagine that switching from CS3 to CC 2014.1 would be a jolt to the system, but as long as you have solid HTML/CSS skills, you should get used to it fairly quickly.
    The main point about the subscription system is that it gives you updates to the program roughly three times a year. You're not forced to update until you're ready, and you can always switch back to a previous version if it suits your workflow better. Most people are used to paying monthly for mobile phone, and the cost of the CC subscription is similar or less. The downside is that if you stop paying, the program stops working, so it is a long-term commitment that needs to be carefully considered.
    I taught a postgraduate web media course at university last year using both Dreamweaver CC and Brackets. Most students preferred Dreamweaver, but two or three of them opted for Brackets, and loved it. Brackets is a free HTML/CSS/JavaScript editor created by Adobe. If you're happy hand-coding, it might be worth considering as an alternative.

  • [CS3][JS] How to get the file type of current document

    Hi,
    How to get the file type of current opening document (e.g., tif, jpeg, png) using JavaScript with Photoshop CS3.
    I am using file object the open the files one by one in the folder (the files sometimes don't have the extensions).
    If the current document is in tiff format then I need to convert to 8-bit, if its an Jpg image then needs to ignore the file.
    Regards,
    Karthik

    Do you really need to know the file type? What about just checking the bit depth?
    var doc = activeDocument;
    if (doc.bitsPerChannel != BitsPerChannelType.EIGHT) {//Not 8 bit
    doc.bitsPerChannel = BitsPerChannelType.EIGHT;
    //do your save etc
    }else{
        //Ignore

Maybe you are looking for

  • IPod shuffle(2nd gen) is not recognised by Windows XP

    I instaled iTunes software from the website and transfered the songs to the iPod. When i unpluged the iPod and turned it ON, the green light on one side is glowing continuously. I neither responded to any of the button press. When I plugged it in aga

  • Adobe Media Encoder CS4 (Mac) condenses .mov vertically

    Hi, folks QuickTime movie generated by Final Cut Pro 7, converted to same size .flv (720 x 480) results in video that is condensed vertically. No such problem when using Flash 8 Video Encoder. Would prefer to use more recent encoder since a document

  • Movie purchased in iTunes won't play. Audio is fine; video doesn't appear.

    Movie purchased in iTunes won't play. Audio is fine; video doesn't appear.

  • MB90 - Message no. VN108

    I am trying to take Print out for movement type 311 Sloc to Sloc i have completed following steps. In MB02 Selected output type ZWA3 and communication method for document (311) when using MB90 to process the output, the error " No messages for initia

  • How can I tell if my external drive is formated to GUID?

    Just swopping an SSD for my HDD in a mid 2009 macbook pro. I want to boot up from the ssd while it is still external via USB to save the bother of fitting it and finding it doesn't work. I've cloned the hdd to ssd with carbon copy cloner succesfully