Quote from morpha :

Perhaps some gifted regular expression expert can find a way to achieve this with preg_split() which would certainly be the most efficient approach.

That's what I was thinking, where's filur when you need him?

Quote from Dygear :

But I first have to get to that point with PRISM.

And I guess that point is now, but I think it will ship with LFSWorldSDK first, and then PRISM later on. Thining of calling the whole thing like LFS DataType or something, but each class will be like LFSTime, LFSString, LFSWhatEver.

I was working on Krammeh's bug report about MST/MTC/MSX Colors breaking in strings that span multiple lines. I'm not one to duck the hard questions, and this one did cause me quite some time to think through. The only conclusion I've come to is that much of PRISM is going to need to be rewritten to handle strings correct in these cases. I now feel that the best way to handle LFS strings is to make each LFS Datatype; Time, String, ect; into it's own class that will be handled and parsed at the packet level and thus make it available on all levels. This idea was one that I had for version 2.0 of LFSWorldSDK, so I might just prototype the system there and move it into PRISM when it's done. But is there an easier way, am I missing something that would allow me to do this without having to rewrite much of the packet system?

Quote from DavidTiger :

I got around this by reading the RPM values directly from memory, Makes it a little harder to update because the location of this value changes with every patch. Very easy to find so its not too much of a problem.

Really! Reading RPM values directly from memory. Now this I'm very interested in as it was the basis for how AMX Mod worked for Counter-Strike. Source Mod thankfully had built in API controls for finding this information, but needed to be compiled against the latest source sdk version when there was an update, but I digress. Where is the RPM value, what's it's pointer location in the current patch?

*Sigh* Ok. I've been reading some bad things about the dell you posted. Seems that there happens to be quite a few dithering problems with the display.

Wow, that U2410 is stunning, but the ZR24W is quite a bit cheaper in most case (around $100). You say 120 Hz @ it's native 1920 x 1200? Can you find a source for this, I would be quite interested in both of these if this is true and if it is true I would buy one or the other as for me it would be worth it!

I went into the store around me to look at the screens and so far I was most impresssed by the HPs I've seen. They did not have any Dells, but I'll look around and see if I can find a place that stocks these ones you've posted here. I'm leaning toward the U2311H myself, it looks great and is Full HD at a pretty good price for an IPS display. The fact that I can VESA mount it is also a huge plus!

Yeah, I meant that it's much better then that, but I might be bias as I went from one of the hottest CPUs (In fact, I think it was the hottest ever) to one of the coolest CPUs. Crazy what 7 years does.