Mentions of bugs in the dev guide

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The dev guide references some known issues (without bug numbers). I appreciate any help in figuring out if they are still relevant.

https://wiki.documentfoundation.org/Documentation/DevGuide/LibreOffice_Basic#Date_Field
Dropdown is currently not working by program, but you can set it with the Control Properties in the IDE.

https://wiki.documentfoundation.org/Documentation/DevGuide/LibreOffice_Basic#File_Control
The directory must be given as a system path, file URLs do not work at the moment.

https://wiki.documentfoundation.org/Documentation/DevGuide/LibreOffice_Basic#Time_Field
Short time format is currently not working.

https://wiki.documentfoundation.org/Documentation/DevGuide/Drawing_Documents_and_Presentation_Documents#Filter_Options
XMimeTypeInfo is currently not supported by the GraphicExportFilter.

https://wiki.documentfoundation.org/Documentation/DevGuide/Drawing_Documents_and_Presentation_Documents#Other_Drawing-Specific_View_Settings
The method setViewData() is currently not working. It can only be used with loadComponentFromURL().

https://wiki.documentfoundation.org/Documentation/DevGuide/Drawing_Documents_and_Presentation_Documents#Presentation_Settings
The properties IsShowAll, IsShowLogo and IsTransitionOnClick are currently not documented in the API reference.

https://wiki.documentfoundation.org/Documentation/DevGuide/Forms#Initializing_Bound_Controls
Or, you want to have real null values for date fields. This is currently not possible, because the com.sun.star.form.component.DateField service interprets a null default as an instruction to use the current system date. Effectively, you cannot have date fields in forms which default to null on new records, but you can get this by programming the API.

https://wiki.documentfoundation.org/Documentation/DevGuide/Forms#Parameters
If there are still parameter values left, the com.sun.star.form.XDatabaseParameterListeners are invoked. Any component can add itself as a listener using the com.sun.star.form.XDatabaseParameterBroadcaster interface implemented by the form. The listeners then have the chance to fill in anything still missing. Unfortunately, LibreOffice Basic scripts currently cannot follow the last step of this procedure - there is a known implementation issue which prevents this.

https://wiki.documentfoundation.org/Documentation/DevGuide/Office_Development#Implementing_a_Spell_Checker
The Context menu of the Writer that pops up when pressing the right-mouse button over an incorrectly spelled word currently has a bug that may crash the program when the Java implementation of a spell checker is used. The spell check dialog is functioning.

https://wiki.documentfoundation.org/Documentation/DevGuide/Office_Development#Using_the_Desktop
As long as the Windows quickstarter is active, the soffice executable is not terminated.

The office freezes when terminate() is called if there are unsaved changes. As a workaround set all documents into an unmodified state through their com.sun.star.util.XModifiable interface or store them using com.sun.star.frame.XStorable.

The object returned by getFrames() does not support XTypeProvider, therefore it cannot be used with LibreOffice Basic.

https://wiki.documentfoundation.org/Documentation/DevGuide/Text_Documents#Auto_Text
The current implementation forces the user to close the AutoTextEntry instance when they are changed, so that the changes can take effect. However, the new AutoText is not written to disk until the destructor of the AutoTextEntry instance inside the writer is called. When this example has finished executing, the file on disk correctly contains the complete text "This string was inserted using the API!\n\nSome text for a new autotext block", but there is no way in Java to call the destructor. It is not clear when the garbage collector deletes the object and writes the modifications to disk.

https://wiki.documentfoundation.org/Documentation/DevGuide/Text_Documents#Redline
Calling XPropertySet.getPropertySetInfo() on a redline property set crashes the office.

https://wiki.documentfoundation.org/Documentation/DevGuide/Text_Documents#TextView
In StarOffice 6.0 and OpenOffice.org 1.0 you can only influence the zoom factor by setting the ZoomType to BY_VALUE and adjusting ZoomValue explicitly. The other zoom types have no effect.

https://wiki.documentfoundation.org/Documentation/DevGuide/Text_Documents#Text_Frames
The API reference does not know the properties above. Instead, it specifies a com.sun.star.text.ChainedTextFrame with an XChainable interface, but this is not yet supported by text frames.

Ilmari



[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux