Questions of the Week

Question on Adobe Captivate 2Developer Playbar

In addition to my skin, there is a playbar on the right side of the slide. I can’t figure out where it comes from.  I’ve attached a picture of it at the right.  Any hints or help would be greatly appreciated.

Answer

You are talking about the developer playbar that is visible at the right of your window when you preview your slides. The playbar does not appear in your published projects.


Another Question on Adobe Captivate 2

I need the users to be able to right-click to demonstrate short cut menus.  I would think this would be something that Captivate would surely be able to do, but I only see the capability to do single or double-clicking.  Do you have any suggestions?

Answer

Files you Publish with Adobe Captivate do not support a right-click in a simulation. Why? The Flash Player uses right-clicking to allow users to view and change the player’s settings. There are some options you might want to investigate posted in an article on the Captivate Developer Center.

Got a question or comment? Email it to us.

Adobe Captivate 2: Combining Question Slides in a Simulation? No Problem!

What’s the difference between a Captivate simulation and demonstration? Typically speaking, a simulation is interactive; a demonstration isn’t. Between the two, I urge you to create simulations because simulations will encourage your users to actively participate in your lessons. (Unless budget is not a concern, in which case by all means create both a simulation and demonstration for each and every lesson.)

While markedly different, simulations and demonstrations can both include Question Slides that can validate your lessons. But should you include the Question Slides in your project, or should you keep the Question Slides separate? Personally, I tend to keep the Questions Slides in a separate project and make the quiz available via a link on my LMS. Because you will have to worry about the Reporting options of the non-quiz slides, keeping the projects segregated is the cleanest/easiest way to go.

If you do decide to include Question Slides in a simulation, be warned–you could be throwing off your scoring results unless you take the appropriate evasive action.

How so? I’ve had several customer’s who have included interactive slides (slides with Buttons, Click Boxes or Text Entry Boxes) and sprinkled Question Slides throughout the project. Upon playback, the scoring was off (the user failed even if they answered the questions correctly) or the Question Slide numbers were off (the first Question Slide would say it was number 2 of 5 when it was the first Question Slide).

When you add Question Slides in the middle of interactive slides, Captivate treats everything like a quiz, even though the interactive slides may not be an actual part of the quiz. What’s a developer to do? Well, as they say, "If you can’t beat them…" We decided to treat the Interactive objects as part of the quiz without having the interactive elements actually count as points in the quiz.

Controlling How Objects Report Scores

  1. Open an interactive slide and double-click the interactive object
  2. Select the Reporting tab
  3. Select Include in Quiz and Report Answers
  4. Change the Point to 0
  5. Reporting in Captivate 2

  6. Click OK

One important step to remember here:

  1. Choose Project > Quiz Manager
  2. On the Quiz Settings tab, ensure Allow backward movement is selected in the Settings area (this will allow users to go back to the interactive slides–without this setting enabled, users would be able to click the Button or Click Box, to move to the next slide, but would not be able to go back and take the lesson again)
  3. Captivate Quiz Settings

  4. Click OK

Want to learn more about Adobe Captivate 2? Click here.

Click here to sample some of our 100% interactive simulations.

Adobe RoboHelp 6 HTML: What’s in a Name? Changing Project, Title & Start Page Names

Anyone who has attempted to rename project files in RoboHelp can tell you that it’s not as cut and dry as it seems. When renaming project files, it’s important to realize that there are three places you may need to go, depending on what you are trying to rename.

Rename the Project

If your goal is to change the name of the project (the XPJ file that is the backbone of your entire project), follow these steps:

  1. Choose File > Rename Project
  2. Give your project the desired new name (avoid spaces in the project name)
  3. Rename a RoboHelp Project

  4. Click OK

    There will not be a visible change on your screen. However, if you were to explore your project folder, you would see that the new project name is now being used by the XPJ file and a gaggle of support files.

Change the Project Title

The Project Title appears in the title bar of the browser window when your Help system first appears on a user’s screen. Follow these steps to change the Project Title:

  1. Choose File > Project Settings

  2. Change the Project Title as you see fit (you can and should use spaces in the Project Title)
  3. Change RoboHelp Project Settings

  4. Click OK

    The changes to the Project Title will appear the next time you generate WebHelp or FlashHelp.

Change the Start Page

The Start Page is the first page that appears when the Help system is called by the user. It’s a frameset and can be given any name you like (typically, the Start Page is given the name index.htm). Follow these steps to change the name of the Start Page:

  1. Right-click a WebHelp or FlashHelp layout in the Single Source Layouts folder
  2. From the Select Output Folder and Start Page area, change the name of the Start Page
  3. RoboHelp Output Start Page

  4. Click OK

    The change you made to the name of the Start Page will not manifest itself until you next Generate the project.

Click here to learn more about our step-by-step RoboHelp workbook (Essentials of Adobe RoboHelp HTML 6).

You can now teach yourself RoboHelp via our online, interactive lessons. Click here to learn more about the course and to test drive a few of the lessons for free.

QuarkXPress 7: Creating Tickets From Job Jackets

In the last episode of this newsletter, you learned how to create Job Jackets in QuarkXPress that controls the specifications of a layout at the time it is created.

So now what? From Job Jackets, come Job Tickets. Each Job Jacket can have multiple Job Tickets. And each Ticket can contain Resources that can be applied to a Quark project.
Here are some of the Resources you can include in a Ticket:

Project settings: Style sheets, colors, output styles and color management settings

Layout definitions: A Layout Specification (page size, orientation), Output Specifications, Rule Sets, Medium type (Print or Web), Color management settings, and Proofing specifications (Proof Output)

Create a Ticket from a Job Jacket

  1. Display the Job Jackets Manager.
  2. Select a Job Jacket from the Job Jacket list at the left
  3. Click the New Ticket Template button
  4. New Ticket Template button

    The new ticket appears with the default name, "Ticket."

  5. Highlight the Ticket name (it may take 2 clicks to highlight the name)
  6. Change the ticket name and press [return]

Set Ticket Resources

  1. If necessary, click the Advanced Settings button (if the Basic Settings button is displayed, you are currently viewing the Advanced Settings)
  2. Job Jacket Manager

  3. Select Layouts from the Resources area of the ticket you created earlier
  4. Click the New Item button on the last panel

    A new layout item is created with the default name.

  5. Click the plus sign (or triangle) at the left of the item name to expand the item
  6. Select Print from the Medium type list (at the right of Medium type)
  7. Scroll down and select Layout Specification from the Layout Specification list (you learned how to create the Layout Specification last week when you were first introduced to Job Jackets in QuarkXPress)
  8. Select a Layout from the Layouts area
  9. Ticket Layout Specifications

  10. Click Save

Next week: Creating Rules for Tickets

Want to learn more about QuarkXPress 7? Click here.

Comment of the Week

Maximizing the Appearance of Transparent Text Captions: Another Possible Solution

Two weeks ago I ran an article offering a technique for sharpening the appearance of the text in a transparent Text Caption.

Fellow subscriber Brooke Schepker offers the following:

"Regarding the text quality problem in Captivate, we have two other solutions as well.  We have noticed that adding bullets or an underline to any of the text in the caption improves the text quality.  If we don’t have a need for either of those font options, we just hit enter a couple of times, add a bullet, and click OK.  Then, we shrink the size of the caption to remove the bullet from view."

Got a question or comment? Email it to us.