Game Development Community

Fix the damn website

by Jason Swearingen · in Site Feedback · 01/10/2006 (3:24 pm) · 2 replies

Sorry for the rather incendiary topic name, but honestly, please fix the website.

I recognize that the GG website was overdue for a cosmetic face lift, and that's great and all, but it introduced some bugs in the presentation...

and these bugs were 'fixed' in a very ad-hoc way. (example, adding horizontal scroll bars to postings that would otherwise be clipped)

This is of course due to forcing people to view the website at 800x600 resolution, which in itself is a questionable call.

Also, if you are revamping the website, why not add the following: increase the thread-topics displayed in the 'new fourms threads' from 10 to X (something like 20 or 30). As it stands right now I only get to see the last thread posts that occured in the last 2 hours. And clicking the "More unread posts" link under that is not helpfull, as it doesnt show unread posts, but instead shows a listing of all fourms you are subscribed to (whether there are unread posts or not)


And to prove my point on the first rant i mentioned in this post, behold the following code (a hi-res stopwatch if anyone needs one). (On IE, it will now be a serious pain in the ass to scroll horizontally to read my post)

//  Below is a high-resolution performance counter stopwatch i wrote in C++   it works, so use it if you want
// think of this as me paying for the cost of reading this rant ;)

//if you use this code, give me credit! ;)  jaytau <<aatt>> yahoo <<ddoott>> com

LARGE_INTEGER* g_large_integer_temp = new LARGE_INTEGER;
__int64 HighResolutionClock()  //accesses the high-resolution perf counter.  if there is an error, -1 is returned.
{
	bool isSuccess = QueryPerformanceCounter(g_large_integer_temp);
	if(!isSuccess)
	{
		return -1;
	}
	return g_large_integer_temp->QuadPart;
}

__int64 HighResolutionTicksPerSecond()  //returns the number of ticks occur per second from the high-res perf counter.  if there is an error, -1 is returned.
{
	bool isSuccess = QueryPerformanceFrequency(g_large_integer_temp);
	if(!isSuccess)
	{
		return -1;
	}
	return g_large_integer_temp->QuadPart;
}

int NUMBER_OF_CLOCKS=100;
__int64* g_int64_stopWatchElapsed=new __int64[NUMBER_OF_CLOCKS];
__int64* g_int64_stopWatchTime=new __int64[NUMBER_OF_CLOCKS];



__int64 StopWatchStart(int stopWatchNumber)  //starts (or unpauses) the stopwatch. //returns time in ticks (1/CLOCKS_PER_SEC gives the time per tick in seconds)
{
	if(stopWatchNumber==-1)  //if -1, then start all watches.
	{
		for(int i=0;i<NUMBER_OF_CLOCKS;i++)
		{
			StopWatchStart(i);
		}
		return 0;
	}
	__int64 int64_beginning = g_int64_stopWatchTime[stopWatchNumber];
	g_int64_stopWatchTime[stopWatchNumber] = HighResolutionClock();//time(&g_int64_stopWatchTime);

	if(int64_beginning!=0) //if the stopwatch is currently running...  (this is zero if the stopwatch is reset or has been stopped
	{
		g_int64_stopWatchElapsed[stopWatchNumber] += (g_int64_stopWatchTime[stopWatchNumber]-int64_beginning); //difftime(g_int64_stopWatchTime,int64_beginning);
	}
	return g_int64_stopWatchElapsed[stopWatchNumber];
}
NextNext Thread
PrevPrevious Thread
More from Site Feedback


Torque Owner Jason Swearingen
#1
01/10/2006 (3:25 pm)
And if anyone actually wanted that pef counter i pasted in code, here are the remaining 3 functions (i ran into the character limit in the post)

__int64 StopWatchStop(int stopWatchNumber) //stops (pauses) the stopwatch. //returns time in ticks (1/CLOCKS_PER_SEC gives the time per tick in seconds)
{
	if(stopWatchNumber==-1)  //if -1, then stop all watches.
	{
		for(int i=0;i<NUMBER_OF_CLOCKS;i++)
		{
			StopWatchStop(i);
		}
		return 0;
	}
	__int64 int64_beginning = g_int64_stopWatchTime[stopWatchNumber];
	__int64 int64_ending = HighResolutionClock();//time(&g_int64_stopWatchTime);

	if(int64_beginning!=0)
	{
		g_int64_stopWatchElapsed[stopWatchNumber] += (int64_ending-int64_beginning); //difftime(g_int64_stopWatchTime,int64_beginning);
	}

	g_int64_stopWatchTime[stopWatchNumber]=0;

	return g_int64_stopWatchElapsed[stopWatchNumber];
}



__int64 StopWatchReset(int stopWatchNumber) //stops and resets the stopwatch. //returns time in ticks (1/CLOCKS_PER_SEC gives the time per tick in seconds)
{
	if(stopWatchNumber==-1)  //if -1, then reset all watches.
	{
		for(int i=0;i<NUMBER_OF_CLOCKS;i++)
		{
			StopWatchReset(i);
		}
		return 0;
	}
	__int64 toReturn = StopWatchStop(stopWatchNumber);
	g_int64_stopWatchElapsed[stopWatchNumber]=0;
	g_int64_stopWatchTime[stopWatchNumber]=0;
	return toReturn;
}


__int64 StopWatchCheck(int stopWatchNumber) //checks the current stopwatch reading, without starting/stopping the watch. //returns time in ticks (1/CLOCKS_PER_SEC gives the time per tick in seconds)
{
	__int64 toReturn = g_int64_stopWatchElapsed[stopWatchNumber];
	__int64 currentTime = HighResolutionClock();//__int64 currentTime=time(0);

	if(g_int64_stopWatchTime[stopWatchNumber]!=0)
	{
		toReturn+=(currentTime-g_int64_stopWatchTime[stopWatchNumber]); //difftime(currentTime,g_int64_stopWatchTime);
	}
	return toReturn;
}

Torque Owner Stefan Lundmark
#2
01/10/2006 (3:52 pm)
I also think something needs to be done to the horizontal bar solution, because it does not do justice.
A long post that has text clipped is a PAIN to have to scroll down to the bottom each time, to scroll horizontally, go back up to read, and then scroll back each line of text.