<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Occasionally, LO Calc loses blocks of comments." href="https://bugs.documentfoundation.org/show_bug.cgi?id=118740#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Occasionally, LO Calc loses blocks of comments." href="https://bugs.documentfoundation.org/show_bug.cgi?id=118740">bug 118740</a> from <a class="email" href="mailto:georgera@gvtc.com" title="George <georgera@gvtc.com>"> George</a> <pre>(In reply to Buovjaga from <a href="show_bug.cgi?id=118740#c5">comment #5</a>) > (In reply to George from <a href="show_bug.cgi?id=118740#c4">comment #4</a>) > > (In reply to Buovjaga from <a href="show_bug.cgi?id=118740#c3">comment #3</a>) > > > In essence, do you mean that you have worked with the file, saved, but not > > > closed and reopened. Then, after the shut down / restart cycle, you notice > > > the comments were lost? > > > So basically, you should be able to reproduce it without any lengthy "shut > > > down, go to sleep, start the next day" -cycle by just doing File - Reload > > > after saving. > > > > Today, I tried out your suggestion. I saved the file, made a change in one > > cell (so I could see if it actually reloads to file) and then attempted to > > reload the file. Apparently it doesn't reload if the file is already there. > > No, it does reload, if the file is already there. That is the sole purpose > of the reload functionality. With reload, we are able to quickly see for > example, if saving to some Microsoft format caused unwanted changes. It is a > shortcut for closing and reopening a file. > > > I really do not have time to test over and over using different techniques > > to replicate this problem and I do NOT wish to have this occur again. When I > > lose the comments, it really messes up what I am doing. I keep notes on the > > progress of the clocks throughout the day and night so I can see what they > > are doing each hour. This keeps the display much simpler when it only > > showing the results twice a day. The in between times are in those comments. > > When I lose those comments, I have much less information to refer to if a > > problem occurs. > > Quite frankly, I have no idea how this stuff works. I just use the > > spreadsheet as it is and expect it to work properly. When it doesn't, I do > > try to gather the circumstance and report it so you folks can attempt to > > work it out so it won't do that. > > Us folks are fellow users trying to figure out a way to reproduce the > problem, so developers can step in eventually. We suffer from the same lack > of time as yourself, so it is sort of a balancing act. > > I tried adding one comment, saving and reloading, but the comment did not > vanish. > > Arch Linux 64-bit > Version: 6.1.0.3 > Build ID: 6.1.0-2 > CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; > Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded this morning, I loaded up the 'puter and LO Calc. This was VERY close to 7am and I barely caught the clock chimes. When I got to the "Banjo", I notice the comments were missing from last night. So I finally got a chance to make a test by using "File/Reload" before the "Auto save kicked in and before I had time to "Save" the file as I usually do. What I got after "Reload" was exactly the same thing. So, it wasn't a failure AFTER I loaded the file, before auto save and before I manually saved it, it loaded without the comments again using "Reload". This indicates it was lost when I saved it last night. It always happened this way before but, I had no definitive proof until now. Since this so intermittent, I have no idea how you folks are going to find the time to have this happen to YOU. It took a few days until this happened to me. It's aggravating to me and I hate it. If we can't find a fix for this and several other problems with the comment section, I will be forced to begin trying alternative solutions such as other spreadsheet programs. So now, I can move on to report other problems with the "Comment" boxes. It seems almost all the bugs I'm experiencing are in the comment boxes.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>