I don't think it is meant to work like you assume. It is logical to number them by order of creation.

I don't know how it would deduce the order in the document.
Do you mean it should be an option, when the frame is anchored to paragraph that it would determine its relative position in the order of paragraphs?

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.

Created attachment 124897 [details]
para numbering via frames

I've attached an example with lipsum text.

I anchored the frames to the paragraphs.

In Frames, I used the style "frame contents". I activated outline & numbering under "frame contents". 

The frames anchored to the paragraphs written/inserted lately are not numbered in document/text order. In order to correct the numbering, I disable the outline & numbering under paragraph style and reenable it; however the frames still get the numbering in creation order/time.

As far as I can see there is another logic behind the numbering frames by using styles. With this way, you get the ordering reflecting creation time of each frame.

I have achieved the numbering/ordering corresponding to vertical placement of the paragraphs/frames in the documents by using increment fields.

Please attach the original document. The pdf does not allow to investigate, what settings are actually used.

There exist several kind of numbering: Paragraph outline numbering, body text lists, number ranges, line numbers. It is not clear, what you are using and what object actually gets a number.

The frames anchored to the paragraphs get number.

If I use list numbering in the frames, the frames are numbered according to their creation order.

If I use number ranges in the frames, the frames are numbered according to their vertical placement in the document.

can you please post a test file?

Created attachment 125358 [details]
list number

Created attachment 125359 [details]
fields - number range

(In reply to Hakan from comment #9)
> (In reply to Cor Nouws from comment #6)
> > can you please post a test file?
> 
> I have attached two examples.

Now, I have found out: If you save, close and reopen the document, the list numbering also gets the right order. That is why the documents I attached are not helpful what I want to say. I am attaching a new screenshot which shows the wrong ordering by using list numbering in the frames via style "frame contents"

Created attachment 125360 [details]
screenshot

Hi Hakan,

(In reply to Hakan from comment #0)
> Numbering frames and marginalias via "paragraph style: Frame contents" does
> not function properly.
> 
> First, the numbering confuses when I insert a new frame in between old
> frames. The new frame in between gets the highest/last number even though it
> is somewhere in the middle.

I opened your file "fields - number range.odt"
The frames in the margins contain a numbering field.
When I copy a frame and paste it at a different position, the numbering of all fields gets updated immediately.
So I cannot reproduce this.
(libreOffice Daily20160525 / 5.1.3.2; Ubuntu 32 bits)

> Secondly, "paragraph style: Frame contents" starts not the respond to
> amendments. I remove "numbering" under "outline & numbering" tab, however
> nothing changes. The frames still contain wrong numbers.

I opened your file "list number.odt"
The text in the frames in the margins have the paragraph style Frame Contents and that style has numbering level 3 applied.

When I copy a frame and paste it at a different position, the numbering of all paragraphs does not get updated immediately.
So I can reproduce this. 
After closing and reopening the numbering is fine.
(libreOffice Daily20160525 / 5.1.3.2 / 3.3.0; Ubuntu 32 bits)

So I would suggest to change the summary of this issue:
"Paragraph numbering in frames not updated immediately after inserting a new frame" or something..

Does that sound OK?

yes, this sounds well.

Thanks.

Dear Hakan,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug