Classic CensusPlus
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
It is a beta because I am thinking about adding a message to be displayed when you request the main window to be opened.
One of the reasons CensusPlus did not start with full Guild display connections until you requested a specific realm was due to the computation demands to process all the display data.
Since I no longer have the ability to require Realm selection for those who want the data...
everyone has to pay the wait time.
On new fast machines.. you might not notice..
On my old limited resource notebook .. I did.. enough that even though I wrote the code.. I still had doubts that I had triggered the window open until it finally opened up.
There still may be other bugs.. that last code change was verified two seconds before Blizzard shutdown the realms this morning.
One of the reasons CensusPlus did not start with full Guild display connections until you requested a specific realm was due to the computation demands to process all the display data.
Since I no longer have the ability to require Realm selection for those who want the data...
everyone has to pay the wait time.
On new fast machines.. you might not notice..
On my old limited resource notebook .. I did.. enough that even though I wrote the code.. I still had doubts that I had triggered the window open until it finally opened up.
There still may be other bugs.. that last code change was verified two seconds before Blizzard shutdown the realms this morning.
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
Ah yes.. there were a few graphics tweaks let to do.. and they have been done.
I also moved the Guild window over.. since I made room when I .. yes it was mostly pre-planned
..made the not so last minute change to cover level 5-60 and display them
it is call planned compromise.. know what position you want.. push for more.. and accept a requested change back to what you had always thought best
(That is my story and I am sticking to it!)
I have also discovered my thoughts about the delay are incorrect!
I placed the message in code just before the routine jump to all the data calculations.. only to have the message and window open happen almost at the same time.. no delay noticed.
So the delay must be coming from the actual window Frame setup and creation process!
What is different between Classic and live? as the two code bases are the same for that.
I also moved the Guild window over.. since I made room when I .. yes it was mostly pre-planned
..made the not so last minute change to cover level 5-60 and display them
it is call planned compromise.. know what position you want.. push for more.. and accept a requested change back to what you had always thought best

(That is my story and I am sticking to it!)
I have also discovered my thoughts about the delay are incorrect!
I placed the message in code just before the routine jump to all the data calculations.. only to have the message and window open happen almost at the same time.. no delay noticed.
So the delay must be coming from the actual window Frame setup and creation process!
What is different between Classic and live? as the two code bases are the same for that.
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
oh it is data volume driven...
the delay appears to be in loading data character data from disk to memory.
live with 600KBytes of data took 2 seconds to load window.
Classic with almost 4.6MBytes of took over 4 seconds to load window.
When I renamed my output data file and restarted.. the window loaded right away.
And I also verified it was local computer issue. as Blizzard is getting hit by DDOS apparently again.
my latency during the last test was nearly 1000ms.
the delay appears to be in loading data character data from disk to memory.
live with 600KBytes of data took 2 seconds to load window.
Classic with almost 4.6MBytes of took over 4 seconds to load window.
When I renamed my output data file and restarted.. the window loaded right away.
And I also verified it was local computer issue. as Blizzard is getting hit by DDOS apparently again.
my latency during the last test was nearly 1000ms.
I'm seeing a weird glitch in the level range of 45-50 (I'm level 50, in case that's related) where I'm not getting results back during a census sweep using the current beta version.
I turned on verbose mode and ran it again and sure enough:
I turned on verbose mode and ran it again and sure enough:
Code: Select all
[11:14:19] Census+ Who query: 51-55, found 45
[11:14:19] Census+ Processing 45 characters.
[11:14:19] Census+ Sending /who 36-45
[11:14:26] Census+ Who query: 36-45, found 49
[11:14:26] Census+ Processing 49 characters.
[11:14:26] Census+ Sending /who 41-45
[11:14:32] Census+ Who query: 41-45, found 49
[11:14:32] Census+ Processing 49 characters.
[11:14:32] Census+ Sending /who 44-45
[11:14:39] Census+ Who query: 44-45, found 49
[11:14:39] Census+ Processing 49 characters.
[11:14:39] Census+ Sending /who 45-45
[11:14:45] Census+ Who query: 45-45, found 26
[11:14:45] Census+ Processing 26 characters.
[11:14:45] Census+ Sending /who 44-44
can confirm. Looks like 46-50 is empty.TheDeamon wrote:I'm seeing a weird glitch in the level range of 45-50 (I'm level 50, in case that's related) where I'm not getting results back during a census sweep using the current beta version.
I turned on verbose mode and ran it again and sure enough:
Code: Select all
[11:14:19] Census+ Who query: 51-55, found 45 [11:14:19] Census+ Processing 45 characters. [11:14:19] Census+ Sending /who 36-45 [11:14:26] Census+ Who query: 36-45, found 49 [11:14:26] Census+ Processing 49 characters. [11:14:26] Census+ Sending /who 41-45 [11:14:32] Census+ Who query: 41-45, found 49 [11:14:32] Census+ Processing 49 characters. [11:14:32] Census+ Sending /who 44-45 [11:14:39] Census+ Who query: 44-45, found 49 [11:14:39] Census+ Processing 49 characters. [11:14:39] Census+ Sending /who 45-45 [11:14:45] Census+ Who query: 45-45, found 26 [11:14:45] Census+ Processing 26 characters. [11:14:45] Census+ Sending /who 44-44

Now that's interesting, I have a reasonable number of characters in 46-49... although 50 is empty for me too.
However my database is a few days older as I had the beta version, some bug must've crept in before release then, or else I'd have a larger hole in my data; indeed checking on Show Chars, the characters I have in that lvl range were all last seen on the 8th or earlier.
However my database is a few days older as I had the beta version, some bug must've crept in before release then, or else I'd have a larger hole in my data; indeed checking on Show Chars, the characters I have in that lvl range were all last seen on the 8th or earlier.
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
Ah! I think I know what is happening..
it is due to not using 1 or level x0 as ending level.
The initial job queue is built bottom up like a stack of plates. and processed from top down.
Due to using level 5 as a starting.. the decade count is offset and with the beta levels are missed.
Good catch people.
it is due to not using 1 or level x0 as ending level.
The initial job queue is built bottom up like a stack of plates. and processed from top down.
Due to using level 5 as a starting.. the decade count is offset and with the beta levels are missed.
Good catch people.
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
One quick re-enable of a debug message confirms.
what happens as the stack builds up the last created/ first run, I have to make sure I don't attempt to query levels that are higher then allowed in the game.
The last query build is for Max-level to Max-level, the one before is and adjustment to get to Max-Level - 1.. and that where the Beta breaks.. and adjustment skips levels.
Easy fix.. expect a new beta on Curseforge soon.
what happens as the stack builds up the last created/ first run, I have to make sure I don't attempt to query levels that are higher then allowed in the game.
The last query build is for Max-level to Max-level, the one before is and adjustment to get to Max-Level - 1.. and that where the Beta breaks.. and adjustment skips levels.
Easy fix.. expect a new beta on Curseforge soon.
- Poisonenvy
- Posts: 48
- Joined: Wed Jun 25, 2008 4:10 pm
- Location: UK
- Contact:
Dunno if this is the right place, but I've just installed the new beta version and on login, have received two errors:
and:
(possibly because I'm in EU?)1x ClassicCensusPlus\realmlist_US.lua:44: '}' expected (to close '{' at line 6) near '.'
Locals:
and:
11x ClassicCensusPlus\CensusButton.lua:59: attempt to index field 'Info' (a nil value)
ClassicCensusPlus\CensusButton.lua:59: in function <ClassicCensusPlus>
Locals:
self = CensusButtonFrame {
0 = <userdata>
}
event = "ADDON_LOADED"
arg1 = "ClassicCensusPlus"
arg2 = "nil"
arg3 = "nil"
arg4 = "nil"
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index field 'Info' (a nil value)"
init = false
- Poisonenvy
- Posts: 48
- Joined: Wed Jun 25, 2008 4:10 pm
- Location: UK
- Contact:
7x Frame CensusPlusConnectedRealmButton1: Unknown function CENSUSPLUS_CONNECTEDRealmsButton_OnLoad in element OnLoad
6x Frame CensusPlusConnectedRealmButton1: Unknown function CENSUSPLUS_CONNECTEDRealmsButton_OnClick in element OnClick
6x CensusPlusConnectedRealmButton1: Couldn't find relative frame: CensusPlus
13x ClassicCensusPlus\realmlist_US.lua:44: '}' expected (to close '{' at line 6) near '.'
Locals:
1x ...rfaceClassicCensusPlus\ClassicCensusPlus-1.0.lua:4772: bad argument #1 to 'pairs' (table expected, got nil)
[C]: in function `pairs'
...rfaceClassicCensusPlus\ClassicCensusPlus-1.0.lua:4772: in function `PTR_Color_ProblemRealmGuilds_check'
...rfaceClassicCensusPlus\ClassicCensusPlus-1.0.luain function `CensusPlus_StartCensus'
...rfaceClassicCensusPlus\ClassicCensusPlus-1.0.luain function <rfaceClassicCensusPlus>
Locals:
(*temporary) = nil
(*temporary) = "table expected, got nil"
= <function> defined =[C]:-1
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
- Poisonenvy
- Posts: 48
- Joined: Wed Jun 25, 2008 4:10 pm
- Location: UK
- Contact:
- Poisonenvy
- Posts: 48
- Joined: Wed Jun 25, 2008 4:10 pm
- Location: UK
- Contact:
Logged in after updating and got the following:
7x Frame CensusPlusConnectedRealmButton1: Unknown function CENSUSPLUS_CONNECTEDRealmsButton_OnClick in element OnClick
also
7x CensusPlusConnectedRealmButton1: Couldn't find relative frame: CensusPlus
and
8x Frame CensusPlusConnectedRealmButton1: Unknown function CENSUSPLUS_CONNECTEDRealmsButton_OnLoad in element OnLoad
7x Frame CensusPlusConnectedRealmButton1: Unknown function CENSUSPLUS_CONNECTEDRealmsButton_OnClick in element OnClick
also
7x CensusPlusConnectedRealmButton1: Couldn't find relative frame: CensusPlus
and
8x Frame CensusPlusConnectedRealmButton1: Unknown function CENSUSPLUS_CONNECTEDRealmsButton_OnLoad in element OnLoad
- bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
Pruning does not work, there's still some coalesced/connected realm code in the prune function.
I would also like to confirm the "connected button" errors above. They are caught by the default error window during loading before Swatter loads in. The relevant code causing the errors is in ClassicCensusPlus.xml:
Line 127:
Line 912:
I would also like to confirm the "connected button" errors above. They are caught by the default error window during loading before Swatter loads in. The relevant code causing the errors is in ClassicCensusPlus.xml:
Line 127:
Code: Select all
<Button name="CensusPlusConnectedRealmsTemplate" virtual="true">
<Size>
<AbsDimension x="160" y="16" />
</Size>
<Layers>
<Layer level="BORDER">
<FontString name="$parentText" inherits="GameFontHighlight" justifyH="LEFT">
<Size>
<AbsDimension x="160" y="14" />
</Size>
<Anchors>
<Anchor point="LEFT">
<Offset>
<AbsDimension x="2" y="2" />
</Offset>
</Anchor>
</Anchors>
</FontString>
</Layer>
</Layers>
<HighlightTexture file="Interface\QuestFrame\UI-QuestTitleHighlight" alphaMode="ADD">
<Size>
<AbsDimension x="160" y="16" />
</Size>
<Anchors>
<Anchor point="TOP">
<Offset>
<AbsDimension x="0" y="0" />
</Offset>
</Anchor>
</Anchors>
</HighlightTexture>
<Scripts>
<OnLoad function="CENSUSPLUS_CONNECTEDRealmsButton_OnLoad" />
<OnClick function="CENSUSPLUS_CONNECTEDRealmsButton_OnClick" />
</Scripts>
</Button>
Code: Select all
<Button name="CensusPlusConnectedRealmButton1" inherits="CensusPlusConnectedRealmsTemplate" id="1">
<Anchors>
<Anchor point="TOPLEFT" relativeTo="CensusPlus">
<Offset>
<AbsDimension x="68" y="-32" />
</Offset>
</Anchor>
</Anchors>
</Button>
I have the same 3 errors and I confirm I only have ClassicCensusPlus addon in my classic addons folderbringoutyourdead wrote:Check your addon list..
That looks like you have loaded CensusPlus into the Classic client.. (and have the out of date checkbox enabled.)
You should only have ClassicCensusPlus in your addon directory and in your
WTF/'"Youraccountname"/Saved Variables directory.