Backward compatibility of Captivate 2

If a demo was created in Captivate 2, can it be opened and
edited in Captivate 1?

Hi elissag
Hmmm, I do understand that management may be reluctant to
upgrade all licenses from a cost savings standpoint. Naturally, the
best case scenario would be for all to upgrade. And actually, that
may be the most cost effective solution if you factor in all the
time wasted searching for assorted ways of coaxing two versions to
work together and all.
But I do realize your hands may be tied here.
Here are my own thoughts on it. Hopefully others will fill in
what I'm incorrect about or missed entirely.
In this situation, you would need to maintain two different
sets of content. One in version 1 format and one in version 2
format. Any change to either format will result in having to change
the other to ensure they are both the same. This means that if a
person with access to only version 1 of Captivate makes a change,
they need to interrupt a person that is a version 2 user so they
can make the same changes to the version 2 file. And vice-versa.
Keep in mind that the feature set is different between the
versions. This can affect your consistency. Perhaps you like using
the zoom object in version 2. You are limiting yourself to only
version 1 features if you are trying to maintain any form of
standards.
The output files are different between version 1 and version
2. Again, you can somewhat maintain some consistency by foregoing
any of the new flash based playback controls with version 2 as well
as the new skin file. But this does limit your choices to version 1
options only.
I'm sure there are other things I'm missing as well. These
are simply the ones that popped into my head to start with.
Cheers... Rick

