Bug 118598 - BASE form navigation toolbar record count not displayed correctly
Summary: BASE form navigation toolbar record count not displayed correctly
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.4.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-06 22:53 UTC by Andrew Richardson
Modified: 2019-05-15 09:34 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot showing overwrite issue (169.50 KB, image/png)
2018-07-06 22:53 UTC, Andrew Richardson
Details
example (14.31 KB, application/vnd.oasis.opendocument.database)
2018-07-08 14:29 UTC, Drew Jensen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Richardson 2018-07-06 22:53:45 UTC
Created attachment 143371 [details]
Screenshot showing overwrite issue

When a form has a subform (based on two recordsets), moving cursor between the parent & child records results in the navigation toolbar max record count updating but the new value overwrites the previous value.  User cannot read the new max value as a result.  
Previous value should be cleared, and then new value written to ensure overwrite does not happen.
Comment 1 Drew Jensen 2018-07-08 14:28:04 UTC
I can confirm this behavior with 5.4.7.2 and 6.0.5.2.

It seems to have gone away with 6.1RC1 and 6.2Alpha0

So, I'll set it to new and maybe if there is a 6.0.6 the fix could be backported.
Comment 2 Drew Jensen 2018-07-08 14:29:21 UTC
Created attachment 143390 [details]
example

This is as good an example of it as any, single form. Just open it and move the cursor focus between the main form controls and the sub-form grid control a few times.
Comment 3 Xisco Faulí 2018-07-09 13:58:09 UTC
(In reply to Drew Jensen from comment #1)
> I can confirm this behavior with 5.4.7.2 and 6.0.5.2.
> 
> It seems to have gone away with 6.1RC1 and 6.2Alpha0
> 
> So, I'll set it to new and maybe if there is a 6.0.6 the fix could be
> backported.

Indeed, it's fixed in

Version: 6.2.0.0.alpha0+
Build ID: 67f3063b7c334d4d5c59132d90b938671aad09f0
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded

Closing as RESOLVED WORKSFORME and adding the whiteboard 'backportRequest'