Bug 87145 - Writers - Forms - Activation sequence nr
Summary: Writers - Forms - Activation sequence nr
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: high enhancement
Assignee: Not Assigned
Depends on:
Reported: 2014-12-09 09:23 UTC by Michel VERET
Modified: 2015-09-04 03:01 UTC (History)
0 users

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Michel VERET 2014-12-09 09:23:09 UTC

I'm using a large document with different controls (check box, text fields and radio button)

Into the "form navigator" (navigateur de formulaire in French), the controls are shown in the creation order.

Q1 : is it possible to show the fields ordered by the "activation sequence" (séquence d'activation in french)

While using the button "activation order" (séquence d'activation in French) in the toolbar "Ebauche de formulaire in French" (Form design ?), you can see the list of all the controls in your form. Your can choose "Automatic sort" or move the controls by hand ("with the mouse"). If you have a large number of controls, they are not all shown. You have to change the activation sequence number into the filed properties to find it.
You can select one or more field with the mouse by clicking and handle the key Shift (select between first and last clic) or Control (select only the lines "clicked"). But you can't move all the block selected by this way. Only one line is moved.
Q2 : is it possible to move a bloc of items selected into the window "activation order". Into the properties of the field, the activation sequence number is not changed. You have to change it manually.

I save the document into a pdf file (direct export to pdf file). After exporting the fields from the pdf file, the fields are not shown by activation sequence number. It seems they are ordered by the creation order...
Q3 : is it possible to have a pdf file with the fields in the "good order".

I use Libreoffice release (windows 8.1 pro 64).

Comment 1 Björn Michaelsen 2014-12-12 01:48:48 UTC
Seems like an enhancement request => ENHANCEMENT, not clearly speced on what is exactly needed (see https://wiki.documentfoundation.org/QA/BugReport) -- putting in NEEDINFO for now until independently confirmed.
Comment 2 QA Administrators 2015-07-18 17:36:00 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

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

Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 3 QA Administrators 2015-09-04 03:01:21 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03