CS5 and the slideshow template

I just upgraded from Flash CS4 to CS5 and have discovered that the slide show template is no longer supported.
Does anyone know if flash slideshows will be supported in upcoming versions of the Flash player or will they be discontinued?

Thanks for the ideas!
When I try to open a CS4 fla containing a slideshow with CS5 it gives an error message "Slides and Forms documents are not supported in this version of Flash. Please open in a previous version."
I called Adobe support and was told I would have to reauthor the slide show as a frame based app. After working for several years creating slide based flash presentations this is not good news.
I guess my fear now is that if they dropped support for slides and forms in CS5 will they drop support for them in newer versions of Flash player as well. Yikes! That would sink me for sure.

Similar Messages

How can I change the counter symbols for the slideshow templates in Muse?

How can I change the counter symbols for the slideshow templates in Muse? Currently they are obviously normal text characters. So, how can I change them to filled circles, for example?

Hi Aish,
Thank you very much. This was very helpful. I am still new to Muse and try to find my way through all the features and possibilities. I like it very much so far.
Does Muse support ‘liquid” design as well?
Thank you !
Best regards,
Fred

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images

Any ideas?

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images from Lightroom and choosing the "Render using Lightroom option when it popped up in the dialogue box. She has been doing this for over a year and a half without any problem. Today when she hit Command E no dialogue box appeared and the image just opened in Photoshop. I'm concerned that all of her Lightroom edits are not being rendered to Photoshop. Anyone have an idea as to how we can get the "Render using Lightroom" dialogue back?

I had to reinstall Win 7 and PS CS5, and the updates fail even when opened using 'run-as-admin'. Why?

The title says it all ...
I had to reinstall Win 7 and PS CS5, and the updates fail even when opened using 'run-as-admin'. Why?

If you are using Help 》updates, it is outdated. You can however go to Product Updates on the Adobe.com website and download your updates there. I am not at my desk b<t when I get back, I'll get the links unless someone else can do that sooner.

I have Photoshop cs5 and the pen does not work. The icons below also do not work. Why? and how can I activate them? Thank you , Wren

I have Photoshop cs5 and the pen does not work. The icons below also do not work. Why? and how can I activate them? Thank you , Wren

Why?
Do you expect an answer to that question based on the information you have provided so far?
Please read these and proceed accordingly:
http://blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-mos t-issues.html
http://forums.adobe.com/docs/DOC-2325

I work with photoshop CS5 and the stamp is very slow. Why?

I work with photoshop CS5 and the stamp is verry slow. Why?

If you can afford it, go with a Crucial M4 SSD.
If your in a limited budget, go with a Seagate Momentus XT 750GB.
The SSD will be the fastest one and the Seagate being faster than a conventional drive.
If you decide to go conventional, avoid the Western Digital Scorpio Blue. They tend to have issues with Macbooks.
Good luck

Burned iDVD project and the slideshow is messed up.

I made a project and played it on my computer to preview before it was burned and it was fine so I burned it. But when I put it in my DVD player and my Vaio, the slideshow portion of the DVD is messed up. Plus when I put it in my Mac it doesnt even play. There is a green screen where the transition WOULD have been, then one of the pictures comes up, green screen, then another picture, etc. So instead of my transition I have a green screen.
Also, this is the 2nd DVD I've burned. I changed the transition in the 1st one to see if that would solve the problem but my 2nd one is messed up too. On the first DVD I get weird iDVD images (icons, theme stuff, etc) that pop up randomly on the picture as the transition starts.
What's up with this?

Before going any further, give this basic remedy a try. Quit iDVD and delete your iDVD preferences. To do this, go to your username> library> preferences> com.apple.idvd.plist. Delete this file. Then reopen iDVD; it will create a new preference file with all of the default settings.
Do a verify and repair of permissions using Disk Utility.
As far as the disk image, I made one but my computer wont even play it.
Did you use your computer's DVD player? If you cannot find the player, use Spotlight to locate it. Look for "DVD player".
To view a disk image, first double-click on the icon for your project. Then open your DVD player by double-clicking on the icon in the applications folder. Another way to view the disc image is to open DVD Player in your Applications folder, then use its Open command to select your disc image.
Besides, I burned the disk image to a DVD and its just a file, not a playable DVD.
If the disk image does not play properly on your computer's DVD player, then the burned disk also will not work.
Did you use Disk Utility to burn the disk? A DVD that is burned via the Finder will not work on a standard DVD player.
For troubleshooting purposes, try to create a project using another account. Create the disk image, and see if you can get it to play. If things work correctly, then the problem lies within your account. If it persists, you might have to do a reinstall of iDVD.
I hope this helps.
Message was edited by: Glo H