Similar Messages

  • Backward compatibility with Captivate 7.0

    We are in the process of procuring Captivate 7.0. If we develop web based training materials using Captivate 7.0 will be able to make edits in future with Captivate 6.0 ?

    No backward compatibility!  This is crazy.  We've just tried the Save As option expecting there to be an option to save for previous versions and it's not there.  What a short sighted approach to take, and very frustrating.
    I am not on a maintenance contract for the software, but my colleagues are, so to be able to collaborate either they have to hold back on updates or I have to upgrade.
    So this is Adobe’s approach to supporting licensed users in their ability to work collaboratively?   I wish there was a competitor on the market we could use instead of Adobe.

  • Backwards compatibility on Captivate 8.

    I have a Captivate 7 licence through my company. We need to do some onsite recordings for the client using a trial version of Captivate 8 that we need to install on the client's computer.
    I'll then take the files and work on them away from the client site. The plan is to use Captivate 7, but I can't find any confirmation that I can edit files recorded in Captivate 8 using Captivate 7?

    However, there is a workaround...sort of...
    If your screen captures are all separate images on slides, just export all background images from the Library to a folder and then import these images into a Cp7 project of exactly the same dimensions as the original Cp8 project.
    If you are doing video captures then you'd probably be importing the final published video files anyway.

  • PP backwards compatibility format after import/edit in Captivate 5

    I was trying to find an original PowerPoint presentation today that I'd used for a Captivate video (.F4V) but when I got to the directory that I was expecting it in I found 2 copies of it.
    I examined the 2 copies and they appeared the same, except one was in Office 2007 format (the version we run) and the other was in 2003 compatible format (the default we run, for backwards compatibility with students' software). The 2 files were marked as being editied 5 minutes apart.
    It struck me that I'd used the "Edit in PowerPoint" feature to change one of the slides in the presentation via Captivate.
    It's not a problem, more for future reference, but when I edited the presentation did Captivate bypass our default settings and save the presentation in MS Office 2007 native format? Is there and easy way round this or is it just down to me to manage my files?
    Thanks in advance.

    No, Scott, Captivate has never been backwards compatible, and that is also the case for CP6: you can upgrade a CP5.5 file to CP6 but you cannot open a CP6-file with CP5.5.
    Lilybiri

  • Captivate 6 to 5.5 Backwards Compatibility

    Hello,
    I've searched under my subject line (in a few different derivations) and can't seem to find a clear answer.
    What (if any) are the backwards compatibility options from Captivate 6 to 5.5? I know there are a lot of new features in 6, but if I develop a project in 5.5, and my co-worker opens it in 6 to edit it, will I be able to work on it again in 5.5?
    Thank you.
    - Scott

    No, Scott, Captivate has never been backwards compatible, and that is also the case for CP6: you can upgrade a CP5.5 file to CP6 but you cannot open a CP6-file with CP5.5.
    Lilybiri

  • Captivate 7 - Backward Compatibility?

    To test the Backward compatibility, I tried the following:
    1. Opened a Project built in Captivate 6 in Captivate 7, saved the file and again reopened in Captivate 6 - It opened
    2. Changed the Text (Text Caption box) content in Captivate 7 and reopened in Captivate 6 - The changes in Text (Text Caption box) were reflected in Captivate 6
    3. Changed the properties of the Continue button to "Action -> On Success -> Go to Next Slide" - This change did not reflect in Captivate 6. It still had the original properties that was given to it in Captivate 6.
    So my question is, "Is Captivate 7 Backward Compatible"??????????
    Thanks,
    Soumya

    Hi Soumya,
    I am Sorry but Adobe Captivate 7 is not Backward Compatible .
    You will be able to open the projects of Captivate 7 in Captivate 6 because the source file extension (.cptx) is same in both version but they might not behave exactly the same .
    Thanks and Regards
    Himanshu Satija

  • My iPad 1 is now very unstable. Apps crash consistently, Mac Numbers/Pages etc incompatible with IOS 5.1 etc. There seems to be no backwards compatibility to iPad 1. Am I just supposed to throw it away? I have restored the iPOad and it has ample storage .

    My iPad 1 is very unstable. Many Apps simply crash after opening. There is ample storage available.I have restored the iPad twice now and still it is unstable.
    Is this a lack of backwards compatibility because no-one writes apps for IOS 51.1. and the original iPad anymore? not even Apple, as the documents and sheets I create on my Mac are incompatible with my iPad now.
    My naievete tells me that this is simply Apple expecting us to upgrade to later levels of hardware. If so, very disappointing for an Apple fan. Seems your App developer approvals (even your own apps) do no require compatibility with anything but IOS 6 or later.

    There are various things to make your iPad more stable. You can try deleting all apps from the multitasking bar; do a reset ie hold the power and home buttons simultaneously until the Apple logo appears; Settings > General > Reset all Settings.
    If you had the previous version of iPages (version 09) on your Mac before upgrading to Pages 5.2, your Mac should still have that version in Applications, which is still compatible with your version of Pages on your iPad.
    If you don't have that version, you can 'Export to Pages 09' which is still compatible with iOS 5.1.1.

  • An error occcurred on line 105 while executing script 'MOM Backward Compatibility Service State Monitoring Script"

    We've been getting the following error for some time now.
    An error occurred on line 105 while executing script 'MOM Backward Compatibility Service State Monitoring Script'
    Source: Microsoft VBScript runtime error
    Description: The remote server machine does not exist or is unavailable: 'GetObject'
    One or more workflows were affected by this.
    Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring
    Instance name: server.domain.local
    Instance ID: {INSTANCE}
    Management group: GROUP
    Unfortunately the instance in question has since been decommissioned and simply does not exist any more. 
    We're currently on a repeat count of over 350,000 and I would REALLY like to get it stopped. I've had a look at adding an override but that points to the management server rather than the instance itself.
    Does anyone have any suggestions?
    thanks in advance!

    Hi Steven,
    There are for option for us to override a monitor ot rule:
    For all objects of class:             
    Class            
    When you select this option for your override, the override settings apply to all objects in the class at which the rule or monitor is targeted.
    For a group            
    When you select this option for your override, the override settings apply only to members of the group. The rule or monitor without the override settings continues to apply to all objects in the targeted class except for those objects that are also members
    of the group used for the override.
    When you create a group, you save it to an unsealed management pack. However, an element in an unsealed management pack, such as an override, cannot reference an element in a different unsealed management pack, such as a group. If you are going to use a group
    to limit the application of an override, you must either save the group to the same unsealed management pack as the override, or you must seal the management pack that contains the group.
    For a specific object of class:             
    Class            
    When you select this option for your override, the override settings apply only to the specified object. The rule or monitor without the override settings continues to apply to all other objects in the targeted class.
    For all objects of another class            
    When you select this option for your override, the override settings apply only to objects of a class other than the targeted class. The rule or monitor without the override settings continues to apply to all objects in the targeted class.
    Did you try to override it for a specific object of class?
    Regards,
    Yan Li
    Regards, Yan Li

  • Adobe Acrobat -Create PDF 1.0 does not work in FireFox 4.How do i directly convert pages to PDF??Why is that your products are not backward compatable.U people are in the IT industry and should know this.Shame on You people.learn somthing form the IE team

    While Updating to Fire Fox 4. It said Adobe Acrobat -Create PDF 1.0 is not supported.How come 3.6 supports but not 4. I believe you people have never heard of the term "Backward Compatibility" .U people will loose your customer/support base if every new version doesn't support some existing stuff.

    '''Problem Solved FINALLY !'''
    Solution:
    I just updated my '''Adobe Acrobat X Pro''' to '''Version 10.1.0'''.By the way, I have to complain, Adobe is really slow in solving this problem...
    Here is the official link for the Adobe Acrobat update.[http://www.adobe.com/support/downloads/detail.jsp?ftpID=5135 <click me!>http://www.adobe.com/support/downloads/detail.jsp?ftpID=5135<click me!>]
    After update, the extention changed from "Adobe Acrobat -Create PDF 1.0" into "Adobe Acrobat - Create PDF 1.1". And the '''"Adobe Acrobat - Create PDF 1.1" is compatiable with the firefox 4.0.1'''. A screenshot is attached as a proof.

  • InDesign Backwards Compatibility in CS5 an MAJOR issue

    I am a print designer who works in InDesign. I bought CS3 Design Premium in late summer of 2008. Shortly thereafter CS4 came out, but after just having forked out a big chunk of change, I decided against upgrading to CS4 right away. Recently I considered upgrading but then heard CS5 was coming out so I decided to postpone the upgrade and wait for the new software. I've just checked out the trial version of CS5 InDesign and after speaking with Adobe Support have come to the conclusion that I can't upgrade to CS5. Why? BACKWARDS compatibility to CS3. The previously offered export features that supplied a path for backwards compatibility via an .inx file are gone.
    I design freelance for a lot of different customers and once the design is complete, I have to deliver the InDesign file along with all associated fonts ad images to my clients. Most of my clients are still on CS3. If I upgrade to CS5 I will instantly not be able to work for 2/3 of my clients, as I will have no means by which to save a file backwards to CS3. I was informed by Adobe support that I would need to buy CS4 and CS5, as I could save my CS5 file in the IDML format and open it in CS4 and then I could save the file from CS4 as an INX file and open that is CS3. ARE THEY INSANE??? First off that requires keeping 3 version of InDesign up and running on my machine all of the time and secondly, why should I have to buy CS4 when I'm paying an additional fee to upgrade to CS5 because I didn't upgrade from CS4? This is so screwed up that it has to be an oversight---please tell me there is a patch in the works!!!
    PS- I've never posted to a forum before, so if I have broken any rules of forum etiquette or offended in any way, I offer my apologies now and if I (and the Adobe Support staff I spoke to) have overlooked something, please enlighten me!

    Cynthia Ryan Graphic wrote:
    I am all for working with better workflow practices and I understand that saving files backwards is less than ideal but Adobe needs to look at the real world uses of their software as well. I have to work with firms that aren't upgrading now--especially with the economy we are now in--and most of the items I design for them are ads-- one page- nothing too complex--really nothing fancy. I obviously wouldn't save a book or a very complex document backwards in this way, but simple things have translated just fine in the past. In the real world we hit situations like this.
    I bought my software 21 months ago and in this time Adobe has expected me to upgrade twice--I haven't even finished expensing  the initial cost of the software on my books yet. Upgrading that often just can't happen in a small firm--it's prohibitively expensive for a one man shop.
    So now from what I understand, to do this properly, I am supposed to buy the upgrade and keep both versions running on my machine and track with every client which version of the software I need to be working in. What happens when I have to add an employee? I will have to buy the CS3 version of the software in addition to the CS5 Suite because otherwise we can't work on the same files. I'm finding this frustrating.
    Your suggestion of buying CS4 from Amazon is a good one. I will look into that further.
    DISCLAIMER: I'm an Adobe stockholder. REALITY: My holdings are probably in the same proportion as the number of bits it takes to store a period character (".") on an Internet server is to the entire Internet's storage capacity. So, while I may have some self-interest here, it's not driving me to encourage you - or even all the participants on this forum - to buy more software than you want to or need to.
    If you're simply interested in test-driving a new release, you can do that with the free 30-day trials. If you run out time, you can probably figure out a way to trick out your system to get another 30-day shot.
    However, if you use the software commercially - either to train others, or to create new material or revise old material for clients or employers - you need to decide if you can continue to do this with the software versions you own, or if the commercial needs will require you to license new versions.
    Regarding "expensing the initial cost of the software on my books" If I understand the US income-tax policies, purchases under a rather modest amount can usually be expensed in the year of purchase. If, because of your accounting method or preference, you're using a longer expensing time period, you might want to reevaluate your approach. If you attribute a portion of the software cost to each project you use it on, and, in this case, in 21 months your work hasn't let you recapture the investment, they you may want to use that information to decide how to pursue more paying for the software, or decline that stream of work and forgo upgrading.
    An alternate way to evaluate the software, especially as an employer of users, is to compare the product cost vs. how many more billable hours you and your workers can complete in a given time with it and without it, and, how competitively you can bid projects, due to the product's efficiency.
    HTH
    Regards,
    Peter
    Peter Gold
    KnowHow ProServices

  • I want to install Snow Leopard Server on our MacPro (2.66) using Mac Mini Snow Leopard Server disks?  I kept getting an error for backwards compatibility.   Is this possible or do I need to purchase another copy of Snow Leopard Server?

    I want to install Snow Leopard Server on our MacPro(2.66) using Mac Mini Snow Leopard Server disks?  I kept getting an error for backwards compatibility.   Is this possible or do I need topurchase another copy of Snow Leopard Server?

    The OS disks that are shipped with a particular product
    are set up so that tey will only install on that product.
    It will install on any Mini of that exact vintage, but that
    is all.
    This is to prevent people from doing exactly what you
    are trying to do.  The license for OSX shipped with any
    is only valid for that product.  Also, Snow Leopard,
    including Server, is only permitted to be run on one
    computer at a time.  Bottom line, unlike Lion, legally
    you cannot install the same copy on multiple
    computers unless some "family pack" or site license
    is purchased.
    Yes, you need to purchase another copy.
    The copy of Snow Leopard license is here:
    http://images.apple.com/legal/sla/docs/macosx_snowleopard.pdf

  • Specific Flash Player 10 Backward Compatibility Issue

    There's an issue with backward compatibility on Flash Player
    10 that is breaking a lot of Flash content that was created with a
    tool that I develop and sell. It is to do with the way
    globalToLocal and localToGlobal handles NaN.
    I've reported it on the bugbase at
    https://bugs.adobe.com/jira/browse/FP-964
    There are more details here -
    http://www.questionwriterblog.com/archives/2008/11/scrollbar_causing_content_to_disappear. html
    The impact of the bug can be seen here.
    http://www.questionwriter.com/samples/fp10problem/v1perceptions.swf
    It is a serious enough backward compatibility issue, and
    doubtless affects other content too. I'm hoping for the outcome
    that the functionality will be restored in future player releases -
    but right now, can someone give me confirmation it is on the Flash
    Player team radar?

    bump!

  • Backward Compatibility

    Hi
    Our application is composed of few data layers. The layers comunicate through interfaces.
    My manager thinks that we should maintain backward compatibility between the layers.
    So:
    There is a defined functional interface "I".
    There is a layer component "L" which provides the functionality of I.
    There is a layer component "UL" which Uses L via I.
    A new layer component "L2" is created which has greater functionality than L and which it exposes via a new interface "I2".
    All the functions of I are also provided by I2. In other words, I is a subset of I2.
    "UL" will provide to a "layer factory" a version number, and the factory will return "L" or "L2" etc.
    This means that we cannot override methods, and difficult maintaining of code as well as code duplication.
    The bennefit of this is that all the components that worked fine with the previous "L" and were not changed, are guarantied to continue working, and needn't any QA.
    What do you think? Does it worth the trouble?
    Thanks,
    Libbhy

    libbysharf wrote:
    The bennefit of this is that all the components that worked fine with the previous "L" and were not changed, are guarantied to continue working, and needn't any QA.Based on what you have stated here, this is not necessarily the case. Just having the same method signatures doesn't not mean that it will work exactly the same way. Even if the methods from L are implemented in the exact same way in L2, you could have situations where the new L2 methods change the behavior of the old L methods.
    What do you think? Does it worth the trouble?Personally, I think it seems a little over-engineered. If you just add to a class, it will not break binary compatibility with existing clients. You'd be much better off spending time creating unit tests and regression test scripts and try to verify that the behaviors from the previous verison are maintained.

  • Backward Compatibility Question

    Our ADS system is running with Basis 7.0 SAPKB70005
    Can we develop forms on systems with a lower Basis version e.g. 6.4?
    Are there backward compatibility issues?
    Regards,
    Lavaughn

    Hi Lavaughn
    it depends a bit on what you want to do.
    If you want to develop the form on the 6.40 box and then render it with the 7.0 Application Server, the answer is No, as the solution always needs to be on the same NW level (i.e. either '04 or 2004s). SAP development always coordinates changes between Designer, ADS, Reader, and the SAP development environment - and there are a few incompatible changes between '04 and 2004s.
    If you want to develop and render the forms on the 7.0 box and integrate data from a lower-release backend (e.g. R/3 Enterprise), you can do that for interactive scenarios using RFC connections to transfer the data and/or the PDF form from system to system.
    Do not attempt to do this for print forms. The amount of data that may have to be transferred will heavily impact the form generation time.
    Kind regards,
    Markus Meisl
    SAP NetWeaver Product Management

  • I am considering CS6. I worry about "backwards compatability." I am in a windows-only environment.  Some files were antiquated mac computer.  Files are: psd doc eps tif indd otf ai jpg RW2 xmp pm7 bmp fh9 fh10 dng pm6 and ps. Rick

    I am considering CS6. I worry about
    "backwards compatability." I am in a windows-only environment.  Some files were antiquated mac computer.  Files are: psd doc eps tif indd otf ai jpg
    RW2 xmp pm7 bmp fh9 fh10 dng pm6 and ps. Rick

    Backward compatibility FROM what TO what?
    CS6 to older, or newer to CS6?
    For specific answers, you most likely need to check in the forums for specific programs
    The Cloud forum is not about using individual programs
    The Cloud forum is about the Cloud as a delivery & install process
    If you will start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll

Maybe you are looking for