https://bugs.documentfoundation.org/show_bug.cgi?id=165773

--- Comment #7 from Mark <[email protected]> ---
I am now using that exact version on my Windows 11 Pro 24H2 system

Version: 25.2.1.2 (X86_64) / LibreOffice Community
Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49
CPU threads: 8; OS: Windows 11 X86_64 (10.0 build 26100); UI render:
Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

With the calc (.ods) file I provided, I can easily reproduce the problem.

Just now I did this:
1- entered text in a few random fields
2- saved
3- clicked ctrl-z until the changes were all undone
4- saved
5- noticed that a few checkboxes LOOKED un-checked
6- scrolled down, then back up
7- saw that those checkboxes still LOOKED unchecked
8- clicked one of them, it still LOOKED un-checked
9- clicked it again, and it LOOKED checked 
10- This makes me believe they only LOOKED un-checked at both (5) and (7)  

Simply SCROLLING down, then back up can make checkboxes LOOK un-checked.

Sometimes they even LOOK un-checked when I first open the file.

I will get a screenshot and/or screen recording when I can.  No one else can
see this???

Recall that the checkboxes were all created by a macro I wrote, which is also
attached.  It sets them to have LOOK3D visual style (by default.)

DO the buttons you see in the .ods file I attached have that LOOK3D visual
style for you?  A blue square with slightly-rounded black borders and a white
checkmark over it when checked.  A simple white square with a black border when
un-checked.




ALSO - the problem I was seeing with selecting a few rows, then right-clicking
on one of the rows, then selecting "Insert rows below", and then not seeing any
checkboxes in those new rows seems to have changed.  Now I see rows much
farther down in the sheet with no checkboxes.  It used to be the actual
inserted rows that had no checkboxes.  Very weird.  Why would inserting new
rows there change rows farther down in the sheet?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to