Skip to main content
W
wmsgva
Inspiring
September 26, 2018
Question

Multiple hide & show commands for images in groups doesn't work

  • September 26, 2018
  • 2 replies
  • 704 views

I have created a complex slide with several buttons which each trigger a different sequence (they use cpCmdGotoFrameAndResume to relaunch the movie header in the correct place). Overall it works very well despite its complexity.

The objects in the different sequences are originally hidden and then shown using an Advanced Action, depending on the button pressed. Some of these objects are in groups.

I have noticed that when one of the objects to show/hide is in a group, it will sometimes not be displayed after issuing a "Show" command for that group if the object is an image. The problem can be solved by using a shape with an image as a background instead of an image object.

Not sure where to report bugs in Captivate 2019 following the pre-release stage which I was involved in, but this clearly seems to be a bug.

One related topic is that of objects grouped in a responsive project not being treated as responsive, even if they all have the same start time and length (grouping makes it easier to address multiple objects in scripts). If someone from the Adobe Captivate team reads this, perhaps this is an improvement in a future release that would be welcomed.

    This topic has been closed for replies.

    2 replies

    Lilybiri
    Lilybiri
    Brainiac
    September 26, 2018

    I never did see this problem myself, and I am using a lot of Advanced actoins with and without groups.

    In responsive projects with the fluid boxes workflow groups should never be used.

    W
    wmsgvaAuthor
    Inspiring
    September 26, 2018

    Lilybiri​ This is what I was hinting at in the last part of my post.

    Adobe should correct this in Captivate and make it possible to use groups in responsive fluid boxes to group objects that all share the same time parameters (length and start). It makes your life so much easier if you need to address many objects in a script (just address the group).

    W
    wmsgvaAuthor
    Inspiring
    September 26, 2018

    You can HOPE all you like about what you want Adobe to do, but if you want any chance that they will even look at it, then you (and lots of other users) need to be logging enhancement requests for such a feature.

    As far as Captivate viewing objects as groups, this might be more difficult than you think.  As a similar issue, although you can group objects on a slide in Captivate's EDIT mode, and use HIDE SHOW actions applied to the group, the fact is that these items are not actually grouped in the underlying code at all.  Captivate still has to individually hide and show all of the same original objects.  Using grouping in the UI is just hiding the underlying complexity from you the user.  I suspect that groups in responsive design will be done similarly.


    Rod, I agree with your comment regarding feedback, but could you specify where users are to log such requests? It was easy during the pre-release period as a member of the test team to do so, but not sure now that this phase is over.

    Similar question: where does Adobe provide a roadmap for upcoming features in Captivate?

    As far as coding is concerned, I did expect the objects not to be grouped in the underlying code, which in fact should make it easier to ignore the groups when dealing with displaying the objects within a group in a fluid box and only use it when interpreting the advanced actions.

    TLCMediaDesign
    TLCMediaDesign
    Inspiring
    September 26, 2018

    I have a feeling that it is related to you jumping frames. Never seen that type of behavior.

    W
    wmsgvaAuthor
    Inspiring
    September 26, 2018

    Don't think it has to do with jumping frames, as all I'm doing is returning to just after the position in the movie in which the different buttons pause (to play thereafter, with the objects shown/hidden according to the button the learner pressed).

    It works fine after using shapes with image backgrounds instead of image objects, so I don't think that's the issue. I tend to think, as I hinted and Lilybiri suggested, that the problem is related to using grouped objects in responsive fluid boxes.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices