Skip to main content
rynotrain
rynotrain
Known Participant
February 15, 2017
Question

Going Vertical 2

  • February 15, 2017
  • 1 reply
  • 241 views

Even thought this:  https://elearning.adobe.com/discussion/1610490/?query=Vertical was posted in 2014, it's more relevant than ever.  I won't bore you with use cases, but Cp users are constrained with the # of vertical pixels we're able to design in.  In responsive project, if I adjust view to 25% or Best Fit, break the device height and slide height, call device height, say 700, and slide height 5000 (which is the max), you can only see about 2800 vertical pixels of the slide, and are unable to get to the remaining +/- 2200 vertical pixels to design in.  Essentially the vertical scroll bar in Cp is not visible.  We need a hot fix for this.  It is constraining designers who, like me, are jumping away from the Cp ship to explore other tools.  We need to solve this without transitions, click boxes, or other Cp elements that take a user to 'another slide.'  I might as well put the lame next button.  Isn't there an application file in the local install that could be changed or manipulated to expand the 'container.' - Ryan

This topic has been closed for replies.

1 reply

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
February 16, 2017

Ryan,

You're welcome to submit a Feature Request / Bug Report for this if you really feel strongly about it. 

But my gut feeling is that Adobe is more focused on keeping Captivate as a slide-based application, and I'd have to say I agree with that decision.

If you had all of your content on one huge single vertically scrolling slide, it would just limit you in other ways. For example, it would mean you only had one On Slide Enter event to trigger actions with.  I personally prefer having one of these events available each time I enter a new slide.

Captivate may not be everything you want, and you are certainly free to move to another tool if you find one that suits you better, but I think realistically Captivate still does so many things well that it's worth sticking with it.

rynotrain
rynotrainAuthor
Known Participant
February 16, 2017

Totally agree, understand what I'd lose with a single slide. On that note, one enhancement would be to allow xAPI statements to apply to a single element rather than a slide (whole different issue). I think what's disturbing me is that my max vertical slide height in responsive mode is really 5000px but I can only see a bit over 2800px with 'best fit' view selected (which is really about 10% view). I know there is another 2000 px down below (I see this by moving device height down to as far as my screen(s) will go. The scroll bar is completely gone so can't go down to take advantage of designing the remaining 2200px. So if it's intended to go 5000 but designer can't get there, that to me is a foundational miss, enhancement request, and really should be patch fixed. Slider just needs to be shown ya know. I love Cp, just missing that flexibility, reporting xAPI and single elements within a slide, and of course slide transitions (which they haven't enhanced in years). Even if they had a fly up slide transition, we could at least get closer to a vertical scroll.

On another note, since I'm stuck with 2800px, if I wanted to put a menu at top with links to particular elements on that slide, is there a resource you could point me to to accomplish that? Not sure if that's possible either. Keep trying to stretch Cp I guess. Thanks for talking this out with me! Ryan

Sent from Ryan's iPhone

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