Timestamps are in GMT/BST.
| 01:15:00 | | Watusimoto_ has joined |
| 01:16:00 | raptor | looks like someone left their IRC client on at work... |
| 01:16:00 | | Watusimoto Quit (Ping timeout: 252 seconds) |
| 02:00:00 | raptor | 1.79 x 10^12 furlongs per fortnight |
| 05:44:00 | raptor | zoomber_ibm: I hate issue 124 |
| 05:44:00 | raptor | (coding it, at least...) |
| 05:45:00 | | Watusimoto_ Quit (Ping timeout: 244 seconds) |
| 05:46:00 | raptor | I have tried to code it twice now, and I'm still unhappy with my partially finished solution |
| 05:52:00 | sam686 | zoomber_ibm's idle time: 4d 2h 20m 28s (i think zoomber is idling a long time now...) |
| 05:53:00 | raptor | i wonder if he has his laptop on IRC and left for vacation |
| 05:53:00 | sam686 | i think zoomber has 2 computer, laptop and ibm desktop with hackintosh, i think... |
| 05:55:00 | sam686 | could be in vacation, possibly, and forgot to turn off computer maybe... |
| 05:55:00 | raptor | brb |
| 05:55:00 | | raptor Quit (Remote host closed the connection) |
| 05:58:00 | | raptor has joined |
| 05:58:00 | | ChanServ sets mode +o raptor |
| 05:59:00 | raptor | sorry, laptop hardware failure |
| 05:59:00 | raptor | mor elike buggy firmware |
| 05:59:00 | sam686 | my guess is graphics problem? or what? |
| 05:59:00 | raptor | the IRQs on my laptop act up and will randomly disable |
| 06:00:00 | raptor | usually that means wireless goes out, but lately it has messed up the keyboard |
| 06:00:00 | sam686 | laptop getting old? |
| 06:00:00 | raptor | nope, i think it shipped with buggy hardware |
| 06:00:00 | raptor | it's my work laptop: dell e6510 |
| 06:01:00 | sam686 | does bumping or shaking the laptop cause errors, or does it just happen randomly? |
| 06:02:00 | raptor | just happens randomly |
| 06:02:00 | raptor | no physical trauma required |
| 06:02:00 | raptor | :) |
| 06:03:00 | sam686 | maybe list all of your hardware devices? |
| 06:04:00 | raptor | well, i'm on linux, and i consistently get an IRQ timing error in the kernel messages |
| 06:04:00 | sam686 | does it show whick IRQ or anythign specific? |
| 06:05:00 | raptor | yes, it does, but it changes |
| 06:05:00 | raptor | i am hoping dell will release a BIOS update - many of my coworkers have similar problems |
| 06:06:00 | sam686 | keyboard stops working problems as well? |
| 06:06:00 | raptor | well... |
| 06:07:00 | raptor | that has only started happening when I added the kernel boot parameter 'irqpoll' |
| 06:07:00 | raptor | but all the other problems went away |
| 06:07:00 | raptor | irqpoll is supposed to work around buggy firmware with IRQ problems |
| 06:08:00 | raptor | oh wow, they did release a new BIOS |
| 06:10:00 | raptor | i'll have to try it and report back tomorrow |
| 06:12:00 | raptor | i'm gonna try something crazy - update my DVD firmware from a windows VM in linux :) |
| 06:13:00 | sam686 | i don't think a virtual maching have direct access to DVD firmware (not sure) |
| 06:13:00 | raptor | i don't think so either - but I'm gonna see what happens |
| 06:15:00 | raptor | oh my goodness, it worked!! |
| 06:16:00 | sam686 | well, then i guess that virtual machine software lets windows have direct access to dvd drive... |
| 06:17:00 | raptor | yeah, i'm surprised |
| 06:18:00 | sam686 | but, dvd firmware probably won't fix computer problems (maybe it might fix problems related to DVD drive) |
| 06:19:00 | raptor | no it won't - but i saw an update for it |
| 06:21:00 | sam686 | maybe your computer have a problem with one of a device sending junk irq or something, or it might be drivers problems... |
| 06:21:00 | sam686 | probably software drivers problems if it happens to many computer of the same computer.. |
| 06:22:00 | raptor | i don't htink it is drivers problem because we all run different OSes (some openSUSE 11.3, 11.4, Windows 7) |
| 06:23:00 | raptor | in fact, usually OEMs work around the hardware problems they fix with better software drivers for windows - which means us linux users are stuck |
| 06:24:00 | sam686 | so, does the windows ever blue screens for you on computer? |
| 06:24:00 | | koda has joined |
| 06:26:00 | sam686 | which drivers was updated that have the fix, adn is it possible to disable that driver? |
| 06:26:00 | raptor | i have no idea - i dual boot windows 7 on this laptop, but i only use windows once every few weeks |
| 06:27:00 | raptor | no blue screens ever |
| 06:27:00 | raptor | never had wireless problems on windows |
| 06:32:00 | raptor | can i show you my ugly hack for issue 124? |
| 06:32:00 | sam686 | ok.. |
| 06:32:00 | raptor | http://pastie.org/2766184 |
| 06:32:00 | raptor | so ugly... |
| 06:32:00 | raptor | this is one of the worst hacks i've written in a long time... |
| 06:33:00 | raptor | i am even ashamed |
| 06:34:00 | raptor | this hack is what happens when I code late at night... |
| 06:34:00 | sam686 | what happens if a line gets too long (one player zaps 200 robots)? |
| 06:34:00 | raptor | it is using method drawWrappedText |
| 06:34:00 | raptor | it just doesn't show... |
| 06:35:00 | sam686 | the problem is a long too long may overflow mDisplayMessage array from using strcpy |
| 06:35:00 | raptor | oh yeah, forgot about that... |
| 06:35:00 | raptor | 2048 is the limit i think |
| 06:38:00 | sam686 | one problem with zapped messages is when there is like 20 players, you only have less then 1 second to read them, when every players are zapping.. |
| 06:38:00 | raptor | yes |
| 06:39:00 | sam686 | maybe in a non-bitmatch (like CTF flag dropped messages) maybe just ignore all zap messages unless it has your name in it.. |
| 06:39:00 | raptor | this one takes into account the message length: http://pastie.org/2766213 |
| 06:41:00 | | koda Quit (Quit: koda) |
| 06:43:00 | sam686 | i guess never mind about buffer overflow, .c_str() : message, sizeof(mDisplayMessage[0])); // Use strncpy to avoid buffer overflows |
| 06:44:00 | sam686 | but still, without that fix, that line will just get cropped when long enough.. |
| 06:44:00 | raptor | yeah |
| 06:46:00 | raptor | i hate this hack |
| 06:46:00 | raptor | i think i'm going to go to bed... |
| 06:46:00 | raptor | good night sam686 |
| 06:48:00 | sam686 | ok, i think combining multiple messages into one zapped message can make messages get overcrouded (too many text) i think... |
| 06:49:00 | raptor | i think so too |
| 06:49:00 | sam686 | i can show you one screenshot of my testing it (in 60 seconds) |
| 06:50:00 | raptor | ok |
| 06:53:00 | sam686 | http://208.107.52.15/bitfighter/111029screenshot_21.png |
| 06:54:00 | sam686 | while it slows down messages, it does seem to get more crowded.. |
| 06:54:00 | raptor | yes, i agree |
| 06:55:00 | raptor | was it Zap! that had this implemented? |
| 06:55:00 | sam686 | and, I don't think players care about seeing who zapped who, only care about you zapped someone or someone zapped out? |
| 06:55:00 | sam686 | yes, but old Zap had only one line of who zapped who, who, who |
| 06:55:00 | raptor | i think it was a dedicated line at the top, wasn't it? |
| 06:55:00 | sam686 | probably yes.. |
| 06:55:00 | raptor | because that is something we could do, too |
| 06:56:00 | raptor | although I am starting to think that we are getting little benefit from so much work... |
| 06:56:00 | raptor | i don't really want to push down server messages |
| 06:57:00 | sam686 | it is something to think about over night, as that seems not right... |
| 06:57:00 | raptor | yep |
| 06:57:00 | raptor | maybe we can ask watusimoto in the morning |
| 06:57:00 | raptor | ok good night sam686, i'm falling asleep |
| 06:57:00 | sam686 | ok, night. |
| 06:57:00 | | raptor Quit (Remote host closed the connection) |
| 07:09:00 | | kodax has joined |
| 07:30:00 | | sam686 Quit (Ping timeout: 258 seconds) |
| 07:30:00 | | sam686 has joined |
| 07:30:00 | | ChanServ sets mode +v sam686 |
| 10:14:00 | | sam686 Quit (Ping timeout: 258 seconds) |
| 10:15:00 | | sam686 has joined |
| 10:15:00 | | ChanServ sets mode +v sam686 |
| 10:36:00 | | Watusimoto has joined |
| 11:07:00 | | Watusimoto_ has joined |
| 11:07:00 | | Watusimoto Quit (Ping timeout: 240 seconds) |
| 12:02:00 | | Watusimoto_ Quit (Ping timeout: 240 seconds) |
| 12:14:00 | | Watusimoto has joined |
| 12:54:00 | | kodax Quit (Remote host closed the connection) |
| 13:13:00 | | Watusimoto Quit (Ping timeout: 252 seconds) |
| 13:19:00 | | kodax has joined |
| 13:54:00 | | raptor has joined |
| 13:54:00 | | ChanServ sets mode +o raptor |
| 14:25:00 | | raptor Quit (Remote host closed the connection) |
| 16:19:00 | | Watusimoto has joined |
| 16:59:00 | | kodax Quit (Remote host closed the connection) |
| 17:03:00 | karamazovapy | hah! QuickWeb just added this checkbox to its support tickets: |
| 17:03:00 | karamazovapy | I agree to be billed and pay the cost of work performed if the support request/problem is found to be because of my own fault or lack of linux skills which otherwise I could haven done on my own |
| 17:04:00 | | kodax has joined |
| 17:09:00 | | BFLogBot - Commit df1ea2c9a8f7 | Author: watusim...@bitfighter.org | Log: UI Framework for team shuffle |
| 17:13:00 | | kodax Quit (Remote host closed the connection) |
| 17:13:00 | | kodax has joined |
| 17:19:00 | | BFLogBot - Commit 73847001eba3 | Author: watusim...@bitfighter.org | Log: Hook up /shuffle command |
| 17:27:00 | | Watusimoto Quit (Ping timeout: 260 seconds) |
| 17:37:00 | | kodax Quit (Ping timeout: 248 seconds) |
| 18:08:00 | | raptor has joined |
| 18:08:00 | | ChanServ sets mode +o raptor |
| 18:08:00 | raptor | good day! |
| 19:14:00 | | Watusimoto has joined |
| 19:19:00 | | Watusimoto Quit (Ping timeout: 258 seconds) |
| 19:21:00 | | LordDVG has joined |
| 19:49:00 | | LordDVG Quit (Ping timeout: 240 seconds) |
| 19:49:00 | raptor | watusimoto come back! |
| 19:52:00 | | LordDVG has joined |
| 20:15:00 | | Watusimoto has joined |
| 20:19:00 | | koda has joined |
| 20:20:00 | raptor | hi Watusimoto |
| 20:20:00 | raptor | I think I wrote the hack-iest i've ever written last night for issue 124 |
| 20:21:00 | raptor | but we now know what the behaviour would kind of look like: http://208.107.52.15/bitfighter/111029screenshot_21.png |
| 20:21:00 | Watusimoto | hi |
| 20:21:00 | Watusimoto | glad you are so proud of your work |
| 20:21:00 | raptor | i am ashamed |
| 20:21:00 | Watusimoto | good lord |
| 20:22:00 | raptor | if you think that picture is bad, look at the code: http://pastie.org/2766213 |
| 20:22:00 | Watusimoto | ummm.... not sure what to say |
| 20:22:00 | Watusimoto | that's pretty appalling |
| 20:22:00 | Watusimoto | well at least the code's on 45 lines long |
| 20:23:00 | Watusimoto | that's short enought to grok and to rewrite sometime in the future |
| 20:23:00 | Watusimoto | but the question is what are we going to do about that screenshot |
| 20:23:00 | raptor | yep |
| 20:23:00 | raptor | the results are kind of bad |
| 20:24:00 | raptor | sam686 and I think that Zap! had a dedicated line at the top of the messages just for 'kill' messages |
| 20:24:00 | raptor | but we have module indicators there... |
| 20:25:00 | raptor | and I'm not sure I want to push server messages down a line just for this |
| 20:25:00 | raptor | this |
| 20:25:00 | raptor | this horrific monstrosity that I wrote |
| 20:28:00 | Watusimoto | I don't object to the code so much as the screenshot |
| 20:28:00 | Watusimoto | maybe we just revert and close the case |
| 20:28:00 | raptor | really? i'm appalled I even wrote that |
| 20:28:00 | Watusimoto | I'd call that a success |
| 20:28:00 | raptor | made feel all dirty inside - like I was programming PERL |
| 20:29:00 | Watusimoto | the only way I can think to save it would be to change the messages to S_Bot killed sam686 12 times |
| 20:29:00 | raptor | well, if it's a large bitmatch, that won't work |
| 20:29:00 | raptor | lots of player names in a row... |
| 20:29:00 | raptor | different names, i mean |
| 20:30:00 | Watusimoto | right, but at least it won't look so idiotic |
| 20:30:00 | Watusimoto | no offence |
| 20:30:00 | raptor | haha |
| 20:30:00 | raptor | i completely agree |
| 20:30:00 | Watusimoto | s_bot killed sam686 (12 times), watusimoto (2times) and raptor |
| 20:31:00 | raptor | what i meant was, Watusimoto killed raptor, sam68, karamazovap, BFLogBo, zoomber_ib, LordDV, kod |
| 20:31:00 | raptor | so lots of single kill different names |
| 20:31:00 | Watusimoto | Watusimoto killed raptor, sam68, karamazovap, BFLogBo, zoomber_ib, LordDV, and koda |
| 20:32:00 | Watusimoto | Watusimoto killed raptor, sam68, karamazovap, BFLogBo, zoomber_ib, LordDV, and then koda |
| 20:32:00 | raptor | (i had removed the last character to not alert them...) :) |
| 20:32:00 | Watusimoto | oops |
| 20:32:00 | Watusimoto | Watusimoto killed raptor, sam68, karamazovap, BFLogBo, zoomber_ib, LordDV, and then kod |
| 20:32:00 | Watusimoto | sorry kod |
| 20:32:00 | Watusimoto | a |
| 20:32:00 | koda | 'lo |
| 20:33:00 | Watusimoto | just usng your name in vain |
| 20:35:00 | raptor | sooo... I could add even more text processing to try and reduce the messages... but i really don't want to |
| 20:35:00 | raptor | i'm sure I slowed down the displayMessage method by a magnitude already... |
| 20:35:00 | koda | i feel abused D: |
| 20:36:00 | Watusimoto | ah heck, it's all client side\ |
| 20:36:00 | Watusimoto | so... revert? |
| 20:38:00 | | LordDVG Quit (Remote host closed the connection) |
| 20:40:00 | raptor | if we were to take ratio of good/bad of this enhancement would it be > 1 or < 1? |
| 20:41:00 | Watusimoto | < 1 |
| 20:41:00 | raptor | thenr evert |
| 20:41:00 | raptor | then revert |
| 20:41:00 | Watusimoto | If you think the idea has no future, and want to throw in the towel, i'll back you. You can revert your code, add a comment to the case, and close it with "won't implement". to badd there's no "we tried it and it sucks" status. |
| 20:41:00 | Watusimoto | not every idea is a good idea |
| 20:41:00 | Watusimoto | even if they sound good |
| 20:41:00 | raptor | i can actually create those statuses (statii?) |
| 20:42:00 | Watusimoto | can you? |
| 20:42:00 | Watusimoto | that might be a good one to have |
| 20:42:00 | raptor | which one? |
| 20:42:00 | Watusimoto | we tried it and it sucks |
| 20:42:00 | Watusimoto | there's already a won't implement |
| 20:46:00 | raptor | http://code.google.com/p/bitfighter/issues/detail?id=124 |
| 20:47:00 | raptor | Is that status OK for you? ^^ |
| 20:48:00 | raptor | I actually didn't commit my code changes - I was too ashamed |
| 21:38:00 | Watusimoto | perfect |
| 22:31:00 | | raptor Quit (Remote host closed the connection) |
| 22:37:00 | | raptor has joined |
| 22:37:00 | | ChanServ sets mode +o raptor |
| 22:38:00 | raptor | thing learned today - don't let your computer run for a week without restarting after updating the graphic system libraries... |
| 22:55:00 | | BFLogBot - Commit 00f16bb3e1db | Author: watusim...@bitfighter.org | Log: Rearrange code a tiny bit |
| 22:55:00 | | BFLogBot - Commit 43b573df1a72 | Author: watusim...@bitfighter.org | Log: Made helper menus lazily initialized. Not sure if this is really a good thing, but I just couldn't bear to create a teamShuffleHelper for players who may never use it. Just couldn't bear to do it. |
| 23:22:00 | | Watusimoto Quit (Ping timeout: 258 seconds) |
| 23:52:00 | | raptor Quit (Remote host closed the connection) |
