WoW:API Region SetPoint/Exponential time - Revision history

Move page script: Move page script moved page API Region SetPoint/Exponential time to WoW:API Region SetPoint/Exponential time without leaving a redirect

2023-08-15T04:47:08Z

Move page script moved page API Region SetPoint/Exponential time to API Region SetPoint/Exponential time without leaving a redirect

← Older revision

Revision as of 04:47, 15 August 2023

WoWWiki>Sky2042: redirect

2008-11-02T01:18:15Z

redirect

← Older revision		Revision as of 01:18, 2 November 2008
Line 1:		Line 1:
	~~{{widgetmethod}}~~		#Redirect [[API Region SetPoint]]
	~~As of approximately v1.11, creating a chain of relative positioning, where more than one~~ SetPoint~~() call is done on a number of frames (i.e. the next frame has its size ''and'' position dependent on the previous one), causes '''exponential execution time''' during SetPoint() calls.~~

	~~== Multiple chained SetPoint() calls causing exponential execution time ==~~

	~~Consider the below code, which creates a stack of frames, each 100 pixels wide and 10 pixels high, with 2 pixels of spacing between them:~~

	~~first = CreateFrame("Frame", UIParent);~~
	~~first:SetPoint("TOPLEFT", UIParent, "BOTTOMLEFT", 700, 500);~~
	~~first:SetWidth(100);~~
	~~first:SetHeight(10);~~
	~~prev=first;~~
	~~for i=1,NUMFRAMES do~~
	~~f = CreateFrame("Frame", UIParent);~~
	~~f:SetPoint("TOPLEFT", prev, "BOTTOMLEFT", 0, -2);~~
	~~f:SetPoint("TOPRIGHT", prev, "BOTTOMRIGHT", 0, -2);~~
	~~f:SetHeight(10);~~
	~~prev=f;~~
	~~end~~
	~~endTime = GetTime();~~

	~~Timing results for different numbers of frames chained:~~
	~~19: 0.3s~~
	~~20: 0.6s~~
	~~21: 1.3s~~
	~~22: 2.6s~~
	~~23: 5.2s~~
	~~24: 10.4s~~
	~~25: 20.8s~~


	* The original snippet feeds information for the same edge (TOP) twice, but the below code, which avoids doing that, has the exact same results:
	~~f:SetPoint("TOPLEFT", prev, "BOTTOMLEFT", 0, -2);~~
	~~f:SetPoint("'''RIGHT'''", prev, "'''RIGHT'''", 0, 0);~~


	* Referencing the same corner in both calls also has the same results:
	~~f:SetPoint("TOPLEFT", prev, "'''TOPLEFT'''", 0, -12);~~
	~~f:SetPoint("TOPRIGHT", prev, "'''TOPLEFT'''", 100, -12);~~


	~~== Solutions ==~~

	* However, chaining only ONE SetPoint from object to object, and referencing the first object for the second SetPoint, executes faster than GetTime() can measure even for dozens of objects:
	~~f:SetPoint("TOPLEFT", prev, "BOTTOMLEFT", 0, -2);~~
	~~f:SetPoint("RIGHT", '''first''', "RIGHT", 0,0);~~


	* This code also executes in "0 seconds":
	~~f:SetPoint("TOPLEFT", prev, "BOTTOMLEFT", 0, -2);~~
	~~'''f:SetWidth(100);'''~~


	~~Timing the two problematic SetPoint() calls, they both take the same time (i.e. 1.3s each on the 23rd loop). Nothing else in the loop is taking any discernible amount of time.~~

WoWWiki>Pcj at 16:33, 15 April 2008

2008-04-15T16:33:42Z

← Older revision		Revision as of 16:33, 15 April 2008
Line 1:		Line 1:
	~~<small>[[API Region SetPoint\|Region:SetPoint]] » Exponential time</small>~~{{widgetmethod}}		{{widgetmethod}}


	As of approximately v1.11, creating a chain of relative positioning, where more than one SetPoint() call is done on a number of frames (i.e. the next frame has its size ''and'' position dependent on the previous one), causes '''exponential execution time''' during SetPoint() calls.		As of approximately v1.11, creating a chain of relative positioning, where more than one SetPoint() call is done on a number of frames (i.e. the next frame has its size ''and'' position dependent on the previous one), causes '''exponential execution time''' during SetPoint() calls.

