RendererIssues - Revision history

Colin Marquardt: Reverted edits by Uu4E4n (Talk); changed back to last version by GigaClon

2007-04-20T15:47:36Z

Reverted edits by Uu4E4n (Talk); changed back to last version by GigaClon

← Older revision		Revision as of 15:47, 20 April 2007
Line 1:		Line 1:
	This is a meta-page for bugs and problems related to the renderer. The ones I found are:		This is a meta-page for bugs and problems related to the renderer. The ones I found are:

	* [http://sourceforge.net/tracker/index.php?func=detail		* [http://sourceforge.net/tracker/index.php?func=detail&aid=853827&group_id=93438&atid=604306 bug 853827]

			* [http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306 bug 854468]

			* As discussed on Sodipodi list long ago, the maximum zoom is set in desktop.h. I tried

			#define SP_DESKTOP_ZOOM_MAX 256.0

			:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.

			My wild guess is that the above problems are related, and that they can be fixed or at least made less nasty by increasing the precision used by the renderer. Does this sound plausible?

			Answering my own question: yes it does, partially. Making everything double in libnr fixed the last of the three problems above. Patch is being submitted. Two other problems, however, did not fix. In fact 853827 even became worse: now it crashes as soon as you try to zoom into the zero-length path. Other than that, however, Inkscape seems to work fine with double precision. Todo: increase the precision of writing coordinates into SVG (currently only 6 digits!).

			UPDATE: 853827 is now fixed (this was a one-character fix, borrowed from Sodipodi). 854468 stays.

			----

			It's not simply a matter of throwing more bits at the problem. If the rendering is all based on floating-point then there will be problems since you don't get fine control of the precision. This is one of the issues we've been trying to handle well with [http://cairographics.org cairo] where the guts use fixed-point arithmetic almost everywhere, (and where they don't it's a bug). See [[Cairoification]] --Carl Worth
			[[Category:Wiki Attic]]

Uu4E4n at 15:38, 11 April 2007

2007-04-11T15:38:29Z

← Older revision		Revision as of 15:38, 11 April 2007
Line 1:		Line 1:
	This is a meta-page for bugs and problems related to the renderer. The ones I found are:		This is a meta-page for bugs and problems related to the renderer. The ones I found are:

	* [http://sourceforge.net/tracker/index.php?func=detail~~&aid=853827&group_id=93438&atid=604306 bug 853827]~~		* [http://sourceforge.net/tracker/index.php?func=detail

	* [http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306 bug 854468]

	* As discussed on Sodipodi list long ago, the maximum zoom is set in desktop.h. I tried

	~~#define SP_DESKTOP_ZOOM_MAX 256.0~~

	~~:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.~~

	~~My wild guess is that the above problems are related, and that they can be fixed or at least made less nasty by increasing the precision used by the renderer. Does this sound plausible?~~

	Answering my own question: yes it does, partially. Making everything double in libnr fixed the last of the three problems above. Patch is being submitted. Two other problems, however, did not fix. In fact 853827 even became worse: now it crashes as soon as you try to zoom into the zero-length path. Other than that, however, Inkscape seems to work fine with double precision. Todo: increase the precision of writing coordinates into SVG (currently only 6 digits!).

	~~UPDATE: 853827 is now fixed (this was a one-character fix, borrowed from Sodipodi). 854468 stays.~~

	~~----~~

	It's not simply a matter of throwing more bits at the problem. If the rendering is all based on floating-point then there will be problems since you don't get fine control of the precision. This is one of the issues we've been trying to handle well with [http://cairographics.org cairo] where the guts use fixed-point arithmetic almost everywhere, (and where they don't it's a bug). See [[Cairoification]] --Carl Worth
	~~[[Category:Wiki Attic]]~~

GigaClon: Categorization

2006-06-20T18:14:42Z

Categorization

← Older revision		Revision as of 18:14, 20 June 2006
Line 7:		Line 7:
	* As discussed on Sodipodi list long ago, the maximum zoom is set in desktop.h. I tried		* As discussed on Sodipodi list long ago, the maximum zoom is set in desktop.h. I tried

	#define [[SP_DESKTOP_ZOOM_MAX]] 256.0		#define SP_DESKTOP_ZOOM_MAX 256.0

	:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.		:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.
Line 20:		Line 20:

	It's not simply a matter of throwing more bits at the problem. If the rendering is all based on floating-point then there will be problems since you don't get fine control of the precision. This is one of the issues we've been trying to handle well with [http://cairographics.org cairo] where the guts use fixed-point arithmetic almost everywhere, (and where they don't it's a bug). See [[Cairoification]] --Carl Worth		It's not simply a matter of throwing more bits at the problem. If the rendering is all based on floating-point then there will be problems since you don't get fine control of the precision. This is one of the issues we've been trying to handle well with [http://cairographics.org cairo] where the guts use fixed-point arithmetic almost everywhere, (and where they don't it's a bug). See [[Cairoification]] --Carl Worth
			[[Category:Wiki Attic]]

Conversion script: link fix

2006-01-22T02:33:33Z

link fix

← Older revision		Revision as of 02:33, 22 January 2006
Line 7:		Line 7:
	* As discussed on Sodipodi list long ago, the maximum zoom is set in desktop.h. I tried		* As discussed on Sodipodi list long ago, the maximum zoom is set in desktop.h. I tried

	#define SP_DESKTOP_ZOOM_MAX 256.0		#define [[SP_DESKTOP_ZOOM_MAX]] 256.0

	:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.		:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.

Buliabyak: *

2003-12-11T20:59:05Z

New page

This is a meta-page for bugs and problems related to the renderer. The ones I found are:

* [http://sourceforge.net/tracker/index.php?func=detail&aid=853827&group_id=93438&atid=604306 bug 853827]

* [http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306 bug 854468]

* As discussed on Sodipodi list long ago, the maximum zoom is set in desktop.h. I tried

#define SP_DESKTOP_ZOOM_MAX 256.0

:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.

My wild guess is that the above problems are related, and that they can be fixed or at least made less nasty by increasing the precision used by the renderer. Does this sound plausible?

Answering my own question: yes it does, partially. Making everything double in libnr fixed the last of the three problems above. Patch is being submitted. Two other problems, however, did not fix. In fact 853827 even became worse: now it crashes as soon as you try to zoom into the zero-length path. Other than that, however, Inkscape seems to work fine with double precision. Todo: increase the precision of writing coordinates into SVG (currently only 6 digits!).

UPDATE: 853827 is now fixed (this was a one-character fix, borrowed from Sodipodi). 854468 stays.

----

It's not simply a matter of throwing more bits at the problem. If the rendering is all based on floating-point then there will be problems since you don't get fine control of the precision. This is one of the issues we've been trying to handle well with [http://cairographics.org cairo] where the guts use fixed-point arithmetic almost everywhere, (and where they don't it's a bug). See [[Cairoification]] --Carl Worth

Buliabyak: *

2003-12-05T01:23:58Z

← Older revision		Revision as of 01:23, 5 December 2003
Line 11:		Line 11:
	:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.		:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.

	My wild guess is that the above problems are related, and that they can be fixed or at least made less nasty by increasing the precision used by the renderer. Does this sound plausible?		My wild guess is that the above problems are related, and that they can be fixed or at least made less nasty by increasing the precision used by the renderer. Does this sound plausible?

			Answering my own question: yes it does, partially. Making everything double in libnr fixed the last of the three problems above. Patch is being submitted. Two other problems, however, did not fix. In fact 853827 even became worse: now it crashes as soon as you try to zoom into the zero-length path. Other than that, however, Inkscape seems to work fine with double precision. Todo: increase the precision of writing coordinates into SVG (currently only 6 digits!).

Buliabyak: *

2003-12-05T00:57:43Z

← Older revision		Revision as of 00:57, 5 December 2003
Line 1:		Line 1:
	This is a meta-page for bugs and problems related to the renderer. The ones I found are:		This is a meta-page for bugs and problems related to the renderer. The ones I found are:

			* [http://sourceforge.net/tracker/index.php?func=detail&aid=853827&group_id=93438&atid=604306 bug 853827]

	* [http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306 bug 854468]		* [http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306 bug 854468]

			* As discussed on Sodipodi list long ago, the maximum zoom is set in desktop.h. I tried

			#define SP_DESKTOP_ZOOM_MAX 256.0

			:but that revealed many problems with the renderer. For example, on my system at about 70x zoom, lines in paths simply disappear.

			My wild guess is that the above problems are related, and that they can be fixed or at least made less nasty by increasing the precision used by the renderer. Does this sound plausible?

Buliabyak: *

2003-12-05T00:48:42Z

← Older revision		Revision as of 00:48, 5 December 2003
Line 1:		Line 1:
	This is a meta-page for bugs and problems related to the renderer. The ones I found are:		This is a meta-page for bugs and problems related to the renderer. The ones I found are:

	* [[http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306 \| bug 854468]]		* [http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306 bug 854468]

Buliabyak: *

2003-12-05T00:48:20Z

← Older revision		Revision as of 00:48, 5 December 2003
Line 1:		Line 1:
	This is a meta-page for bugs and problems related to the renderer. The ones I found are:		This is a meta-page for bugs and problems related to the renderer. The ones I found are:

	* [[~~bug 854468 \|~~ http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306]]		* [[http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306 \| bug 854468]]

Buliabyak: *

2003-12-05T00:48:04Z

New page

This is a meta-page for bugs and problems related to the renderer. The ones I found are:

* [[bug 854468 | http://sourceforge.net/tracker/index.php?func=detail&aid=854468&group_id=93438&atid=604306]]