…hyper-step – inconsistency?…

OS_CE Forums Octopus Support …hyper-step – inconsistency?…

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #1054
    Chris Henkel

    …page 109 – parapgraph Engaging hypersteps states, that A track can only have one associated hyperstep

    …while this is the way it actually works, it’s nevertheless possible to copy an active hyperstep in step-view and paste it again…

    …this leads to a hyperstep-indication in page-view, without hyperstep-functionality; furthermore, the pseudo-hyperstep cannot be deleted like the real hyperstep…the only way i found was to assign that step as real-hyperstep and delete it as described…

    …btw.: is it planned to allow more than one hyperstep to a track?…like a hypertrack? B)

    Gabriel Seher

    Hi – I was able to replicate the error you describe in the step copy procedure and solved it in the latest version of the source by not copying the hyper status of the source step to the target step.

    One could argue that the hyper status should be taken over by the target and removed from the source, but regardless, a consistency check needs to be in place, so much is sure.

    In terms of allowing more than one hyperstep to a track, that would involve a major change to the internal structures, is therefore not feasible in the short term.



Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.