WoWWiki>Jyslin at 14:42, 10 August 2007

2007-08-10T14:42:49Z

← Older revision		Revision as of 14:42, 10 August 2007
Line 2:		Line 2:


	As of approximately v1.11, creating a chain of relative positioning, where more than one SetPoint() call is done on a number of frames (i.e. the next frame has its size ''and''' position dependent on the previous one), causes '''exponential execution time''' during SetPoint() calls.		As of approximately v1.11, creating a chain of relative positioning, where more than one SetPoint() call is done on a number of frames (i.e. the next frame has its size ''and'' position dependent on the previous one), causes '''exponential execution time''' during SetPoint() calls.

	== Multiple chained SetPoint() calls causing exponential execution time ==		== Multiple chained SetPoint() calls causing exponential execution time ==

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

2007-02-10T06:34:45Z

Remove singatures made using ~ in main namespace

← Older revision		Revision as of 06:34, 10 February 2007
Line 55:		Line 55:

	Timing the two problematic SetPoint() calls, they both take the same time (i.e. 1.3s each on the 23rd loop). Nothing else in the loop is taking any discernible amount of time.		Timing the two problematic SetPoint() calls, they both take the same time (i.e. 1.3s each on the 23rd loop). Nothing else in the loop is taking any discernible amount of time.


	~~--[[User:Mikk\|Mikk]] 02:49, 19 August 2006 (EDT)~~

WoWWiki>Mikk: Explanation of exponential-time bug, and solutions

2006-08-19T06:49:19Z

Explanation of exponential-time bug, and solutions

New page

<small>[[API Region SetPoint|Region:SetPoint]] » Exponential time</small>{{widgetmethod}}

As of approximately v1.11, creating a chain of relative positioning, where more than one SetPoint() call is done on a number of frames (i.e. the next frame has its size ''and''' position dependent on the previous one), causes '''exponential execution time''' during SetPoint() calls.

== Multiple chained SetPoint() calls causing exponential execution time ==

Consider the below code, which creates a stack of frames, each 100 pixels wide and 10 pixels high, with 2 pixels of spacing between them:

first = CreateFrame("Frame", UIParent);
first:SetPoint("TOPLEFT", UIParent, "BOTTOMLEFT", 700, 500);
first:SetWidth(100);
first:SetHeight(10);
prev=first;
for i=1,NUMFRAMES do
f = CreateFrame("Frame", UIParent);
f:SetPoint("TOPLEFT", prev, "BOTTOMLEFT", 0, -2);
f:SetPoint("TOPRIGHT", prev, "BOTTOMRIGHT", 0, -2);
f:SetHeight(10);
prev=f;
end
endTime = GetTime();

Timing results for different numbers of frames chained:
19: 0.3s
20: 0.6s
21: 1.3s
22: 2.6s
23: 5.2s
24: 10.4s
25: 20.8s

* The original snippet feeds information for the same edge (TOP) twice, but the below code, which avoids doing that, has the exact same results:
f:SetPoint("TOPLEFT", prev, "BOTTOMLEFT", 0, -2);
f:SetPoint("'''RIGHT'''", prev, "'''RIGHT'''", 0, 0);

* Referencing the same corner in both calls also has the same results:
f:SetPoint("TOPLEFT", prev, "'''TOPLEFT'''", 0, -12);
f:SetPoint("TOPRIGHT", prev, "'''TOPLEFT'''", 100, -12);

== Solutions ==

* However, chaining only ONE SetPoint from object to object, and referencing the first object for the second SetPoint, executes faster than GetTime() can measure even for dozens of objects:
f:SetPoint("TOPLEFT", prev, "BOTTOMLEFT", 0, -2);
f:SetPoint("RIGHT", '''first''', "RIGHT", 0,0);

* This code also executes in "0 seconds":
f:SetPoint("TOPLEFT", prev, "BOTTOMLEFT", 0, -2);
'''f:SetWidth(100);'''

Timing the two problematic SetPoint() calls, they both take the same time (i.e. 1.3s each on the 23rd loop). Nothing else in the loop is taking any discernible amount of time.

--[[User:Mikk|Mikk]] 02:49, 19 August 2006 (EDT)