Bugs - Revision history

Jrheinlaender at 17:04, 20 July 2017

2017-07-20T17:04:45Z

← Older revision		Revision as of 17:04, 20 July 2017
Line 2:		Line 2:
	== Getting debug output ==		== Getting debug output ==

	The first thing to do is to increase the debug level from the ~~Extras~~ - Options - Writer - iMath options page. A good starting point is level 2.		The first thing to do is to increase the debug level from the Tools - Options - Writer - iMath options page. A good starting point is level 2.

	On Linux, just run soffice from a terminal, and you will see the debug output.		On Linux, just run soffice from a terminal, and you will see the debug output.

Jrheinlaender at 19:04, 16 June 2017

2017-06-16T19:04:37Z

← Older revision		Revision as of 19:04, 16 June 2017
Line 6:		Line 6:
	On Linux, just run soffice from a terminal, and you will see the debug output.		On Linux, just run soffice from a terminal, and you will see the debug output.

	On Windows the location of the debug output depends on the iMath version. The newest versions (> 2.1.1) write to a file called iMathDebug_cerr.txt in the current user's temporary file directory (usually <User>/AppData/Local/ but see [https://msdn.microsoft.com/en-us/library/windows/desktop/aa364992(v=vs.85).aspx this link] for details).		On Windows the location of the debug output depends on the iMath version. The newest versions (> 2.1.1) write to a file called iMathDebug_cerr.txt in the current user's temporary file directory (usually <User>/AppData/Local/ but see [https://msdn.microsoft.com/en-us/library/windows/desktop/aa364992(v=vs.85).aspx this link] for details). If you still cannot find the log file, consider setting a well-defined temporary path as described [https://answers.microsoft.com/en-us/windows/forum/windows_7-files/change-location-of-temp-files-folder-to-another/19f13330-dde1-404c-aa27-a76c0b450818 here].

	Older versions output some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).		Older versions output some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).

Jrheinlaender at 20:02, 6 June 2017

2017-06-06T20:02:31Z

← Older revision		Revision as of 20:02, 6 June 2017
Line 6:		Line 6:
	On Linux, just run soffice from a terminal, and you will see the debug output.		On Linux, just run soffice from a terminal, and you will see the debug output.

	On Windows the location of the debug output depends on the iMath version. The newest versions (> 2.1.1) write to a file called iMathDebug_cerr.txt in the current user's temporary file directory (usually <User>/AppData/Local/).		On Windows the location of the debug output depends on the iMath version. The newest versions (> 2.1.1) write to a file called iMathDebug_cerr.txt in the current user's temporary file directory (usually <User>/AppData/Local/ but see [https://msdn.microsoft.com/en-us/library/windows/desktop/aa364992(v=vs.85).aspx this link] for details).

	Older versions output some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).		Older versions output some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).

Jrheinlaender: /* Getting debug output */

2015-12-28T15:47:43Z

Getting debug output

← Older revision		Revision as of 15:47, 28 December 2015
Line 6:		Line 6:
	On Linux, just run soffice from a terminal, and you will see the debug output.		On Linux, just run soffice from a terminal, and you will see the debug output.

	On Windows the location of the debug output depends on the iMath version. The newest versions write to a file called iMathDebug_cerr.txt in the current user's temporary file directory (usually <User>/AppData/Local/).		On Windows the location of the debug output depends on the iMath version. The newest versions (> 2.1.1) write to a file called iMathDebug_cerr.txt in the current user's temporary file directory (usually <User>/AppData/Local/).

	Older versions output some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).		Older versions output some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).
Line 12:		Line 12:
	But usually this will be empty... So you need a Microsoft Visual Studio installation to proceed. Here you will find a program called editbin.exe.		But usually this will be empty... So you need a Microsoft Visual Studio installation to proceed. Here you will find a program called editbin.exe.

	On Windows, you need to open a command prompt ("Run" - ~~command~~). In the little black window that comes up, change to the Office installation directory (e.g. cd "C:\Program Files\LibreOffice ~~3.6~~\program"). If you type soffice.exe here, the Office should start, otherwise you are in the wrong directory. Tip: If you press the <tab> key while entering the path, Windows will rotate through all possible continuations. E.g. you could type cd C:\Pro and then press the <tab> key to reach C:\Program Files. Then enter \Li and press <tab> again until you reach C:\Program Files\LibreOffice ~~3.6~~ and so on.		On Windows, you need to open a command prompt ("Run" - cmd). In the little black window that comes up, change to the Office installation directory (e.g. cd "C:\Program Files\LibreOffice 5\program"). If you type soffice.exe here, the Office should start, otherwise you are in the wrong directory. Tip: If you press the <tab> key while entering the path, Windows will rotate through all possible continuations. E.g. you could type cd C:\Pro and then press the <tab> key to reach C:\Program Files. Then enter \Li and press <tab> again until you reach C:\Program Files\LibreOffice 5 and so on.

	Now set your path to find editbin.exe: Type C:\Program Files\Microsoft Visual Studio 10.0\Common7\Tools\vsvars32.bat You should get a message telling you the environment was set. Now tell Windows to send debug output to the window and to stdout.txt: editbin /~~subsytem~~:console soffice.exe and the same again for soffice.bin.		Now set your path to find editbin.exe: Type C:\Program Files\Microsoft Visual Studio 12.0\Common7\Tools\vsvars32.bat (assuming you installed Visual Studio 12). You should get a message telling you the environment was set. Now tell Windows to send debug output to the window and to stdout.txt: editbin /subsystem:console soffice.exe and the same again for soffice.bin.

	Run soffice.exe and you should see some output in the window and more in stdout.txt.		Run soffice.exe and you should see some output in the window and more in stdout.txt.

