Daniel Dekany wrote:
> XXE 4.1, editing a DocBook book.
>
> I'm using "Document structure" view for quickly move in large
> documents. However, I have not enough space on a 1280x1024 screen to
> keep it visible, as I do this:
>
> <windowLayout>
> <center css="DocBook" />
> <bottom css="Document structure" size="0.001" />
> </windowLayout>
>
> Whenever the ToC is needed, I resize the bottom view to bigger with
> the mouse, click on the desired title in it, and the drag it back to
> it's minimum size. (Yeah, lame enough... I hope I will find it's
> possible to assign these operations to keyboard short-cuts. But
> ideally the bottom view should also be automatically minimized when I
> click on a title.)
>
> The bug: When I click on a title in the structure view, the cursor
> jumps to the correct position in views; so far so good. But when I try
> to decrease the height of the bottom view, the cursor suddenly jumps
> away to some apparently random place (several "pages" away from where
> it should be), hence spoiling the whole navigation thing. This doesn't
> occur if I only do a little resizing, but any serious height change
> will trigger this. Interestingly, when I select the title in the
> structure view (for example with double clicking), the cursor will not
> jump away. So maybe it's trivial to fix.
>
We currently don't see how this problem could be fixed.
Workaround (tested with v4.2alpha3, which is very different from v4.1 in
terms of synchronization of the views -- see below):
[1] Increase the size of the document structure view.
[2] Click in the document structure view to specify the document region
of interest.
This makes the document structure view, the ``master view''.
* The master view is the view which has the keyboard focus.
* The caret of the master view is always kept visible. (This is the
cause of your problem)
* The caret position of the master view determines the scrolling
position of the other views.
[3] Click in the styled view to make it the master view. (This step is
critical to solve your problem.)
[4] Decrease the size of the document structure view.
> Oh, and bug 2: If I switch the CSS within the same view (like
> back-and-forth between DocBook and Document Structure views), I also
> lose the cursor position, find myself elsewhere where I wanted to get
> to. So it's not good for navigation either. I'm actually quite
> surprised on that, as I believed that's the intended way of
> navigation, only it's far too slow for me (document not small enough),
> while I had no performance problems with two parallel views.
>
I cannot reproduce this problem with our current development version
(v4.2alpha3). Note that a customer, Philippe Nobili, has already
reported a *severe* bug related to the synchronization of the views
(this bug is present only in v4.1), so may be the bug fix has also
removed this problem.
> Actually, how do you guys navigate when using your own product? Do I
> miss something?
Personally, I use a single view: the styled view. When I open a large
document, I immediately press Esc 1, then navigate and make changes in
the collapsed document.
---
<binding>
<keyPressed code="ESCAPE" />
<charTyped char="1" />
<command name="toggleCollapsed" parameter="collapseAll+expand" />
</binding>
---
>
> (BTW, it would like to note again that it would be good if XXE
> provides a *convenient* and fast ToC navigation view out-of-the-box
> (i.e., without the user digging himself into the topic of writing
> custom configurations, if it's possible to achieve it that way at
> all). Think about potential users downloading your stuff for a trial;
> I would think that you often fall under too fast, as efficient
> navigation is on the checklist of many, I'm certain. Isn't that a low
> hanging fruit for you? I mean, almost everything is on place for that,
> so... why not?)
>
Thank you for the bug report and for this feedback.
