Yeah unfortuantely that's a basic rule in coding I was taught by my programming teacher, "one mistake will bring about the program ceasing to function". But @kiki..... Good job dude, you are obviously a pretty switched on guy and that's what we like around here, keep it up!
THEfog On 19/07/2010 9:22 PM, "AngelicTears" <[email protected]> wrote: lol,good idea there Kiki... it's good to see ppl giving out ideas ^^ hmm, although there are a few draw backs , the ideas that u present here is in fact good, but i have done some similar idea but somewhat different and ending up reconstruction the whole inf with error...and dead strings / splits....im not saying that it is a bad idea, i may be doing errors back then, and ur idea is perfectly organize... but still, if one string branch done with error, all strings connected to it will have error...(basic coding error) since Kiki make a point that organized inf lines will result a cleaner more easier to read the inf functions, then i will try to make it possible.. i try and redo the inf based on ur idea but i literally need u and if can the others to check the inf for errors and possible dead strings...there are thousands of lines in the inf itself ^^ gonna try and make up every lines in the inf first ^^ lol, i am too feels dizzy with words when starting with V1.2...no need to feel bad, it's ok to post ideas here... On Mon, Jul 19, 2010 at 5:36 PM, Kiki <[email protected]> wrote: > > if the INF will have some... -- Laptop: Acer Aspire Core Duo T2300E @ 1.67GHz Intel GMA 950 IGP Intel 945 Chipset 1GB RAM (512MB... -- 9xx SOLDIERS SANS FRONTIERS -- 9xx SOLDIERS SANS FRONTIERS
