Created attachment 114172 [details] File with the issue In the test file we have a table, a form, a grid in the form, that shows entries from the table. There is macro connected to form load event, that calls moveToInsertRow method. If list is longer than 40-50 entries, then it doesn't show the rest entries and moveToInsertRow moves the cursor to the last shown entry, but not to the insert row. That makes it almost useless. Was previously discussed there: http://ask.libreoffice.org/en/question/47478/adding-entries-to-a-long-grid/
Please tell us exact steps to reproduce the issue and what we should see and what is seen instead. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Could confirm the behavior. You have to enable macros to see this: Open the form. Cursor moves to something like row 60, but there are 81 rows. The macro should move the cursor to row 82 to insert a new row. This works right if you are not using a tablecontrol. Seems there is something like a cache-problem for the tablecontrol. If you are using textboxes instead it doesn't show the right number of the row, but does show the field "ID" with <AutoValue>. You could use the following workaround: Sub MoveToInsertRow(oEvent as Object) oEvent.Source.Last() oEvent.Source.moveToInsertRow() End Sub This works for all versions. Moves the cursor to the last row, then jumps to the new row and also shows the right number of the row. Have tested this with OpenSUSE 13.2 64bit and LO 4.3.5.2
** 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.0.5 or 5.1.2 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Bug also appears with LO 5.1.2.2 on OpenSUSE 64bit rpm Linux. Have tested older versions: LO 3.6.7 on OpenSUSE the same buggy result. LO 3.3.0 and 3.3.4 on OpenSUSE: all primary-key-fields of the tablecontrol will show <Auto Value> - so the bug couldn't be reproduced here because there is another buggy behavior. Will set this bug to inherited from OOo, because I couldn't find any version before which will work right in this case.
** 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.2.7 or 5.3.3 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Bug still appears with LO 6.1.5.2 on kUBUNTU 18.04 64bit.
Dear senya, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Tested with actual MANJARO-KDE LibreOffice Version: 7.0.5.2 Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a CPU threads: 16; OS: Linux 5.10; UI render: default; VCL: kf5 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded It's still the same issue: Open the database from Senya, allow macros. Open the form which should show a new line for a new record based on the macro. It shows record 47 but more than 80 records are in the source. E.g.: Same behavior as Robert has described in #4.
Confirming also with Version: 7.1.2.2 / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded
@Lionel : guessing that this has something to do with the way the UI displays a cached subset of the resultset which doesn't get refreshed ?
There are two moveToInsertRow() in the API. com::sun::star::sdbc::XResultSetUpdate::moveToInsertRow() or com::sun::star::form::runtime::FormFeature::MoveToInsertRow() My guess is about the latter. (In reply to Alex Thurgood from comment #10) > @Lionel : guessing that this has something to do with the way the UI > displays a cached subset of the resultset which doesn't get refreshed ? My guess is more that it is linked to the lazy loading of rows (when the UI displays a "*" next to the number of rows to say that not all rows are loaded yet). In that case, it can probably be worked around by: moveToLast() to force loading of all rows, then only moveToInsertRow()