Jrheinlaender: /* Getting debug output */

2015-12-28T15:43:25Z

Getting debug output

← Older revision		Revision as of 15:43, 28 December 2015
Line 2:		Line 2:
	== Getting debug output ==		== Getting debug output ==

	On Linux, just run soffice from a terminal. On Windows, iMath ~~outputs~~ some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).		The first thing to do is to increase the debug level from the Extras - Options - Writer - iMath options page. A good starting point is level 2.

			On Linux, just run soffice from a terminal, and you will see the debug output.

			On Windows the location of the debug output depends on the iMath version. The newest versions write to a file called iMathDebug_cerr.txt in the current user's temporary file directory (usually <User>/AppData/Local/).

			Older versions output some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).

	But usually this will be empty... So you need a Microsoft Visual Studio installation to proceed. Here you will find a program called editbin.exe.		But usually this will be empty... So you need a Microsoft Visual Studio installation to proceed. Here you will find a program called editbin.exe.

Admin: /* Feature requests */

2012-12-15T11:10:18Z

Feature requests

← Older revision		Revision as of 11:10, 15 December 2012
Line 1:		Line 1:

			== Getting debug output ==

			On Linux, just run soffice from a terminal. On Windows, iMath outputs some information to a file called stdout.txt in the Office program directory (e.g. C:\Program Files\LibreOffice 3.6\program).

			But usually this will be empty... So you need a Microsoft Visual Studio installation to proceed. Here you will find a program called editbin.exe.

			On Windows, you need to open a command prompt ("Run" - command). In the little black window that comes up, change to the Office installation directory (e.g. cd "C:\Program Files\LibreOffice 3.6\program"). If you type soffice.exe here, the Office should start, otherwise you are in the wrong directory. Tip: If you press the <tab> key while entering the path, Windows will rotate through all possible continuations. E.g. you could type cd C:\Pro and then press the <tab> key to reach C:\Program Files. Then enter \Li and press <tab> again until you reach C:\Program Files\LibreOffice 3.6 and so on.

			Now set your path to find editbin.exe: Type C:\Program Files\Microsoft Visual Studio 10.0\Common7\Tools\vsvars32.bat You should get a message telling you the environment was set. Now tell Windows to send debug output to the window and to stdout.txt: editbin /subsytem:console soffice.exe and the same again for soffice.bin.

			Run soffice.exe and you should see some output in the window and more in stdout.txt.

	== Feature requests ==		== Feature requests ==

Admin: /* Feature requests */

2012-12-10T04:46:54Z

Feature requests

← Older revision		Revision as of 04:46, 10 December 2012
Line 2:		Line 2:
	== Feature requests ==		== Feature requests ==

	Please use the [http://sourceforge.net/p/ooo-imath/feature-requests\|sourceforge interface] for this.		Please use the [http://sourceforge.net/p/ooo-imath/feature-requests sourceforge interface] for this.

	== Bugs ==		== Bugs ==

	Please use the [http://sourceforge.net/p/ooo-imath/bugs sourceforge interface] for this.		Please use the [http://sourceforge.net/p/ooo-imath/bugs sourceforge interface] for this.

Admin: /* Bugs */

2012-12-10T04:43:14Z

Bugs

← Older revision		Revision as of 04:43, 10 December 2012
Line 5:		Line 5:

	== Bugs ==		== Bugs ==

			Please use the [http://sourceforge.net/p/ooo-imath/bugs sourceforge interface] for this.

Admin: /* Feature requests */

2012-12-10T04:42:44Z

Feature requests

← Older revision		Revision as of 04:42, 10 December 2012
Line 2:		Line 2:
	== Feature requests ==		== Feature requests ==

	~~Managing options through user~~-~~defined properties is not user~~-~~friendly~~.		Please use the [http://sourceforge.net/p/ooo-imath/feature-requests\|sourceforge interface] for this.

	== Bugs ==		== Bugs ==

Jrheinlaender: Created page with ' == Feature requests == Managing options through user-defined properties is not user-friendly. == Bugs =='

2012-03-03T14:40:40Z

Created page with ' == Feature requests == Managing options through user-defined properties is not user-friendly. == Bugs =='

New page

== Feature requests ==

Managing options through user-defined properties is not user-friendly.

== Bugs ==