WoW:UIOBJECT ScrollFrame - Revision history

Move page script: Move page script moved page UIOBJECT ScrollFrame to WoW:UIOBJECT ScrollFrame without leaving a redirect

2023-08-15T04:49:07Z

Move page script moved page UIOBJECT ScrollFrame to UIOBJECT ScrollFrame without leaving a redirect

← Older revision

Revision as of 04:49, 15 August 2023

Bear at 06:52, 14 February 2015

2015-02-14T06:52:37Z

← Older revision		Revision as of 06:52, 14 February 2015
Line 1:		Line 1:
	{{widget}}		{{widget}}
	~~{{Stub/API}}~~

	In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider\|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible.		In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider\|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible.
Line 8:		Line 7:
	'''Notice''': Multiple textures, positioned one to another, may start "fidgeting" when the ScrollFrame's ScrollChild containing them is resized/moved/scrolled. And "fidgeting" may mean quite serious distortions, with textures shifting up to 3-4 pixels in an unpredictable direction. Speculation here - apparently this happens because ScrollFrames are (seemingly) created by rendering all their content onto a texture in memory, and treating the ScrollFrame's ScrollChild as a mere Texture, taking its contents from the in-memory texture using SetTexCoord. Now when the 0-1 texture coordinates suffer from precision errors, everything starts to shake. Surprisingly, though, text does NOT suffer much. Bottom line - use ScrollFrames for large images or blocks of text, but not for a large number of multi-textured relatively-positioned controls.		'''Notice''': Multiple textures, positioned one to another, may start "fidgeting" when the ScrollFrame's ScrollChild containing them is resized/moved/scrolled. And "fidgeting" may mean quite serious distortions, with textures shifting up to 3-4 pixels in an unpredictable direction. Speculation here - apparently this happens because ScrollFrames are (seemingly) created by rendering all their content onto a texture in memory, and treating the ScrollFrame's ScrollChild as a mere Texture, taking its contents from the in-memory texture using SetTexCoord. Now when the 0-1 texture coordinates suffer from precision errors, everything starts to shake. Surprisingly, though, text does NOT suffer much. Bottom line - use ScrollFrames for large images or blocks of text, but not for a large number of multi-textured relatively-positioned controls.

	==~~XML~~==		== See also ==
	~~See~~ [[XML/ScrollFrame]]		* [[XML/ScrollFrame]]

WoWWiki>SinusPi at 16:24, 18 September 2009

2009-09-18T16:24:38Z

← Older revision		Revision as of 16:24, 18 September 2009
Line 4:		Line 4:
	In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider\|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible.		In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider\|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible.

			Scroll frames are good for scrolling large portions of text, or a large [[UIOBJECT EditBox\|EditBox]].

	~~Scroll frames~~ are ~~good~~ for ~~scrolling~~ large ~~portions~~ of text, or a large [[~~UIOBJECT EditBox\|EditBox~~]].		'''Notice''': Multiple textures, positioned one to another, may start "fidgeting" when the ScrollFrame's ScrollChild containing them is resized/moved/scrolled. And "fidgeting" may mean quite serious distortions, with textures shifting up to 3-4 pixels in an unpredictable direction. Speculation here - apparently this happens because ScrollFrames are (seemingly) created by rendering all their content onto a texture in memory, and treating the ScrollFrame's ScrollChild as a mere Texture, taking its contents from the in-memory texture using SetTexCoord. Now when the 0-1 texture coordinates suffer from precision errors, everything starts to shake. Surprisingly, though, text does NOT suffer much. Bottom line - use ScrollFrames for large images or blocks of text, but not for a large number of multi-textured relatively-positioned controls.

			==XML==
			See [[XML/ScrollFrame]]

WoWWiki>Adys at 13:43, 24 December 2008

2008-12-24T13:43:23Z

← Older revision		Revision as of 13:43, 24 December 2008
Line 5:		Line 5:


	Scroll frames are good for scrolling large portions of text, or a large [[UIOBJECT EditBox\|EditBox]]. However, there is a glitch that will cause dots to appear between the lines of text. This appearance of this glitch changes depending on the height of the ScrollFrame. Certain heights have no visible problems (250 worked for me, and there are others).		Scroll frames are good for scrolling large portions of text, or a large [[UIOBJECT EditBox\|EditBox]].

WoWWiki>Azxiana: Grammar

2007-04-05T02:33:16Z

Grammar

← Older revision		Revision as of 02:33, 5 April 2007
Line 5:		Line 5:


	Scroll frames are good for scrolling large portions of text, or ~~large~~ a large [[UIOBJECT EditBox\|EditBox]]. However, there is a glitch that will cause dots to appear between the lines of text. This appearance of this glitch changes depending on the height of the ScrollFrame. Certain heights have no visible problems (250 worked for me, and there are others).		Scroll frames are good for scrolling large portions of text, or a large [[UIOBJECT EditBox\|EditBox]]. However, there is a glitch that will cause dots to appear between the lines of text. This appearance of this glitch changes depending on the height of the ScrollFrame. Certain heights have no visible problems (250 worked for me, and there are others).

WoWWiki>Baudzilla: Added note about ScrollFrame display glitch

2007-02-24T19:58:39Z

Added note about ScrollFrame display glitch

← Older revision		Revision as of 19:58, 24 February 2007
Line 3:		Line 3:

	In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider\|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible.		In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider\|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible.


			Scroll frames are good for scrolling large portions of text, or large a large [[UIOBJECT EditBox\|EditBox]]. However, there is a glitch that will cause dots to appear between the lines of text. This appearance of this glitch changes depending on the height of the ScrollFrame. Certain heights have no visible problems (250 worked for me, and there are others).

WoWWiki>VoidvectorBot: Remove singatures made using ~ in main namespace

2007-02-10T07:47:17Z

Remove singatures made using ~ in main namespace

← Older revision		Revision as of 07:47, 10 February 2007
Line 2:		Line 2:
	{{Stub/API}}		{{Stub/API}}

	In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider\|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible. ~~--[[User:Mikk\|Mikk]] 17:22, 23 May 2006 (EDT)~~		In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider\|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible.

WoWWiki>Mikk: Stub. Explained what scrollframes are for and what they're NOT for (just use Sliders).

2006-05-23T21:22:35Z

Stub. Explained what scrollframes are for and what they're NOT for (just use Sliders).

New page

{{widget}}
{{Stub/API}}

In many cases, ScrollFrames, and in particular the FrameXML-defined FauxScrollFrame, does more than you need. If all you are trying to accomplish is offsetting a list in an array of buttons/fontstrings, as is often the case, all you really need is a [[UIOBJECT Slider|Slider]]. ScrollFrames are for smooth pixel-by-pixel scrolling of a complete frame that is only partially visible. --[[User:Mikk|Mikk]] 17:22, 23 May 2006 (EDT)