Hi Kevin
Okay, let's see what we can pick apart. I did receive a note
back from my contact late last night. I'll insert what he had to
say after I deal with some other things here.
Have you noticed whether it is related to a specific
application you try and record? For example, if you try perhaps
something like recording Windows Notepad, are you okay?
When you are actually in the recording process, the one that
results in a single, blank slide, as you are going about things are
you hearing the camera shutter sounds as if Captivate is doing what
is expected?
You said:
"Final note: After I capture and receive one blank slide, I
can go into File>Record/Create>Additional Slides and properly
record an application process. Even though this is a workaround,
for this I CANNOT use multi-modal publishing which is the #1 reason
I upgraded to Captivate 3!! So whatever the issue is, it's with
recording a process from the opening menu."
I'm guessing you meant to say "muti-modal
recording?
If so, this triggered a thought. I know you listed only a
single mode as being enabled. Multi-mode recording is totally new
to this version of Captivate. So this makes me wonder if we aren't
possibly seeing a bit of weirdness as a result.
Okay, now here is what my contact sent me back:
There could be multiple reasons. I will give you some
information on the basic capturing.
As you know that Captivate will take a screenshot for every
mouse and key event send to the Operating System. This is the
default behavior of Captivate. If the user gets only a single slide
after capturing it means that no events were sent to Captivate or
Captivate has been configured for not receiving any event.
First case: Captivate has been configured for not handling
any of the key event. This is done using manual recording as the
options. Captivate recording options has this option where user has
to take screenshot only by print screen key. The option 'record
keystrokes' is also important in this case. This option is usually
ON.
Second case: The classic case for this is using Captivate 2
on Vista OS. In this case, the high security features of Vista
disable any key event to be sent to Captivate. We have fix this in
CA3 but there are still some high secure applications where
Captivate will not be able to take the screenshot. This is mention
in the Help of Captivate. Applications like Internet Information
Systems, Network Diagnosis, etc are elevated at a higher priority
by Vista. There are workaround to make this work.
Third case: We have also found some applications which will
eat away the event and not passing that events to be send back to
the OS. Application of very high sensitive nature where it was
design in such a way that no hacking is possible comes under this
category. Till date I have seen only 1 application which has
problem with Captivate.
What to look for: First and foremost, any capturing failure
usually lead to what kind of application was used in capturing. To
be sure that it is not the application being capture that is
causing the problem, user should be advise to do the same on a
simple application like notepad. If the failure still occurs then
we need to know the Operating Systems used and what type of user
was logged in (permissions, etc.). Sometimes, it could be very
simple configuration issues like checking whether record keystrokes
was OFF or ON.
Cheers... Rick