Description: The getCount() function returns one number, the Item() function accepts either a string index (which can take more values than what getCount() returned) or a number, but only the numeric index 1 works. These three things should all be consistent. getCount() should return a number that corresponds to the number of different strings that will work as arguments to Item(), and Item() should also accept any numeric index from 1 to that number. Steps to Reproduce: (I don't expect anybody else than myself to be interested in this bug, I mostly file it for work hour tracking purposes. QA, please don't bother looking any closer at this.) Actual Results: . Expected Results: . Reproducible: Always User Profile Reset: No Additional Info: .
And then there are the hasMoreElements() and nextElement() member functions (for the XEnumeration base class) that form yet another inconsistent implementation of enumeration functionality.
The plot thickens. When I try to run the customer application under a fresh COLEAT and against a LibreOffice with the recent CommandBars fixes, it crashes. Probably because COLEAT so far isn't built to have proxies for CommandBars. Now, the CommandBars interface is declared in the type library in MSO.DLL. So far I haven't passed that to genproxy when building COLEAT. If I do that, and add Office.CommandBars and Office._CommandBars to samples/mso.interfaces.list, I run into the "Huh, IDispatch-based interface has different number of functions than the Vtbl-based?" error when running genproxy. Presumably this is caused by the fact that the _CommandBars interface is derived from the _IMsoDispObj interface and not directly from the IDispatch interface. COLEAT currently only handles interfaces that are directly derived from IDispatch. So some more work on that is needed in COLEAT.
More notes, saving them here so they aren't forgotten: The CommandBars property in various Word interfaces (_Application is the relevant one in the customer application's case) returns an object of type CommandBars. That is an interface that is not defined in the Word type library (MSWORD.OLB), but in the common MSO type library (in MSO.DLL). This probably is a complication that COLEAT doesn't handle properly.
Tor Lillqvist committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/50ffab5ff0b17add475c3199cd889196d4af2ce2%5E%21 tdf#123819: Revert "Use comphelper::getProcessComponentContext()" It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Tor, is this bug fixed?
No.
Dear Tor Lillqvist, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.
Dear Tor Lillqvist, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
COLEAT is dead since several years.