All timestamps are in US Mountain Standard Time because i'm too lazy^H^H^H^H busy to write a decent IRC log converter. This converter was originally from Micah Dowty from PicoGUI.

Please note that due to XChat configuration problems, only half of this file has correct time-stamps

01:00:00   --> criswell (Sam Hart <criswell at geekcomix dot com>) has joined #tux4kids
01:00:00   --- carter.openprojects.net sets mode +n #tux4kids
01:00:00   --- criswell has changed the topic to: Sam may be late.... session is being logged
01:00:00   --- We'll miss you
01:00:00   --> cal (Calvin Arndt <cal at tux4kids dot org>) has joined #tux4kids
01:00:00 <cal> hi sam
01:00:00 <cal> I have 1.4 build system working now...
01:00:00   --- Received a CTCP TIME from cal
01:00:00   --> jdandr2 (Jesse Andrews <jdandr2 at uky dot edu>) has joined #tux4kids
01:00:00 <jdandr2> hey guys... sorry I am late :)
01:00:00 <cal> hi jess
01:00:00 <jdandr2> how's it going cal?
01:00:00 <cal> not really late actually bout 3 min early!
01:00:00 <cal> fine jess got a 1.4 build system working!
01:00:00 <jdandr2> great!
01:00:00 <jdandr2> I don't know anything about build systems... (are you walking about automake, etc)?
01:00:00 <jdandr2> looks like I have automake 1.4
01:00:00 <cal> been at it since 5 this morn... I hate the dueling auto's!
01:00:00 <cal> yes... automake autoconfig ...libdrool
01:00:00 <cal> hey got a pick for ya...
01:00:00 <jdandr2> I really like the changes you have been making... The only comment I have is about the large 640x480 tile you made of the background... Since it is repeating, we can just create the tile inside the game ... (I haven't looked at your code that much yet)
01:00:00 <jdandr2> hold on...
01:00:00 <jdandr2> I am in tinyirc (no DCC capabilities...)
01:00:00   --> jesse_132 (Jesse Andrews <jdandr2 at uky dot edu>) has joined #tux4kids
01:00:00   <-- jdandr2 has quit ("TinyIRC 1.1")
01:00:00   --- jesse_132 is now known as jdandr2
01:00:00 <jdandr2> ok. Now you can send it ;)
01:00:00 <cal> I wanna see somebody create that without using SDL_CreateRGBSurface()!
01:00:00 <jdandr2> what is wrong with SDL_CreateRGBSurface??
01:00:00 <cal> When I figure out how to do that my intent would be to create it again.. until then I'm sticking w/it
01:00:00 <cal> memleaks galore
01:00:00 <jdandr2> really?
01:00:00 <jdandr2> hmmm...
01:00:00 <jdandr2> espanol?
01:00:00 <cal> I can't say matter of factly I just know I had to get rid of it to get rid of the leaks...
01:00:00 <cal> Si!
01:00:00 <jdandr2> muy bueno!
01:00:00 <cal> www.freetranslation.com is great but making the pics takes forever!
01:00:00 <jdandr2> I am working on getting the ~n and other spanish chars..
01:00:00 <jdandr2> what we can do is create them on the file!
01:00:00 <jdandr2> (fly)
01:00:00 <jdandr2> we can use the sdl_ttf (which allows unicode)
01:00:00 <jdandr2> that will create some plain text graphics for us.
01:00:00 <cal> yeh... getting ttf going will be a godsend!
01:00:00 <jdandr2> Then we can create a filter that will colorize the graphics for us
01:00:00 <jdandr2> I am thinking about creating an app that just allows customization/i18n...
01:00:00 <jdandr2> It will basically allow you to pick text, graphics, type the menu titles, etc...
01:00:00 <jdandr2> Then it will create a settings file...
01:00:00 <jdandr2> Eventually I want to have the data be in ZIP format.. So we have the main graphics in a zip, and people can change it by adding their own zip (which will be hosted on the site)...
01:00:00 <jdandr2> this is after we get unicode working of course ;)
01:00:00 <jdandr2> did you have a chance to check out step 3?
01:00:00 <cal> mmm no not yrt didn't see it but I'm off after it now!
01:00:00 <jdandr2> its basically just centered letters ...
01:00:00 <cal> by the way tux-3 is an almost complete 1.6 build system... but the reson I sent is it has all my latest...
01:00:00 <jdandr2> tux-3? ??
01:00:00 <cal> the file I just sent... tux-3.tar.bz2
01:00:00 <jdandr2> can you send it again.. I didn't notice
01:00:00 <cal> I've only got about 15 diff tuxtype dirs... gotta name um sumthin...
01:00:00 <cal> coming your way..
01:00:00 <jdandr2> thanks.. I am trying out some code to make the big tile from small ones...
01:00:00 <cal> you know what I was thinking of trying for the splash?
01:00:00 <cal> have you seen SDL_rotozoom?
01:00:00 <jdandr2> no I haven't...
01:00:00 <jdandr2> libsdl.org ?
01:00:00 <cal> yes... from that site...
01:00:00 <jdandr2> it says to use sdl_gfx ... (deprecated)
01:00:00 <cal> I awesome actually!
01:00:00 <cal> s/I/it's/
01:00:00 <cal> well must be new then I got it 6-8 mos ago..
01:00:00 <jdandr2> sounds great... Maybe we can update the congrats to use it as well ;)
01:00:00 <cal> Hey thats an idea!
01:00:00 <cal> I think as far as the game goes there's alot of reconoitering that we can do to make it better.. for instance say the letter as they are typed...
01:00:00 <jdandr2> I think that using sdl_gfx (which contains rotozoom as well as a frame rate thing...)
01:00:00 <jdandr2> yep!
01:00:00 <jdandr2> I like that idea.
01:00:00 <jdandr2> I think that eventually TT will have different types of games (not just cascade)
01:00:00 <jdandr2> I was thinking about one where tux is swimming and typing letters cause him to avoid obstactes)
01:00:00 <jdandr2> First I want to get unicode though ;)
01:00:00 <cal> seems to me we need a lot more functions to become more "Mavis Beacon" like. That said theres lots of room to play!
01:00:00 <jdandr2> yep!
01:00:00 <jdandr2> I agree completely
01:00:00 <cal> Yes me thinks unicode may help bring more developer friends to the mix...
01:00:00 <jdandr2> we could even "steal" the tuxmath code to make a new "game" quickly (but it is very similar)...
01:00:00 <cal> I know there've gotta be a whole bunch of lurkers on the list...
01:00:00 <jdandr2> yep...
01:00:00 <cal> hey where is your SDL_image.h in your system???
01:00:00 <jdandr2> /usr/include/SDL/
01:00:00 <cal> ok then change your globals.h to <SDL/SDL_image.h> and try it and tell me if it works for you?
01:00:00 <jdandr2> in which version?
01:00:00 <cal> your step2 or 3
01:00:00 <jdandr2> yep..
01:00:00 <jdandr2> Although we probably do not want to do that since it may not work on windows... (plus people may install it other places)... I don't really know though...
01:00:00 <cal> who cares it'll work fine for windows (mingw) and VC 6 needs it's own stuff anyway and "SDL_image.h" does not work on my system (x86 linux)
01:00:00 <jdandr2> hehe ...
01:00:00 <cal> by the way when I build your stuff I always do it with mine!!!
01:00:00 <jdandr2> that sounds good with me... Once we get a working system, we can let others tell us how to build it...
01:00:00 <jdandr2> (do you mean your make stuff?)
01:00:00 <jdandr2> or your menu code??
01:00:00 <cal> step3 looks nice!
01:00:00 <cal> yes make _and_ menu...
01:00:00 <jdandr2> cool... Maybe then you can just package the combination stuff and we can use that as the base from here forward ???
01:00:00 <cal> jess: why is globals.h all in an ifdef???
01:00:00 <jdandr2> we don't want to include/define things more than once...
01:00:00 <jdandr2> (that is the theory)
01:00:00 <cal> is it taken care of by the preprocxessor ( I mean we don't have any __GLOBALS_H__ defines that I know of?? ) I guess I just really don't understand...
01:00:00 <jdandr2> oh...
01:00:00 <jdandr2> here is what is happening...
01:00:00 <jdandr2> The first time anything includes <globals.h>
01:00:00 <jdandr2> it checks to see ifndef __GLOBALS_H__
01:00:00 <jdandr2> that is, if not define __GLOBALS_H__.
01:00:00 <jdandr2> and at this point nothing has defined it.
01:00:00 <jdandr2> so it does the next ... lines (ntil the #endifndef or whatever it is call)
01:00:00 <jdandr2> the next thing that happens is #define __GLOBALS_H__
01:00:00 <jdandr2> so the next time that something
01:00:00 <jdandr2> #include <globals.h>
01:00:00 <jdandr2> the #ifndef __GLOBALS_H__ will return FALSE! so the following ... lines will not be done again...
01:00:00 <cal> Ahhh ok from then on globals.h is igored! I see said the blind man!
01:00:00 <jdandr2> it gets rid of nasty infinite loops..
01:00:00 <jdandr2> exactly!
01:00:00 <jdandr2> imagine if you had file1.h including file2.h and vice versa...
01:00:00 <jdandr2> this would lead to infinite loops withing #ifndef stuff...
01:00:00 <cal> no worry mate now I undeserstand why one setup I had wouldn't link... It compiled but I could lin it for all the redefine errors!
01:00:00 <jdandr2> cool... I had only done the #ifndef stuff once before and I didn't know why at the time...
01:00:00 <cal> I couldn't get on that pizzadude site..
01:00:00 <jdandr2> pizzadude.dk ?
01:00:00 <jdandr2> (I might have typed .uk since my wife is in Scotland and I type her email @....uk every day
01:00:00 <cal> when you make a patch what options do you use?
01:00:00 <jdandr2> It has been SO long since I have made a patch I don't remember...
01:00:00 <jdandr2> I always used diff to make diffs
01:00:00 <jdandr2> I never made real patches
01:00:00 <cal> thats what I meant really...
01:00:00 <jdandr2> oh, I just do diff file_a file_b
01:00:00 <jdandr2> what are you making a diff to?
01:00:00 <cal> which one's the orginal a or b?
01:00:00 <jdandr2> I think it is: diff orig new
01:00:00 <cal> ok... I only ask because there's really no docs on patching that I have found and diff man page only mentions patching in passing..
01:00:00 <jdandr2> ok.. I have some code that makes the big tile with no leaks...
01:00:00 <cal> send away!
01:00:00 <jdandr2> I keep getting fail when I try to dcc it...
01:00:00 <jdandr2> I will put it online for you.
01:00:00 <cal> it failed try again..
01:00:00 <jdandr2> http://sweb.uky.edu/~jdandr2/test.c
01:00:00 <jdandr2> gcc test.c -I/usr/include/SDL -Lsdl -lSDL_image
01:00:00 <jdandr2> and have an image call tile.png (just copy main_bkg.png to tile.png in the same directory as test.c)
01:00:00 <cal> compile it by itself???
01:00:00 <jdandr2> yep.
01:00:00 <jdandr2> It is just a proof of concept...
01:00:00 <jdandr2> (the code would have to be cleaned up to just plug it into TT
01:00:00 <jdandr2> what I do is create the tile 100 times in a row
01:00:00 <cal> hmmm compiling...
01:00:00 <jdandr2> I just found a few problems in the SDL_Delay stuff..
01:00:00 <jdandr2> darn.
01:00:00 <jdandr2> I had:
01:00:00 <jdandr2> for (loops=100; loops>0; loops--);
01:00:00 <jdandr2> that darn ; at the end shouldn't be there...
01:00:00 <cal> gcc didn't care here...
01:00:00 <jdandr2> well. that for(...); will do nothing if you don't remove the semicolon...
01:00:00 <jdandr2> for (loops=100;loops>0; loops--) ;
01:00:00 <jdandr2> will just loop from 100 to 0 doing nothing
01:00:00 <jdandr2> reget the test.c ...
01:00:00 <jdandr2> it creates a new tile.
01:00:00 <jdandr2> displays it.
01:00:00 <jdandr2> waits a second
01:00:00 <cal> fixed it here
01:00:00 <jdandr2> then FreeSurface on the big tile.
01:00:00 <jdandr2> then start over...
01:00:00 <jdandr2> 100 times...
01:00:00 <cal> how long does it run there
01:00:00 <jdandr2> 100 seconds
01:00:00 <jdandr2> and then 10 seconds
01:00:00 <jdandr2> (1 second per tile loop)
01:00:00 <jdandr2> then 10 seconds at the end...
01:00:00 <cal> regot... not working right...
01:00:00 <jdandr2> whats happening?
01:00:00   --- jdandr2 has changed the topic to: Sam may be late.... session is being logged ..
01:00:00 <cal> works fine ... so where's the !@#$%^&* leaks at in stable???
01:00:00 <jdandr2> I don't know ;)
01:00:00 <jdandr2> hehe
01:00:00 <jdandr2> are you sure it is in the tile code?
01:00:00   --- cal has changed the topic to: Sam _IS_ late...!!!!
01:00:00 <jdandr2> hehe
01:00:00 <jdandr2> was he here when you got here?
01:00:00 <cal> :-)
01:00:00 <cal> puter was he hasn't been here yet!
01:00:00 <jdandr2> is the tile generator in graphics.c right?
01:00:00   --- Does this mean you're really back?
01:00:00 <criswell> Hi guys
01:00:00 <cal> yes...
01:00:00 <cal> Hey jess he was just lurking!
01:00:00 <jdandr2> hehe
01:00:00   --- criswell has changed the topic to: Sam wasn't lurking
01:00:00   --- jdandr2 has changed the topic to: Sam is here!!!!
01:00:00 <criswell> last minute mothers day presents
01:00:00 <jdandr2> oops
01:00:00 <criswell> my mother is impossible
01:00:00 <jdandr2> I forgot about that...
01:00:00 <jdandr2> I guess I will just call them ;)
01:00:00 <jdandr2> cal: I am looking at the tile creating code and don't see the leak either....
01:00:00   --- cal has changed the topic to: Taa Daa!!!!! hey here them all clapping!
01:00:00 <jdandr2> it looks like temp, temp2 are being used intermediately but both are being freed...
01:00:00 <jdandr2> (Sam: we have been talking about various stuff and have been looking at the tile generation process right now main_bkg.png -> 640x480 surface)
01:00:00 <jdandr2> Sam: I am a dunce, but I have a few questions about cvs...
01:00:00 <jdandr2> are we using sf.net or tux-dev box?
01:00:00 <criswell> j: you did see my message about the parallax scrolling example, right?
01:00:00 <jdandr2> yep.
01:00:00 <criswell> we are using sf.net for cvs for tuxtype.
01:00:00 <cal> Jess one thing I keep noticint over and over... is that the frames don't count the way I would expect them to? I can't put my finger on it but it really seems as if theres a missing bracket or something thats cause a flow control buig and that could really be the cuprit..
01:00:00 <jdandr2> Cal was looking at using sdl_rotozoom for the menu options, which would be cool!
01:00:00 <criswell> basically, anything that already has a cvs account somewhere, is keeping it there
01:00:00 <jdandr2> ok.
01:00:00 <cal> s/noticint/noticing/
01:00:00 <jdandr2> cal: that could be the problem...
01:00:00 <jdandr2> cal: are we making sure to SDL_FreeSurface the background surface before launching a game?
01:00:00 <jdandr2> so if I have the cvs dev branch for TT, I can just start using it right ?
01:00:00 <jdandr2> I am thinking I will commit the combination of my stuff and Cal's awesome work!
01:00:00 <jdandr2> cal: it looks like we do free the background...
01:00:00 <cal> yes ... I have a local cvs server and everytime I found a leak in my stuff I applied it to my local cvs of stable but nothing seem to help..
01:00:00 <jdandr2> hmm
01:00:00 <criswell> I dont think I've been logging this (in case anyone cares)... I had this thing on while I was gone to log everything... but I cant find the file
01:00:00 <jdandr2> don't worry...
01:00:00 <cal> one feature that stable has is alot of unessesary duplication.. and even a couple of extra blits!
01:00:00 <jdandr2> if you start logging now... I will send you my buffer...
01:00:00 <cal> I have it all sam
01:00:00 <jdandr2> cool...
01:00:00 <jdandr2> so cal... here is where I think we are at... You have a lot done on the memory/menu. I have some ttf stuff done.
01:00:00 <jdandr2> If you could upload the combination of our code (or email)... Then we can both use that from today forward...
01:00:00 <jdandr2> does that sound good?
01:00:00 <cal> Works for me.....
01:00:00 <jdandr2> [off-topic] How you been doing Sam???
01:00:00 <criswell> jdandr2: fine... bit stressed these last few weeks... but things have calmed down
01:00:00 <jdandr2> great. Tonight I can attack that memory leak as well (or as soon as you up the combination code)...
01:00:00 <jdandr2> I think using sdl_gfx (which contains sdl_rotozoom) would be GREAT!!!!
01:00:00   --- cal is now known as cal_away
01:00:00 <jdandr2> I have been a little stressed.. I am finally really getting into studying quantum computation and it is VERY confusing (the physics stuff)...
01:00:00 <jdandr2> did you study quantum mechanics?
01:00:00 <criswell> I did, several years ago....
01:00:00 <jdandr2> it is fscked up...
01:00:00 <criswell> I am back in physics now, and am having the hardest time remembering everything
01:00:00 <jdandr2> I can imagine that...
01:00:00 <jdandr2> you don't use it, you loose it...
01:00:00 <jdandr2> I am having to relearn linear algebra ... (and abstract algebra as well)
01:00:00 <criswell> QM wasn't so bad... the key to QM is that most problems can't be solved... they can only be approximated
01:00:00 <jdandr2> (and quantum of coursE)
01:00:00 <jdandr2> hehe
01:00:00 <criswell> that works really well, since you only ever have to apply the same few equations and say "then a miracle happens"
01:00:00 <criswell> xMP (my new project) will be dealing with teaching Special Relativity
01:00:00 <jdandr2> (for tux4kids???)
01:00:00 <criswell> (if I can ever make time to work on it more)
01:00:00 <criswell> yes for tux4kids
01:00:00 <jdandr2> cool..
01:00:00 <jdandr2> how about xQM???
01:00:00 <criswell> it'll be highschool/college age...
01:00:00 <jdandr2> or xQC (x quantum compuation....)
01:00:00 <cal_away> Hey did anyone try out the win exec I put up other day???
01:00:00 <criswell> the key is that I'll be getting help from the U of A physics dept...
01:00:00 <criswell> I haven't
01:00:00 <criswell> sorry
01:00:00 <cal_away> ok
01:00:00 <jdandr2> no... no windows machines ;)
01:00:00 <jdandr2> I have friends I can have check it out...
01:00:00 <criswell> jesse: have you gotten tuxtype dev cvs to work out yet?
01:00:00 <cal_away> I'll get a combination of your/mine going the we'll test that one...
01:00:00 <jdandr2> cal_away: cool... Once you get that uploaded I will put it in tuxtype CVS...
01:00:00 <jdandr2> Sam: I have downloaded from it I haven't uploaded...
01:00:00 <criswell> jesse: but you know you have dev branch, right?
01:00:00 <jdandr2> Sam: I will be working on that tonight after I get the combined changes from Cal...
01:00:00 <jdandr2> how can I check?
01:00:00 <criswell> jesse: if you need any help, lemme know
01:00:00 <criswell> check in the README file
01:00:00 <criswell> it should say development branch or something similar
01:00:00 <jdandr2> README contains no branch info...
01:00:00 <criswell> then you probably have stable
01:00:00 <criswell> first line of README should say:
01:00:00 <criswell> Tux Typing (DEVELOPMENT BRANCH):
01:00:00 <jdandr2> hmmm. I cannot even get to google.com let alone sourceforge.net
01:00:00 <jdandr2> I will have to restart my cpu...
01:00:00 <jdandr2> I have to run... Sorry...
01:00:00 <jdandr2> I will be back in a few hours... I will email you sam if I have any problems getting the dev branch... I probably just downed the tuxtype-cvs from the tt page instead of cvs co ...
01:00:00 <jdandr2> cal_away: thanks for the work! This next version will rock even more!
01:00:00 <jdandr2> Sam: thanks for agreeing to do some graphics (no hurry)...
01:00:00 <criswell> okay, lemme know if you need any cvs info
01:00:00 <jdandr2> great!
01:00:00 <jdandr2> we got some good progress done in the last few weeks. Next week will be UNICODE input/output!!!
01:00:00 <jdandr2> hehe
01:00:00 <jdandr2> once that is done, we have tweaking and then a beta release of i18n...
01:00:00 <jdandr2> have a great day guys...
01:00:00 <criswell> see yez
01:00:00 <jdandr2> l8r ... have fun!
01:00:00 <criswell> cal: have you looked through the rel/ directory at all on the devbox?
01:00:00   <-- jdandr2 has quit ("code & sleep!!!")
01:00:00 <criswell> brb (switching machines- I hate this older machine :-/)
12:47:23   --> You are now talking on #tux4kids
12:47:23   --- Topic for #tux4kids is Taa Daa!!!!! hey here them all clapping!
12:47:23   --- Topic for #tux4kids set by cal at Sat May 11 12:11:11
12:47:43 <criswell> I'm back
12:51:39   --- You have new mail (45 messages, 569974 bytes total).
12:54:50 <cal_away> ok what am I doing wrong jess...
12:55:00 <criswell> he's gone
12:56:12 <criswell> cal_away: do you have diffs of what work you've done on tuxtype-stable?
12:56:30 <cal_away> Haaaaaa I gonna kick this thing.....
12:56:37 <criswell> what?
12:56:53   --- cal_away is now known as cal
12:57:10 <cal> Not in hand sam...
12:57:32 <criswell> i just want to make sure I have everything that's been done for it.
12:58:07 <cal> I set cvs here to try to figure out how to do what you need but alas I haven't spent enough time on it...
12:58:24 <criswell> what do I need you to do with cvs?
12:58:37 <cal> you will Sam I won't let it get away again
12:59:01 <criswell> Uh... okay :-)
13:01:01 <cal> I can't/won't send patches I haven't tested... And I can't test em till I have a cvs server setup(which I do).Now all I have do do Is figure out 1.) how to make em 2.) how to test em... alas not enough time in day!
13:01:29 <criswell> why do you need cvs though? all you need to do is run a diff from a cvs checkout
13:01:39 <criswell> (why do you need a cvs server, I mean)
13:02:57 <cal> well that just it Sam... what is a "diff from a cvs checkout" !!! see whats wrong?
13:03:22 <criswell> no. just do a cvs checkout of whats in stable (you only need a cvs client, not a server, on your machine for that)
13:03:31 <criswell> then, diff your files against whats in cvs stable
13:04:25 <criswell> you really shouldnt need a cvs server on your local machine
13:04:29 <cal> enter "diff" command here > <
13:05:15 <criswell> okay, let's say you're working in the directory "work/tuxtype/" and that the cvs checkout is in "work/stable/tuxtype/"
13:05:23 <criswell> and that you editted "playgame.c"
13:05:30 <criswell> to get a diff, do this
13:06:10 <criswell> diff work/tuxtype/playgame.c work/stable/tuxtype/playgame.c
13:06:28 <criswell> actually, you'll probably want to in turn pipe that output to a new file
13:06:50 <cal> >newfile
13:07:03 <cal> got it...
13:07:15 <criswell> there's more options, do a "man diff" for them
13:08:33 <cal> man diff only tells half the story (and if'n ya grep it you'll find exactly 1 reference to patch and none to cvs...)
13:08:50 <criswell> well. that's because they are seperate tools
13:09:11 <cal> I have yet to find a doc that gives the glue for the 3
13:09:35 <cal> seperate tools that do there work together
13:09:37 <criswell> cvs is the source code repository. its where the soure is stored.
13:09:50 <criswell> diff tells the difference between two files... that's all it does
13:10:06 <criswell> patch takes output from a diff file, and merges it into another file
13:10:44 <criswell> think of cvs like a car garage. The source code is the cars that go in the garage. diff and patch are like wrenches to work on the cars
13:14:04 <cal> I 'm not arguing here Sam... yes but the usefulness of diff while quite a powerful tool is quite miniscule when compared to the combination of the two tools diff&patch.. but on list after list after list.and in bugreport.whatever.txt... I have Seen so many comments of the nature "This project only aceppts PROPER patches..." that I may just be a little gun shy of sending something wrong...
13:14:43 <criswell> try it.... I wont bite. if it's wrong, then i'll see what we need to do to fix it.
13:15:56 <criswell> honestly, I really want to get jesse used to using them. if you dont use them as project manager, you tend to get bogged down pretty quickly
13:16:23 <criswell> for example, when jake first joined long ago, all he'd ever send me were this big-huge tarballs that had minor changes in them
13:16:46 <criswell> at the same time, i had a few other people who were sending me things.
13:17:04 <criswell> jake's changes got put in last because I'd have to go through by hand and see what had changed
13:17:16 <cal> we're trying to catch up sam... do you have a cvs there can you give me a chksum of graphics.c
13:17:47 <criswell> of the most recent stable branch you mean?
13:18:02 <cal> stable yes not dev...
13:18:28 <criswell> actually, my graphics.s stable has changed and needs to be updated...
13:19:12 <cal> K...
13:20:08 <criswell> crap... how do I get just stable again ;-) ?
13:20:33 <criswell> what's this?
13:20:56 <cal> cvs update from within an old stable tree
13:21:16 <cal> cvs -r stable_1_0_x
13:21:30 <cal> eye candy
13:24:28 <criswell> what is "La Cascada Clave?"
13:25:32 <cal> my biggest problem is I have 15 diff tuxtype dirs and haven't yet figured out how to name them so that a week later I can remember what each one had what...
13:25:59 <criswell> that could be a problem
13:26:05 <criswell> c4a2e2256a27a898baee8c269695401d graphics.c
13:26:20 <criswell> there's my md5 for graphics.c
13:26:32 <cal> k...
13:27:04 <criswell> the way I've got my directories set up now, is I just have a stable/ and a dev/ directory
13:27:21 <criswell> in each of these, there is one tuxtype directory.
13:28:22 <criswell> see, this is one of the problems I see with things like BK and Arch (they allow you to do this sort of randome experimental branching inside of the source repository... could you imagine the mess if we had made a branch fro every test we ran?)
13:29:00 <criswell> whereas CVS might not have that feature... but through limitting us, it helps keep our repository much cleaner ;-)
13:29:03 <cal> !!!
13:29:22 <cal> that would be worse tha what I have
13:31:06 <criswell> have you looked at the rel/ directory on the dev server at all?
13:34:14   --> bombastic (~bombastic@66-35-162-47.deltacom.net) has joined #tux4kids
13:34:23 <bombastic> hello
13:34:32 <criswell> hey jake
13:35:13 <bombastic> sam: have you read my email about cvstrac?
13:35:42 <criswell> yes, but I'm yet to respond... sorry....
13:36:17 <criswell> I dont think we'll get that much abuse as is... I think we should leave it open for joe user to add bugs
13:36:26 <cal> yea I know I have one email still waiting on me to reply... looked at it again in fact I mirrored that stuf locally.. I just kind think that I really need to introduce myself to those other packagers.. and look closer at the rel dir before I can reply intelligibly!
13:36:37 <criswell> if you want to come up with a policy for bug submission that would be fine
13:37:36 <criswell> cal: no that's fine. dont worry about talking to the other packagers yet (you can, but no worries yet) I want to first get you introduced to the rel/ directory
13:37:40 <criswell> and the files in it
13:37:56 <criswell> honestly, there's only two or three files you'll ever have to edit for each project
13:38:46 <criswell> bombastic: If you need help on a submission policy, I'd check out Abiword's or Mozilla's... they both have pretty good ones up on their sites.
13:38:57 <cal> cris:and toward that end... I want'd to check it out responcibly before I say anything!!!
13:39:30 <criswell> cal: also, I really would like to eventually replace it with something more automated... but that will happen when I can make time for it
13:40:11 <cal> what'd ya think of the eye candy?
13:40:23 <criswell> what does it mean?
13:40:47 <cal> bombastic: Hi Jake
13:41:07 <bombastic> cal: hi there
13:41:21 <cal> The key cascade (literal)
13:41:27 <bombastic> (sorry reading mozillas bug tracking page)
13:41:43 <criswell> cal: ah! so this is a spanish(?) port
13:41:47 <criswell> (theme)
13:41:58 <cal> woikin on it!!!
13:43:47 <cal> Hey I really need to minimize this window for a few while I try to make heads and tails out of graphics.c stable diff's I'll be back in ten or so...
13:44:12   --- cal is now known as cal_away
13:44:46 <bombastic> sam: I think i prefer abiword's page... it's much easier to read... should/could i mimic that?
13:45:04 <criswell> bombastic: i dont see why not.
13:45:09 <criswell> yes I like their page too
13:45:34 <criswell> mozilla's is very verbose. too verbose... we dont want to confuse people who would otherwise submit bugs
13:46:10 <bombastic> OTOH, by being more verbose mozilla would deter people from filing frivolous bug reports.
13:47:36 <bombastic> sam: why didnt we use bugzilla again? :)
13:48:25 <criswell> bombastic: primarily just because it was so much harder to set up, and (at least for the projects i've been involved in over the years) most of its features go completely unused.
13:48:56 <criswell> plus, i really do like the concept of "low-ceremony" (which is why I didn't use TUTOS, which was otherwise so very kewl ;-)
13:49:05 <bombastic> I was mainly joking :)
13:49:33 <bombastic> yeah, tutos was awesome. i still would like something like it for calandering and appointments
13:52:38 <criswell> bombastic: how were your finals?
13:52:55 <bombastic> sam: rough, and yours?
13:53:45 <criswell> bombastic: I was only taking one class, and it had a final project (that n-body problem I told you about)
13:54:22 <bombastic> i was late today because i went out with friends last night and celebrated the end of the semester
13:54:31   --- cal_away is now known as cal
13:54:38 <bombastic> feeling a bit groggy today :)
13:55:51 <cal> criswell: Sam whats your official point of view on the fprinf/printf thing....
13:56:53 <criswell> cal: uh... I honestly forget why we did that originally. I know it was for some reason...
13:56:56 <bombastic> i've always hated it (personally :)
13:57:03 <criswell> cal: oh, I remember...
13:57:24 <criswell> cal: on some systems if you send info to stdout it's ignored....
13:57:47 <criswell> but stderr will almost always generate something (a text file dumped to disk, etc.)
13:57:59   --- You have new mail (46 messages, 574366 bytes total).
13:58:14 <criswell> for example, I think stdout is ignored using BCC under win32 when not running from DOS prompt
13:58:51 <criswell> that was the reason why... I'm not very attached to it, tho, so we can change it
14:00:44 <cal> criswell: so you won't mind if'n ya get a huge number of fprintf's changed to printf's right? One more official position please... This I can't grep <int main (int x, char y))
14:00:53 <cal> THIS I CAN
14:00:57 <cal> int
14:01:15 <cal> main (int x, int y)
14:01:42 <criswell> cal: printfs are fine... the one BCC issue I was concerned about is no more with W2k & XP (more posix compliance)..
14:01:58 <criswell> what's wrong with int main(..)?
14:02:40 <cal> I've made a huge number of those changes to which I been pluggin in and I never even gave a thought to sayin somethin about it...
14:02:48 <bombastic> main(..) accepts two params from the system. one is a character array for the command line params, the other is the length of the array
14:03:30 <criswell> saying something about the layout you mean?
14:04:23 <cal> can't grep a .c file in that format for the func defs... (or at least I don't know how) but if'n ya just hit enter after the return value then I can!
14:04:58 <criswell> The functions are actually defined in the function header file
14:05:03 <cal> It's important since grepping allows automated documentation of the source
14:05:18 <criswell> oh, I see what you mean... I was confused
14:05:58 <criswell> I actually don't use grep that deeply (I'm a surface grep user ;-) so I dont know what the problem is
14:06:19 <criswell> plus, I do all my editting in Kate (not KDevelop... Kate now has all the features I want without the extra junk)
14:08:26 <criswell> hey, what's jesse's e-mail address (anyone have it on hand?)
14:08:36 <cal> that beside the point. Sam do you care whether the return value is on the same line is the important thing since my anotated graphics.c is not that way....
14:08:40   --> jdandr2 (~jdandr2@12-222-211-55.client.insightBB.com) has joined #tux4kids
14:08:49 <cal> ask him
14:08:53 <jdandr2> hi guys...
14:08:58 <jdandr2> anything new?
14:09:12 <bombastic> <jdandr2@uky.edu>
14:09:20 <bombastic> oh, hi :)
14:10:19 <cal> Jess I was gnna ask you somthin but you took off and now I forget
14:10:39 <jdandr2> was it related to cvs or memleaks or ttf?
14:10:39 <criswell> hey Jesse... thanks Jake (I'm editting the chatlogs to possibly place them online)
14:11:17 <criswell> BTW, sorry to interupt, but there was some interesting stuff in the chats today... could I post them online? (Oh, they did work afterall ;-)
14:11:47 <jdandr2> Sam: I don't see any reason why not ...
14:12:15 <jdandr2> Sam: I am going to try to get the dev version from cvs right now...
14:12:53 <criswell> jdandr2: okay, its the default branch (i.e., you shouldn't need to do anything different from the instructions on the sf.net page)
14:13:08 <criswell> the stable branch, on the other hand, is more tricky ;-)
14:13:19 <cal> jdandr2: yes... I'm havin a prob getting step3 to compile with my stuff upchucks on line 110 globals.c in titlescreen.c
14:13:27 <bombastic> sam: it's not that bad
14:14:02 <jdandr2> cal: ok... I probably know why...
14:14:07 <cal> jdandr2: I'll tar it up...
14:14:08 <jdandr2> cal: did you just use my playgame.c
14:14:09 <jdandr2> ?
14:14:17 <cal> yup...
14:14:17 <jdandr2> or did you include other things?
14:14:31 <jdandr2> ok. I had to add a few #defs and other things to func.h & globals.h...
14:14:32 <cal> step two work'd fine
14:14:34 <jdandr2> let me go look
14:15:15 <cal> jdandr2: hang on let me send it so were on the same page...
14:15:22 <jdandr2> k
14:15:49 <jdandr2> cal: add the following to globals.h...
14:16:02 <jdandr2> ... #include "SDL_ttf.h"
14:16:15 <jdandr2> ... #define ttf_font "FreeSansBold.ttf"
14:16:23 <jdandr2> ... #define ttf_font_size 20
14:16:35 <jdandr2> I think that is all the changes besides playgame.c I made...
14:19:02 <bombastic> jesse: when will these things be up in cvs? i'm anxious to try this out and havent downloaded it yet :)
14:19:28 <jdandr2> As soon as I get the changes from cal (he is working on integrating our changes) and then I will upload them... Within a few hours I think...
14:19:29 <jdandr2> ;)
14:19:38 <bombastic> awesome
14:20:32 <bombastic> sam: can i send you a copy of the bug submission policy for you to check it out beforehand?
14:21:19 <jdandr2> cal: I assigned the "pronounciation of letters" to you on sf.net since you expressed interest in it (this doesn't mean anything, but I would like users to know it is something that we are working towards... I asssigned the i18n to me since I am working on unicode & ttf)
14:21:33 <jdandr2> jake: how are things going with you?
14:22:00 <bombastic> jesse: finals are over, so i cant complain
14:22:16 <criswell> bombastic: actually that would be great. remember that not all of the bugs will be submitted through cvstrac... some projects (eg tuxtype & tuxmath) still have bugtracking elsewhere
14:22:20 <cal> jdandr2: good idea!
14:23:07 <bombastic> jesse: next semester I only have one core class left, and three generals... so my last semester should be a breeze
14:23:09 <jdandr2> some graphics notes... I have noticed a few stray yellow pixels on the tux jumping screen...
14:23:25 <jdandr2> jake: thats nice! My last semester of undergrad was like that...
14:23:37   --- You have new mail (1 messages, 2912 bytes total).
14:23:40 <criswell> jdandr2: jumping screen? is that what I'm making new anim for?
14:24:07 <jdandr2> Sam: no (unless you want to ...) the jumping is when you win... (tux jumps as the congrats pops up)...
14:24:25 <bombastic> i just hope i can find a job when i'm done... HP (in interned there a year ago) closed down the place i was at
14:24:27 <cal> jdandr2: those cuts and pastes for globals.h are already in there...
14:24:38 <jdandr2> Sam: I had asked for Tux juggling when the game is paused.. then when the game is unpaused he swallows the fish ... ;)
14:24:44 <criswell> jdandr2: oh, I see.
14:24:58 <jdandr2> cal: I will see if I can find anything when I get it ;)
14:25:04 <criswell> jdandr2: actually i'm doing a couple of animations... you can pick whichever you want (or use them all randomly)
14:25:05 <jdandr2> 76%
14:25:18 <criswell> jdandr2: I have one of him break dancing ;-)
14:25:30 <jdandr2> Sam: cool.. I really like the animations we have and think adding more will be awesome!
14:25:48 <jdandr2> Sam: I was thinking it would be cool to have him dancing sometimes when he wins (doing various funny stuff!)
14:25:50 <cal> !!! now we juggle !! yea right!!! is it tux Sam was thinking of or himself!!!
14:25:54 <criswell> jdandr2: I could also add more frames to what we have if we ever needed them (I wont work on them until we need 'em)
14:26:01 <cal> juggling his work!
14:26:36 <criswell> jdandr2: I actually have a discarded animation from tuxmath where he does on of those NFL touchdown dances.. you want it?
14:26:43 <jdandr2> yes!!!
14:26:46 <jdandr2> hehe
14:26:57 <jdandr2> any animations you make would be greatly apreciated!
14:27:03 <criswell> i'll need to go through my backup disks, as its from my old desktop
14:27:15 <jdandr2> I think having a collection of different "congrats" animations that are randomly choosen would be great
14:27:27 <cal> post it somewhere Sam!
14:27:32 <criswell> jdandr2: okay. I'm going to be placing things in a cvs repository on the new dev box.. I just haven't yet
14:28:04 <jdandr2> cal: Do I just need to copy the data, image directory to what you sent me?
14:29:01 <jdandr2> cal: didn't you have some new images ???
14:29:14 <cal> yes but for the time being don't forget to copy in back.png and the extra menu items 1_5 2_5 3_5
14:29:50 <cal> jdandr2: need them?
14:29:57 <jdandr2> I think I have them somewhere...
14:30:09 <cal> jdandr2: I can send em
14:30:12 <jdandr2> sure..
14:30:14 <jdandr2> that would work
14:30:18   <-- bombastic has quit (Remote closed the connection)
14:30:52   --- jdandr2 has changed the topic to: Life is what is between coding & sleeping
14:31:34 <criswell> if you guys re-write anything more general than it originally was (i.e., it can be lifted and used in other projects) then I'd like to include it in a code-snippet repository I have on the dev-box
14:31:59 <jdandr2> Sam: eventually the fish falling thing may be general enough...
14:31:59 <criswell> (for example, if you re-write the menu system so it can be used elsewhere, that would be a keen thing to include)
14:32:22 <criswell> jdandr2: great. I'll get you guys write access to sub-dirs in this new repository
14:32:42 <cal> Huh?
14:32:43 <jdandr2> Sam: we are (eventually) switching to using SDL_ttf to generate the menus so there will be easy i18n...
14:32:54 <criswell> that would be wonderful
14:33:18 <jdandr2> cal: what do I need to type to get the new make thing to work??? (I will write it down this time...)
14:33:40   --- You have new mail (1 messages, 125192 bytes total).
14:33:41 <cal> jdandr2: cr: a nice generic keyboard routine would've helped me!
14:33:41   --> bombastic (~bombastic@66-35-162-47.deltacom.net) has joined #tux4kids
14:33:52 <bombastic> sorry... stupid school windows machines
14:34:01 <jdandr2> np
14:34:32 <cal> hey Jake did you paly with my latest win bin yet???
14:35:05 <bombastic> the windows one? no. I dont have a windows box myself... i'm at the school library now
14:35:11 <bombastic> i can try it now, brb
14:35:30 <cal> jdandr2: you must mean make it screw up..
14:35:56 <criswell> bombastic: if you're at U of A main, you wont be able to (they have them locked down severely)
14:36:05 <cal> all I did was ./configure && make
14:36:34 <bombastic> sam: youre right. have you finished pas 272 upgrade?
14:36:59 <criswell> bombastic: no, that's a better idea, just head over there. use machines 1-15 (they still have 98 on them)
14:37:05 <cal> Sam your the sys admin so that would be "I have them"\
14:37:19 <jdandr2> cal: I got back.png what are the other files I need?
14:37:52 <criswell> cal: actually, I'm only over the physics dept. The library is another storry
14:38:06 <bombastic> sam: will the building be locked up
14:38:09 <bombastic> ?
14:38:26 <criswell> bombastic: probably...
14:39:06 <jdandr2> cal: add the line #include <SDL/SDL_ttf.h> to the globals.h ...
14:39:14 <cal> just cp menu1_4.png to menu1_5.png menu2_5.png menu3_5.png
14:39:41 <criswell> jdandr2: just want to mention that <SDL/SDL_ttf.h> isn't portable... so only do this temporarily ;-)
14:40:08 <bombastic> brb... moving to PAS 272 (and sam's hackable windows machines :)
14:40:15   <-- bombastic has quit ("Leaving")
14:40:16 <jdandr2> criswell: cal & I were discussing that... I wasn't sure ... Should it just be SDL_ttf.h and have the right Includes..
14:40:42 <jdandr2> cal: Also I noticed that the makefile isn't linking to SDL_ttf (I am getting linking errors)...
14:40:48 <criswell> it should be #include "SDL_ttf.h" and have the paths determined in the makefiles or configure script
14:41:02 <jdandr2> cool... We will get it set up like that...
14:41:37 <cal> jdandr2: line 116...
14:41:50 <cal> add -lSDL_ttf
14:41:51 <criswell> jdandr2: see http://www.libsdl.org/faq/FAQ-General.html#GENERAL_INCLUDE
14:42:30 <jdandr2> I am still getting link errors... I have to see why...
14:42:47 <jdandr2> oh... I added -L not -l ...
14:42:50 <cal> jdandr2: but then I thought I did that!
14:43:30 <jdandr2> well I have it running, but it is VERY slow in the menu section!!! (VERY !!!)
14:43:44 <jdandr2> descent speed in the game though...
14:44:03 <cal> jdandr2: scuse me thats line 114
14:44:11 <jdandr2> I got it... I have it running now
14:44:20 <cal> jdandr2: what'd you change...
14:44:22 <jdandr2> I didn't run into any problems..
14:44:30 <cal> ughh
14:44:38 <jdandr2> all I added was #include <SDL/SDL_ttf.h> to the globals.h
14:45:00 <cal> slow on the menu is the 30 hz thing...
14:45:17 <jdandr2> cal: I don't think I am getting 30hz ... (is there a way to see???)
14:45:26 <cal> jdandr2: why would that be needed
14:46:13 <jdandr2> because on line 141 of globals.h we have TTF_Font *font
14:46:33 <jdandr2> thus we need to include the library for ttf fonts in the section where we are including sdl_image, sdl_mixer...
14:47:01 <jdandr2> cal: I am going to check out mem leaks on it now...
14:47:05 <cal> jdandr2: to see at full speed comment out sdl_delay at end of loop (just before last SDL_UpdateRect()
14:47:17 <criswell> [OT] I will be leaving for lunch soon, but I will keep my session open for logging purposes
14:47:43 <jdandr2> Sam: have a good one...
14:47:46 <cal> criswell: thanks Sam
14:48:59 <criswell> (I'm not gone yet... my wife's going to pick me up ;-)
14:49:56   --> bombastic (~bombastic@66-35-162-47.deltacom.net) has joined #tux4kids
14:50:20 <bombastic> sam: the building was open.. there's something going on in the big classroom
14:50:45 <jdandr2> cal: I am getting: 5080 5936 6240 6568 from going into key cascade and then leaving... I haven't looked into where the leaks are... Do you have any ideas (I think we aren't clearing the font when we are done using it... that would be a little of it.)
14:50:46 <criswell> bombastic: rilly? hmmm... anyone in 272
14:50:59 <bombastic> sam: nope, its dead
14:51:14 <bombastic> cal: where is your windows binary? i get a file not found
14:52:37 <criswell> okay, I'm off... I'll clean up everyone's ip info from this chat log and post it tonight.... see yez
14:52:44 <jdandr2> looks like it is tux4kids/~cal../current/Tuxtype.zip
14:53:00 <bombastic> thanks
14:53:26   * criswell is away: Out to lunch....
14:54:20 <cal> jdandr2: yes have you updated for curlev and pause_img
14:54:46 <cal> those are the big ones...
14:55:03 <jdandr2> cal: curlev (what was that image again?)
14:55:38 <bombastic> hey images arent in this :/ ill get them from the last stable release
14:56:12 <jdandr2> Jake: cal doesn't have the luxury of a high speed so you will need to get them from stable...
14:56:24 <cal> bomb:I only up'd new images...
14:57:04 <jdandr2> cal: so we need to add the pause_img free stuff to freegame() right...
14:58:41 <cal> jdandr2: look at where we free images in playgame.c (I don't know where in your version line 743 in stable) need to freesurface(curlev) and free pause_img[i]
14:59:14 <jdandr2> cal: cool. I added the freesurface pause_img ones.
14:59:21 <bombastic> cal: this binary goes very slow compared the older one.
14:59:22 <jdandr2> cal: adding the curlev.
14:59:30 <jdandr2> jake: in just the menu or the game itself?
14:59:48 <bombastic> cal: hang on, I didn't try the game
15:02:01 <jdandr2> cal: I am still getting 800k 400k ... for the mem leaks each access...
15:02:02 <bombastic> the game itself seems fine... but the menu is very slow
15:02:16 <jdandr2> Jake: I hit the same thing.. we will have to do some more tweaking...
15:02:18 <cal> bombastic: yes I slowed it down for 3 reasons 1 dizziness! 2 cpu usage 3 so it'd be same across cpu's 100mhz 200 mhz 600mhz 2ghz
15:02:23 <bombastic> cal: why does the background not scroll anymore during startup?
15:02:33 <jdandr2> cal: It does for me ...
15:02:44 <jdandr2> I meant Jake: it does for me...
15:02:58 <bombastic> cal: it really is much slower (i think its too slow)
15:03:10 <cal> bombastic: 486 couldn't handle it
15:03:39 <jdandr2> we need to do screen updates the same way we do them in the game (so that it is about the same speed regardless of cpu)...
15:03:45 <bombastic> but it can be sped up a little, right?
15:04:13 <bombastic> jesse: we need to ask sam about that, but i dont think we can do dirty-blits on the title screen
15:04:16 <jdandr2> the menu is WAY to slow on faster computers (<10 frames a second... very choppy)... But it does work great on slower... We just need to get it working on both of them...
15:04:26 <jdandr2> Jake: what is a dirty blit?
15:04:37 <cal> bombastic: What op system do you have personally (I realize your test win right now)???
15:04:43 <bombastic> jesse: its the blitting method used in the game
15:04:50   --- You have new mail (1 messages, 3813 bytes total).
15:05:02 <bombastic> cal: i have a redhat 7.3 system now (but its at my apt)
15:05:35 <jdandr2> Jake: did you you notice the memory usage (Cal got it down to 5M -- used to be 20M!!!)
15:05:54 <bombastic> dirty blit is when you only blit small squares on the sreen, instead of the hole screen
15:06:03 <bombastic> i didnt see that.. how do i check in windows?
15:06:38 <cal> bombastic: the point of the slowness is not the speed the menu goes around at (that is configurable in the game where I have slowed it down is the actual framerate)
15:06:40 <jdandr2> I think in the start->programs->accessories->system something
15:07:34 <bombastic> sam must have it disabled on these machines
15:07:43 <cal> you have to yuse taskinfo or norton or whatever
15:08:09 <jdandr2> Jake: do you live where Sam lives??
15:08:17 <bombastic> in tucson, yes
15:08:24 <bombastic> i go to the u of a also
15:08:40 <jdandr2> Did you meet him before or after you worked on TT?
15:08:58 <bombastic> so does two other developers who helped out while ago
15:09:11 <bombastic> after tt. he was working at intel when i started helping out
15:09:27 <bombastic> so he was in aother state
15:09:45 <jdandr2> that is still interesting...
15:10:15 <bombastic> actually, i woriginally helped out on noink because i wanted it for my web site.... he roped me into tux typing
15:10:47 <jdandr2> cal: in titlescreen.c around line 677 ... what are those lines for?
15:10:52 <cal> bombastic: well worth the rope!
15:12:15 <bombastic> cal: does the m
15:12:15   <-- bombastic has quit (Remote closed the connection)
15:12:52 <cal> jdandr2: are we on the same page ? 677 is the 3rd last line and is Sams comment???
15:13:20 <jdandr2> sorry... 646
15:14:08 <cal> if we are its Sams note about The font he used in gimp (size and color to create menu's)
15:15:13 <jdandr2> line 646: while ((SDL_GetTicks()- start) < 33 ){
15:15:26 <cal> jdandr2: lines setup the keyboard (menuitem) processing
15:15:55 <jdandr2> line 646-648:
15:15:57 <cal> pressed is the returned value from handleinputs
15:16:01 <jdandr2> while ((SDL_GetTicks()- start) < 33 ){
15:16:04 <jdandr2> SDL_Delay(2);
15:16:07   --> bombastic (~bombastic@66-35-162-47.deltacom.net) has joined #tux4kids
15:16:08 <jdandr2> }
15:16:10 <bombastic> stupid windows
15:16:20 <jdandr2> when I remove those lines I get great framerate on the menu
15:16:39 <bombastic> cal: does the menu have to be in that order? casn we put options up one or two?
15:17:59   <-- bombastic has quit (Remote closed the connection)
15:18:00 <cal> jdandr2: what you just pasted boils down to "hey if 1/30 th of a second hasn't passed yet then wait a moment)
15:18:26 <cal> it is the frame rate deal
15:18:35 <jdandr2> hmm...
15:19:19 <jdandr2> does GetTicks ever loop?
15:19:45 <cal> bo: yeh its there just cause I was more worried bout what I had to do to get all the yellow dots out
15:19:54   --- You have new mail (1 messages, 3101 bytes total).
15:20:08 <jdandr2> cal: I noticed that it loops after 49 days... so I think we are alright...
15:20:47 <cal> jdandr2: yeah but it takes days so...
15:21:35 <jdandr2> somehow those lines are making me only get ~10 frames a second...
15:22:05 <cal> I've actually left it running for 24 hours just to see if mem usage would increase over time and it worked flawlessly
15:22:24 <jdandr2> cool
15:25:34 <cal> jdandr2: I don't know what your calling 10fps if it's whats being printed on stdout ignore it it wrong... hawever the point here is we don't up date the screen until a time value ie the "33" or 33 milliseconds
15:26:17 <jdandr2> cal: I am guessing since it is VERY slow...
15:26:27 <jdandr2> tux blinking takes 3 seconds
15:27:04 <cal> jdandr2: how fast (mhz) is your system
15:27:33 <jdandr2> 500mhz G3
15:28:30 <cal> hang on a min...
15:28:34 <jdandr2> no prob
15:31:44 <cal> tux blinking takes 3 seconds ??? is this from the start of a blink to the finish of that same blink or start of one blink to start of next blink?
15:31:57 <jdandr2> yes
15:32:04 <jdandr2> no
15:32:06 <jdandr2> hold on
15:32:19 <cal> !!!! ok