What exactly is the issue with CS5 and the retina display?

Just picked up a late 2013 MBP with retina display and have PS CS5 running on it.
What is the exact issue that I should be having when it comes to running CS5 on these machines ? Is it just that the UI looks fuzzy? Other than that it seems to run fine and my photos look fine also.

What issue?"
That is what I am asking...Like I said, I am able to open CS5 on my new retina mbp and edit image files with no issue..the only thing that I notice that seems off is the text of the UI seems "fuzzy"....
So, what I am asking is what exactly is the problem supposed to be that I should be seeing?

I bought photoshop cs5 and the keep coming back as not working number but turns on photoshop tells me to buy new number ?

I bought photoshop cs5 new in abode box etc will not work when on line said it needs s/n and to buy it ?

Where did you buy CS5 at this point? Otherwise serial number issues is only something support can handle, so use the web chat or call them by phone.
Mylenium

CS5 and the new Mac OS

Does CS5 work with the new Mavericks? I'd like to update my OS, but only if CS5 works with it.

http://helpx.adobe.com/x-productkb/global/mac-os-mavericks-compatability.html

Has there been any updates for CS5 and the MacBook Retina displays? Everything still looks pixelated.

I keep getting errors when trying to update it.

here are the older version updates, http://www.adobe.com/downloads/updates/, but it's not likely that adobe will work on making older versions work with new os'es.

Books and SlideShows...One And The Same?

Is there any way to scale a photo one way for a slideshow and crop it another way for a book?
When I scale a photo for a Book it changes respectively for the Slideshow.
But I have it adjusted diferently for the Slideshow.
What gives?

Why are the Book and the Slideshow liknked and not separate entities?
Because, as I said, they REFERENCE the photos in the event
This is actually a bnenefit in the long run - but to provide Apple with you comments go to the iPhoto menu ==> Provide iPhoto Feedback. This is a users forum - people here can assist you in understanding and using iPhoto and sometimes can provide work arounds for you but can NOT change anything
Larry Nebel

The bullet list, numbered list and the normal text is not converting when I am converting from RH 9 to MS Word 2010

Hi all,
Greetings for the day
I am created a new CSS in Robohelp 9. I have also created a new template in Word 2010. The style sets for different information elements like (Heading, bullets, body text, ) are more or less same between the CSS and the new templates. I am also able to map the .css styles to Word template when I am converting from RH to Word as I am getting the necessary option in the drop-down list.
However, when the output is generated, the bullet, the numbered list and the body text is not converting at all. The body text works sometimes. However, the numbered list and bullet list is coming out as images.
If anybody knows the solution, I can share the .css and Word template.
Thanks in advance.
Regards,
Parag Deb

Create a new project with two or three topics containing lists of both types. Generate a printed output that shows the problem. Then zip it up and send it to me. See the Contact page on my site for instructions.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

How do i get the slideshow to display on my external monitor in extended view with powerpoint?

i have my T500 (windows 7) connected to a large external monitor with extended view. when i run powerpoint it displays the slideshow on my laptap screen instead of the external view. how can i have the presenter view show on my laptop, and the slideshow show on the external monitor/projector?
thanks!

You can do it that way, (Clone) but everything you do on your laptop will also be displayed on the monitor.
Assuming you would like the display on the external and freedom to navigate on your laptop without broadcasting, you would need to adjust your slide show settings in PowerPoint.
To use this procedure:
In PowerPoint, On the Slide Show menu, click Set Up Show.
Under Multiple monitors > Display slide show on drop down menu: select the monitor you want the slide show to appear on.

Deciphering Aperture Web Themes: the html templates v3

version 3 of my Aperture Web Theme html template reference. enjoy
the html templates.
rkid attributes:
Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
  <ul id="nav" rkid="navbar">
These are the rkid values that I've identified so far:
  "navbar"
    a <ul> element containing all of the navigation elements.
  "active" and "inactive"
    rkid attributes to enable the coder to place different formatting on
    current and non-current page numbers in the navbar.
    eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
      <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
  "content"
    a <div> containing all of the album images and their metadata.
  "pictureblock"
    a mandatory <table> in which the images are placed, one image per <td>.
    the <table> must even be used on the Detail page where only one image is
    displayed.
    the metadata will be within the "pictureblock" table if more than one
    image is displayed so that the metadata can be tied to the image. if
    only one image is displayed; i.e., the Detail page; the metadata may be
    in a <td> outside of the table that the image is in but still within the
    "content" div, usually in the following format:
      <div rkid="content">
        <table>
          <td>metadata
          <td><table rkid="pictureblock">
  "image"
    the rkid for the <img> elements containing the album images, frequently
    placed in <dt> elements within the table's cells.
  "metadata" (added in Decipher v3)
    all metadata for the respective image is specified within this element.
    everything within the element is repeated for every metadata value.
    the Aperture themes use the <ul> element but <div> also works:
      <div rkid="metadata"><p>metaname: metavalue</p></div>
  "titleblock"
    a <div> containing the title text; usually <h3>; for Journals. the <h3>
    element within this element must be given the attribute rkid="text" or
    Aperture will ignore it.
  "textblock"
    a <div> containing the description text for Journals. as with the
    titleblock, the <p> element/s within this div must be given the
    attribute rkid="text".
  "text"
    the rkid given to the text data within the titleblock and textblock
    elements.
