https://bugs.documentfoundation.org/show_bug.cgi?id=152619
Wolfgang Jäger <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Wolfgang Jäger <[email protected]> --- Create a new TextDocument (you may leave the text empty). Just to keep testing separate from different macros: Create a new Basic module in the Standard library of the new Document. (The issue also occurs if the code is executed from a module in the application's library.) Insert the above given 5 lines of Basic code (2 of them REM) into the module. Execute as a step (F8) in the IDE the first actual statement beginning with "dtField = ..." Do NOT execute a second step! (Would exit the Sub in this case. REM While the Sub is still running: Statement-position-arrow visible and pointing to 'End Sub'. Enter the variable name "dtField" into the 'Watch' bar. It's shown in the panel now. REM Still not having exited the Sub: Click on the little "+" next to 'dtField' in the Watch panel. Enjoy the crash. I originally did not test with different subtype services of "com.sun.star.text.textfield..." Assuming I would get the same result, I didn't want to get crashs again and again, and to probably get a corrupted configuration once. Now I also tested with subtype ".Author" and got the same kind of total crash. As soon as the field is already INSERTED into a text object by a statement like tx.insertTextContent(someRange, theField, anyBoolean) It can be inspected without a crash. -- You are receiving this mail because: You are the assignee for the bug.
