Created attachment 115988 [details]
Description with screenshots - different (wrong) rowcount-values
Open the attached *.pdf-description. It shows the whole problem.
The example shows a form with row 3 of a table. Changing one value in one formcontrol and switching to another resets the value of rowcount to '1' in the toolbar-navigationbar (Bug82591). At the same time the value of rowcount is switched to '0' in the formcontrol-navigationbar.
If you read out oForm.getRow() it will give the value '0' - the same wron value as you see in the formcontrol-navigationbar.
Seems to be inherited from OOo as Bug82591.
Created attachment 115990 [details]
Database with one form - try to change any value in second or third row an move to another field ...
This is the database, which shows the buggy behavior on OpenSUSE 13.2 64bit rpm Linux with all LO-versions here.
You could ignore the macros - it's only for trying to get a workaround for this buggy behavior ...
Build ID: 8cbb94a2b79dcaf9675125da800b64a85bae52dc
Locale : fr-FR (fr.UTF-8)
DUP of bug 82591 ?
(In reply to Alex Thurgood from comment #3)
> DUP of bug 82591 ?
No. This bug is about the different values. The formcontrol-navigationbar shows the row you could also get by a macro. The navigationbar of the toolbar shows '1' instead of '0'.
Bug82591 is about the wrong value, which should be the value of the shown row (row 3 for the third row), not '0' or '1' when changing a value in one field and click in another.
Both navigationbars should never show different rows, if cursor is in a field of the same form.
I tried to play with forms/source/solar/control/navtoolbar.cxx
but I'm stuck.
Sorry, I can't help here.
It is probably fixed by the same commit as bug 82591.
** Please read this message in its entirety before responding **
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 on a currently supported version of LibreOffice
(5.1.5 or 5.2.1 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System
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)
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: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Have tested again. It is fixed by the same commit as bug 82591 since LO 5.0. See comment 6.