BIG BUG: Scrolling And Diagramming

When I am using the diagramming tool, if I scroll down to read or diagram text outside of the initial screen view, my cursor no longer lines up with what is being dragged, selected, or highlighted within the diagram — rendering the tool useless for creating a diagram that is larger than a single screen view. Is there any quick fix for this? I have to finish this diagram for class by the end of the day.

Thanks!

Find more posts tagged with

Comments

Keep Smiling 4 Jesus :)

Concur - can scroll down diagram, but trying to drag words in middle now selects all text - side bars turn green (instead on being blue). If first line of sentence diagram not visible in panel, cursor selection does not line up with text (appears to be vertically off by amount of diagram scrolling).

Couple workaround [I]

1) Insert passage - right click - zoom out (tiny text) - diagram from bottom to top

2) Split passage into several diagrams

Keep Smiling [:)]

Tom Philpot (Faithlife)

When I am using the diagramming tool, if I scroll down to read or diagram text outside of the initial screen view, my cursor no longer lines up with what is being dragged, selected, or highlighted within the diagram — rendering the tool useless for creating a diagram that is larger than a single screen view. Is there any quick fix for this? I have to finish this diagram for class by the end of the day.

Thanks!

Unfortunately, I doubt there is a quick fix this problem other than the suggestions KS4J proposed. Fortunately, it's easy enough to reproduce and should be easy to fix.

Jack Caviness

When I am using the diagramming tool, if I scroll down to read or diagram text outside of the initial screen view, my cursor no longer lines up with what is being dragged, selected, or highlighted within the diagram

Additionally, diagrams that were created in either L4 Win or an earlier L4 Mac Beta that are longer than a single screen lose portions of the bottom of the diagram. Checking the diagram in L4 Win reveals that everything is still in place and that this is a display problem in Beta 5.