When you begin a LibreOffice Writer session and launch the Insert Index Entry dialog box for the first time (Insert > Indexes and Tables > Index Entry...), it appears in a reasonably compact size. If you enter an unusually long Entry at some point, it auto-expands horizontally to perhaps two times the original width. Any subsequently opened Edit Index Entry dialog boxes open at that expanded width, as well. Thereafter, both the Insert Index Entry and Edit Index Entry dialog boxes remain suck at the expanded width for the rest of that document's editing session. They cannot be manually resized to a narrower width. This is only an issue because the indexing dialog boxes can interfere with seeing what is behind the in the document and the side panel. Since serious indexing work is not done on the fly but in dedicated indexing sessions, constantly closing and reopening the indexing dialog boxes is not a productive option. Being able to shrink the dialog box horizontally would at least make it less burdensome to drag them out of the way. I think I will also file a separate bug report / feature request proposing that the Insert Index Entry and Edit Index Entry dialog boxes be made iconizable, minimizable, or dockable (if one hasn't already been filed). If the fields in the dialog boxes were auto-expandable to accommodate multiple lines, I can see docking indexing dialogs as new panels in the side panel as a possibly elegant solution. I haven't thought it completely through, though. I would just like to be able to get the indexing dialog boxes "out of the way" without having to close and later re-open them. Dragging them off to the right so I can see the document, and then off to the left so I can see the side panel gets old fast...
I could not reproduce. Maybe we need an example document to test more reliably. How long is an unusually long entry? What type of entry does it have to be? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information/document. Win 7 Pro 64-bit, LibO Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale: fi_FI
Well, this is embarrassing. I can't reproduce it in a NEW document, either. In the document in which I discovered it, however, it is DEFINITELY still an issue: the indexing dialog boxes open and remain at around two and a half times their normal width and can't be resized narrower, so they are constantly "in the way." Unfortunately, that document is a proprietary manuscript that I'm not free to disseminate, so I can't post it as a sample or test document. I don't have the time right now to develop a complex sample document mimicking the one I had the problem in, so for now I'm going to have to leave this bug in NEEDINFO status. Besides, a different indexing bug I reported previously -- about unwanted entry and key field repopulation behavior when the Insert Index Entry dialog box loses and then regains focus -- is MUCH more serious and worthy of attention than this one. Oh, and to answer your question, "long" index entries would be where the "Entry" field contains the equivalent of two or even three ordinary sentences, punctuated with commas. I suspect, but haven't had time to confirm, that using semicolons (;) in the "Entry" field may cause Writer to crash (and render autosaved backups unrecoverable) after six or seven such index entries are made. I stopped using semicolons in index entries and haven't had any crashes during indexing since then. Thanks very much for having taken the time to follow up on this. I'm sorry it turned out to be idiosyncratic and apparently non-reproducible in an ordinary document. All the best.
This method to anonymize the document might work for you: https://wiki.documentfoundation.org/Anonymizing_a_document#Sanitize_file_text Note that a huge regular expression replacement task might take a while to complete.. or maybe even crash :)
It's a ~350,000-word manuscript, and I would also have to sanitize the contents of the index entries, rename a large number of custom character and paragraph styles, and replace or purge a bunch of information from document properties. It's just too much to contemplate (in addition to which my computer doesn't need a WHOLE lot of encouragement to overheat and shut down!). When I have more time to spare, I'll just do something like download a public-domain book from the Internet, import it into Writer, and start indexing it the way I've been doing in the manuscript. Again, I can live with this bug much more easily than I can with the other indexing bug I filed a report on, and if no one else has complained about it, there's really no harm in putting off the diagnosis. Again, I'm really grateful for your responsiveness. I'll post again ... eventually!
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team This NEEDINFO message was generated on: 2015-09-03
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO Message generated on: 2015-10-14
My apologies. I'm still using 4.4.5.2. x86, as a background-CPU-use bug in LO 5 overheats my system and prevents me from upgrading. I'm hopeful that that bug will be resolved in 5.0.3. I'm still experiencing the problem in a 440,000-word document with many long index entries, some of which contain semicolons. I'm not yet experiencing the problem in a 720,000-word document that I have only just begun to index and that does not yet have many long index entries nor (I believe) any (or many) index entries that contain semicolons. I have eliminated my user profile as a potential source of the problem by testing with a default user profile. The documents in question are still confidential, not practically anonymizable, and legally and professionally unshareable. When I can run a version of LibreOffice 5, I will attempt to reproduce the problem by indexing a copy of War and Peace, which is in the public domain. One additional thing I have noticed since filing my original report is that when I horizontally increase the width of default-sized Insert Index Entry dialog boxes, the text boxes they contain do not get wider but remain fixed at the original width. Only the blank space between the text boxes and the command buttons to their right gets wider, and when ample text is entered in the text boxes, they do not auto-expand to fill the blank space. This defeats the purpose of resizing. So, the resizing feature of Insert Index Entry dialog boxes is clearly buggy in some ways, at least in some versions of LibreOffice 4. If I continue to experience the problem in LibreOffice 5, I will hopefully be able to demonstrate this in a reproducible way in the near future.
Fair enough, let's set back to needinfo then.
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team This INVALID Message was generated on: 2016-05-09