Place holders:
  PageTitle
    used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
  IndexPageURL
    the gallery page/s URLs; may be more than one.
  ThumbImageURL
    the href links for the images, whether thumbnails or detail full size.
  DetailPageURL
  used within navbar:
    PageCount
    PageNumber
    PreviousPageNumber
    PreviousPageURL
    NextPageNumber
    NextPageURL
    PageCount the total number of pages
    PageNumber includes all of the page numbers listed in the navbar, one
      occurrence for each page.
    _Previous and _Next are more specific and are currently used to draw the
      prev/next arrows in the navbar.
  ImageName
  ImageNameSpace
  PlateNameSpace
  PlateNumberSpaceSlash
    *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
      chosen.
    used to represent an index of the image in the album. the first image
      shown gets the index 1, the second 2 and so on.
    for the Image placeholders, the word 'Image' is used.
    for the Plate placeholders, the word 'Plate' is used.
    space indicates an extra space after the index, probably for html
      formatting purposes because it's only used within <dt> elements.
    slash indicates an extra / character after the index.
    examples:
      ImageName > 'Image 1'.
      ImageNameSpace > 'Image 1 '.
      PlateNameSpace > 'Plate 1 '.
      PlateNumberSpaceSlash > '1 / '.
  metaname
  metavalue
    the placeholders for all of the metadata names/values in the selected
    metadata set.
  PageWidth
    not sure if Aperture calculates it based on the width and number of
    images being displayed in both gallery and detail pages.
    don't know why it's only used in the Special Occasion theme.
  CellWidth
    the width of the table cells containing the album images. not
    necessarily the width of the images. may include margins as specified in
    the albuminfo.plist files.
  ImageWidth
    the width of the image.
  TableWidth
    the width of the pictureblock table. it can probably be applied to other
    elements too but it's length is almost certainly calculated from the
    pictureblock table.
Operative attributes:
  removeonfirstpage="yes"
    used in the navbar to remove the Prev link from the first page.
    because it's applied to the <a> element, the <a> element is removed
      while leaving an empty <li> in place.
  removeonlastpage="yes"
    used in the navbar to remove the Next link from the last page.
    because it's applied to the <a> element, the <a> element is removed
      while leaving an empty <li> in place.
  removeonsinglepage="yes"
    used in the navbar to remove elements when there's only one page.
    used in a <div> in the Art Collection to remove the whole navbar on
    single pages.
  contenteditable="yes"
    used in text elements to indicate that the user can customise the text.
    not necessary in titleblock and textblock rkid="text" elements.
    in elements outside of the titleblock and textblock elements, content
    will not be truly editable unless a textid is assigned to the text
    elements. unfortunately, all text elements with textids are always
    'common' and can not be specific to any one image.
  common="yes"
    the element is seen on all pages.
Other attributes:
  metaseparator="|"
    used in metadata formatting, within the metadata lists.
    you can add additional characters. for example, the metaseparator
    in the Stock Black theme is " | "; ie, a | bar with a space on both
    sides. (Decipher v3)
    if the metaseparator is specified and the html template places the
    metadata into <li> elements as it does in most of the current themes,
    then it produces non-standard html code with the metaseparator between
    concurrent <li> elements.
  metalayout="paragraph"
    used in metadata formatting, within the metadata lists.
    if not specified, the metadata will not be exported. (Decipher v3)
  singlenesting="yes"
    used in metadata formatting. not sure what it does yet.
  textid="x"
    used to id text elements outside of the titleblock and textblock
    elements.
    possibly no limit to the number and id names used.
    examples used:
      textid="copyright"
      textid="header1"
  picturename="x"
  pictureimage="true"
    picturename gives the image an id.
    pictureimage="true" tells Aperture that the image is a static image
    which can be designated by the user during setup of the album. they show
    up in Aperture as grey blank rectangles with cross-eyes in the middle.
    they do not need to be inside the "content" element
    with picturename and pictureimage, we can place as many static images on
    the page as we wish.
