Created attachment 168002 [details] File to show the bug Hello, Properties of defined fields are changed - Integer changed to float - text fields defined multiline changed to singleline I joined a file to show the bug I compare it to the build on 29/11/2020 Thanks UBUNTU 20.04 LTS Gnome 3.36
Same bug in the last build (10/12/2020)
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 168090 [details] Sample file for testing purpose (In reply to Xisco Faulí from comment #2) > Thank you for reporting the bug. Please attach a sample document, as this > makes it easier for us to verify the bug. > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' once the requested document is provided. > (Please note that the attachment will be public, remove any sensitive > information before attaching it. > See > https://wiki.documentfoundation.org/QA/ > FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help > on how to do so.) Thanks for your reply. As requested, here sample file to enable you to test the bug. BS
Hello, It seems to me that this bug has been, somehow, forgotten. May be that in the next days, someone will try to see for it. Thanks for your work BS
Description of this bug is a little bit confusing. I will try: Execute the form of the attached database file. Field "id" in the table control will be shown with 2 decimal places. Open the form for editing. Right mouse click on the header of the table "id" → chose "Column". Set in properties "Decimal accuracy" - 0. Close the dialog (there is no button for save - it should be saved automatically). Save the form. Execute the form. … and again there are 2 decimal places. Same behavior for a textbox, which isn't part of the table control. Changing to multi line will be shown, also it will be shown when directly reopening the properties for such a field, but it won't be saved in the form. Tested all this daily build from 2021-04-01, LO 7.2.0.0 alpha0+ with VCL:kf5 on OpenSUSE 15.2 64bit rpm Linux.
This buggy behavior doesn't appear in Versions like LO 7.0.4.2 or LO 7.1.0.1. So it's a regression.
(In reply to Robert Großkopf from comment #6) > This buggy behavior doesn't appear in Versions like LO 7.0.4.2 or LO > 7.1.0.1. So it's a regression. Hello, I noticed the bug since the version just after the 7.2 alpha build dated 29th november 2020. (Page 2 in the 1st attached file) Thanks for looking for a patch BS
(In reply to surbun from comment #7) > Hello, > > I noticed the bug since the version just after the 7.2 alpha build dated > 29th november 2020. (Page 2 in the 1st attached file) > > Thanks for looking for a patch > > BS Why did you set this bug to UNCONFIRMED? I have confirmed it an then it has to be set to NEW, so other people could see: Here is a bug with a regression. Let us have a look witch part of code is the code, which changed LO to produce this bug. Have set it back to NEW
(In reply to Robert Großkopf from comment #8) > (In reply to surbun from comment #7) > > Hello, > > > > I noticed the bug since the version just after the 7.2 alpha build dated > > 29th november 2020. (Page 2 in the 1st attached file) > > > > Thanks for looking for a patch > > > > BS > > Why did you set this bug to UNCONFIRMED? I have confirmed it an then it has > to be set to NEW, so other people could see: Here is a bug with a > regression. Let us have a look witch part of code is the code, which changed > LO to produce this bug. > > Have set it back to NEW It was tagged as "unconfirmed". I wanted to change it to "confirmed" & I noticed that there's nothing corresponding to this tag. So I let it unchanged (unconfirmed) Thanks for changing it to the right tag. BS
Hello, I tried the dailybuild of the 10th and noticed that the bug is still there. May be there's someone who can have a look to the codelines. Thanks for your work BS
Hello, It seems that the bug is no more there. Thanks a lot for your work BS
Have tested it also with daily build from 2021-04-04. Seems the bug is gone. I will set this one to WORKSFORME.