November 2, 2018
MC Quiz Retry Image Fill Problem – Captivate is Deleting and Resizing my PNGs
Comments
(4)
November 2, 2018
MC Quiz Retry Image Fill Problem – Captivate is Deleting and Resizing my PNGs
Newbie 1 posts
Followers: 0 people
(4)

Hello,

In both versions of Cap 2017 and 2019, I’m having an issue where I’ve got a small png file, 75 kb, that I’m using as the retry message fill when someone gets a quiz question wrong. I’ve customized the Incorrect and Retry shapes by selecting Fill and using the same image in my library.  It works fine for the incorrect shape. No problems. I could have 10 of these in my module and every time it works. Even if I save, close, and reopen. No problems. This is for T/F slides.

But the retry shape – it does weird stuff.  Let me first say I use the retry shape for multiple choice, multiple answer/infinite attempts so that they keep getting a message if they’ve submitted more than one wrong answer. We want people to get the answer correct before they can continue.

Here’s the thing, sometimes it works for retry when I first import the image. Sometimes, when I open the custom image option and select the file to use, it actually creates a new file version – it adds (2), (3), an so on – for the file name and then increases the image size to 1344kb!  Sometimes, when it seems to work at first, next time I open the captivate file, captivate automatically deleted the custom image from the fill. When I try to select it again from the library, it starts creating new files and increasing the size again. Totally frustrating. I’ve tried updating and importing the image into the library and that used to fix it in 2017, but it doesn’t in 2019.

Thanks in advance for your help!

K

4 Comments
2018-11-03 09:28:07
2018-11-03 09:28:07

Can you check the exact version numbers you are using under Help, About Captivate?

Like
(3)
>
Lieve Weymeis
's comment
2018-11-09 17:17:53
2018-11-09 17:17:53
>
Lieve Weymeis
's comment

Hello Lieve,

It’s 2019 11.0.0.243

Like
(1)
>
sagem15836397
's comment
2018-11-09 18:24:25
2018-11-09 18:24:25
>
sagem15836397
's comment

Try to update (Help, Updates) to 11.0.1.266.

Like
>
Lieve Weymeis
's comment
2018-12-18 14:29:18
2018-12-18 14:29:18
>
Lieve Weymeis
's comment

Hello, Lieve. The update did not resolve the problem. Any other suggestion?

Like
Add Comment