-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leaving pages unstructured needs always a retry of the moving action in the structure tree #3476
Comments
Thanks for the very specific and useful problem description 😝 If I understand you correctly, the missing option Given the current - probably insufficient - options to add new elements at specific locations, the re-numbering of the pages assigned to the newly created structural element seems correct, though. Since the The actual bug in this issue seems to be the two tries required to succesfully move the created structural element. Is that correct? |
Sorry for my next mismatch in writing tickets -I tried to fulfill your requirement for a complete view for a problem. |
It looks like this is partly the problem described in #4038. @subhhwendt, what is shown in the structure tree, is not the pagination, but an internal command number. That is confusing. That's what I described in the other ticket. (In your example, the pagination is " A second (and independent) problem, if I understand correctly, is that the newly created division appears just below the parent node, and the unassigned images with a smaller number after it; they should appear before it. There shouldn't be a new function for this, it should always happen that way. Wrong: (the numbers here indicate the image number, assuming #4038 is fixed)
Correct:
Goal: I would suggest focusing this ticket on the second problem and solving the numbering display problem with the other ticket. |
@subhhwendt Can you confirm that the actual bug reported in this issue - e.g. two drag'n'drop actions are required to move a new structure element - still occurs? I just tested this with the current master and the structure element - including its assigned pages - was successfully moved on the first try. |
I confirm - there's no bug!! |
Step 1
Result makes unhappy regarding page numbering…..
Step 2: You can correct in the structure tree!
First try fails
Second try is ok - and it remains ok after saving the process
The text was updated successfully, but these errors were encountered: