Just released a new version of WidgetFactory that will work with Captivate 6.1. Currently any widgets built with WidgetFactory build with a version under 6.1 will not work with Captivate, so make sure you update your widgets.
A couple of changes have come in with Captivate 6.1 which will cause issues with some widgets. For one, most slide objects now have mouseEnabled and mouseChildren turned off. This means that if you’ve attached a CLICK mouse event to one, then no matter how much you click it the event won’t dispatch. To get around this, WidgetFactory’s getSlideObjectByName() method now turns on the mouseEnabled and mouseChildren properties before returning you the slide object. However, there will probably be various issues with this to come. For example, if at runtime you’ve got a button INSIDE your widget that you want the audience to press, that won’t work out of the box in CP 6.1, because the widget itself has had its mouseEnabled and mouseChildren properties turned off. You’ll have to cycle up the widget’s parents and make sure those two properties are set to true on each parent.
There is currently a known issue with Captivate 6.1 to do with Interactive Widgets. If you place an interactive widget on the first frame of a slide, then everything is fine. However, if you move it off that frame to… say frame 30, then the Interactive Widget will NOT pause the movie, and it will NOT report success or failure. All the code in the widget runs fine, there just seems to be some bug in Captivate that stops this happening. There’s not really anything we can do about it on the Widget developer end, so if you get inquiries about this, just tell the customer that for the moment they’ll have to start the interactive widget from the first frame of the slide. Here’s hoping there’s a patch coming out for this soon.
Aside from that, getSlideObjectByName() will now return objects that have been ‘displayed for rest of project’; which is a nice overdue feature. There are also some bug fixes, mostly fixing some issues widgets had with Question Pools.
Hopefully this will clear your collective headache of all the 6.1 customers sending you e-mails saying: It don’t work!