https://bugs.documentfoundation.org/show_bug.cgi?id=108547
Bug ID: 108547
Summary: When moving to insert a new record, unbound controls
should not get cleared
Product: LibreOffice
Version: 5.3.3.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Base
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: bridgeportcontrac...@gmail.com
Created attachment 134042
--> https://bugs.documentfoundation.org/attachment.cgi?id=134042&action=edit
Example database to demonstrate the issue
Only bound fields should get cleared.
How to demonstrate:
1) Open the attached simple database, then open Form1 in Edit mode.
Notice that the list box is not bound to any field in the underlying table.
(Right click on the List Box control (the first control) and select Control...,
then select the Data tab, and verify that the Data field... is empty.)
2) Now switch out of design mode so you can watch this List Box's behavior.
Select any value in the List Box (either 1 or 2 in this example).
Currently there are only 2 records in the underlying table. So first move the
record pointer forward one step from ID=0 to ID=1 (using the right arrow in the
record navigator), and notice that the List Box value is not affected.
Also move the record pointer backwards from ID=1 to ID=0, and notice the List
Box value is again not affected.
But now move to a new record, either by moving forwards past ID=1, or by
clicking the new record navigator button.
Now even though the List Box is not bound to a record field, it gets cleared.
Now it would make sense if it got cleared if it was bound to a field, but it is
not bound. I don't think the List Box should get cleared.
___________________________________________
Sometimes it's very useful to have some controls on the screen that are not
bound to the underlying record and can be static or independent of the
underlying record data.
One example of such use would be a pull down to select or filter records using
macros. I use both of these. But the trouble is that when using the pull down
to filter the underlying records, the filter selector gets wiped out when
moving to a new record.
Why do I use a pull down to filter rather than a sub-form? Because in my
accounting form I want to be able to select a particular account, or all
accounts, and I don't think using sub-forms does this as well.
_____________
Tested both on HSQLDB 1.8 & MariaDB via MySQL/JDBC connection.
Linux
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