Assertions:
  Aperture uses the rkid values to identify the areas of the html to be
  repeated for the respective objects.
  standard id and class attributes are only used by the css for formatting and
  not by Aperture to write the html data.
Notes:
  Aperture is hardcoded to expect and require that the album images are always
  within a <table rkid="pictureblock"> element. it is not possible to place
  album images outside of the table. all album images must be placed within
  <td> cells within the table. the <td> code is repeated for each image.
  image metadata is also normally within the rkid="content" element although
  it can be outside of the rkid="pictureblock" element.
  by default, the textblock rkid="text" element is added when the T+ button is
  pressed within Aperture. the textblock element is switched with the
  titleblock element when the Title/Text toggle button is clicked.
  width and height attributes of <img> elements are rewritten by Aperture
  based on the inserted images. placeholders aren't necessary within <img>
  elements.
  comments are stripped from the html before export some but some
  Aperture-proprietary attributes are forgotten and left behind.
  some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
  doctype.
  all markup is converted and exported in UPPER-CASE. personally, I prefer
  lower-case.
  high-ascii characters entered by the user are not converted to their html
  entities when available. eg, the © character.
  multiple <p> elements can be inserted into the titleblock and textblock
  <div> elements but each of them must have the rkid="text" attribute. any
  element without this attribute will be ommitted by Aperture.
  the reason there are Smart Galleries but no Smart Journals is because you
  need to write text between each row of images.
  titleblock and textblock elements will not be applied to Galleries or Detail
  templates; only to Journals.
  if there are more than one titleblock or more than one textblock, only the
  first will be used by Aperture.
  upon export, Aperture will remove everything from within the rkid="content"
  element which is not the pictureblock, titleblock or textblock elements.
  (Decipher v3)
  some of the Aperture templates have xhtml doctypes but are exported from
  Aperture with html 4.0 loose doctypes. weird! worthy of note is the fact
  that UPPER-CASE element names is not permitted with xhtml which is
  case-sensitive. (Decipher v3)
Questions:
  are there variable scopes with each rkid? eg, within the "content" rkid, can
  every variable/placeholder be accessed?
  why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
  the images and related metadata in the table? easier css formatting?
JavaScript: (Decipher v3)
  you can include JavaScript in the html code but cannot wrap it in html
  comments because Aperture will remove everything within comments.
  Aperture variables such as PageNumber will not be replaced within
  attributes such as <body onload="dialog(PageNumber);">.
  it is very difficult to use document.write anywhere within the html <body>.
  Aperture seems to be using JavaScript to export the html and its code is not
  able to cope with more than one instance of document.write in the html
  templates. after hours of trial and error, I found that the most stable way
  to use JavaScript within the html <body> was to only use one <script>
  element and place everything within it. using document.write within a second
  <script> element would almost certainly lead to unpredictable exported html,
  and instability and crashes in Aperture.
iMac Duo Core 2GHz 2GB Mac OS X (10.4.6)

It worked. I still have a few tweaks to do on my final template, but the method I described above works. I've set up my templates like this:
1) one large image per thumbnail page (like a photo essay or photo blog style)
2) same size image on detail page, but with paypal buttons directly below in their own table (I have several different paypal buttons - for different print sizes and a couple other things like postcards, etc.)
The neatest thing about this setup is that since it's all controlled by flat html and css, it looks almost like javascript the way the paypal buttons pop up - the image stays in exactly the same place and the buttons just appear below it (haven't tried it on a slow connection, though, probably a slight delay).
This is great because I hate javascript but sometimes like the immediate visual effects it allows.
This template makes it trivial to create a reverse chronological gallery/journal - kind of like a photoblog - and allows visitors to view the large images without the extra clutter of the buttons, but then they can just click on the image to reveal the buttons and click the image again to hide them.
The benefit of putting these buttons directly into the Aperture templates rather than using a find-replace script to add them to iWeb pages after processing? Well, using Aperture, I can add the PageTitle tag to the Paypal button - it doesn't work in hidden form fields or anything that needs to go inside an attribute, but it does parse using a textarea field, which I hid with CSS - This alleviates the problem many photographer sites have where they ask the buyer to email them with the image name/number they want - this way, the shopping cart automatically knows which image they're ordering.
PageTitle uses the following format: Gallery/Journal Name - Image/Version Name
So using this tag in the Paypal button tells me which image the buyer wants and which gallery they were viewing when they ordered - simple but effective.
Anyway, I know it's been a few weeks since I last replied, but I thought I would post this for others who might be interested in doing something similar - entirely through Aperture. Sorry about the run-on sentences; I'm a bit pre-occupied to proofread today.

CS5 and the slideshow template

Similar Messages

Maybe you are looking for