Samapico

Good strategy. I'm too stupid to know how to use ignore.txt Corrected for ya, Ace. One or the other And ace stop showing off your SSC Forum Operator !@#$%^&*le in your custom !@#$%^&*le You mean his sig?

Hoch does that too

May I ask why a 'screenshot' of a text file is required? Anyway, I don't have an ignore.txt, for the same reason as Dav.

Not working completly yet

I lol'ed too

So your goal went from killing yourself to stop smoking? That's an improvemet... much better for your health too

A correct definition of visual lag would be that your eyes are too slow to see their position accurately.

If you don't give that man his link, I shall take away from you the points he donated

Who the !@#$%^&* decides that something is offensive for some people anyway? I'm pretty sure the concerned groups don't give a !@#$%^&*.

6wS5xOZ7Rq8http://www.youtube.com/watch?v=6wS5xOZ7Rq8

?

Are you saying that there are some command line arguments?

Really entertaining post... for some reason...

Lynx I'm halfway through that long !@#$%^&* post, and I'm enjoying it so far

I managed to get 10 points and I don't know how I kept shooting these bubbles, but what are they supposed to do?? Oh right... it's by doing exactly what I was trying to do and it wasn't doing anything... I SEE "A replica of the classic arcade game!" RIGHT!!! THAT GAME IS A CLASSIC! I'm deleting that piece of !@#$%^&* Really I froze in mid-air when dying just like Incomplete said

Keygens? False positives? I always wondered that... Few weeks ago, there were some keygens that were identified as threats, but when I used them like a year ago, they appeared fine to my antivirus. And I don,t seem to have been infected or anything; I always wonder if these are really threats or... dunno... I avoided using it anyway; and now when I use a keygen, I run it a few time and collect a couple of keys and put them in a .txt, so I don't have to run it again after a future reformatting, for example, just in case.

What's bubble bobble anyway?

oh... right... forgot about that Opening a second map from the explorer, I guess. Gotta fix that...

My bad, it's not part of continuum.. however, bots and server software use it. You use Vista? Maybe it's built-in or something. I dunno. But it uses these while importing and exporting lvz files: Private Declare Function compress Lib "zlib.dll" (dest As Any, destLen As Any, src As Any, ByVal srcLen As Long) As Long Private Declare Function uncompress Lib "zlib.dll" (dest As Any, destLen As Any, src As Any, ByVal srcLen As Long) As Long Which proves that the library is necessary Now if you need the file or not to have access to these library functions is another question, first time I encounter such thing. Can't find anything about this on Google... hmm... it wouldn't surprise me if it had it as internal library or something, zlib is what the .zip format uses (and the .lvz as well). If Vista can do that without zlib, then I could add a condition there, but I'd like to know exactly why you don't need it first. Oh, and you wasted more bandwidth complaining about it than if you had downloaded it And you probably have downloaded it already anyway, since it comes in the zip file. The splash screen... hmm didn't think about these. I actually had to fix this same problem for other pop-ups. And the thing in the LVZ manager, yeah I know about that, couldn't figure out why it wasn't working... Well I figured the problem, mostly, but no real solution. A workaround is when you click on the field and get the drop-down menu, check your taskbar there should be a new window with no name, click it, then you can choose something in the list... Basically, we have to use a little trick to be able to pop such a menu that can be larger than its container. We use the exact same method to drop down the Regions list in the Region tool's toolbar. A normal drop-down list would not be visible past the toolbar's height. But that one works there :/ Anyway, now that the LVZ selector works, I think it more efficient to change them with it (in most cases). Edit: just checked to be sure, I use XP and I do need zlib.dll; it doesn't crash, but the import process doesn't work at all.

If I wasn't in a good mood, I'd go on a (legitimate) banning spree... Seriously guys, can't you just find something else to do than cry like babies? Go outside, take a walk, shoot birds, masterbate, hit your head on a sidewalk, ANYTHING. You both are lucky to not being banned already, take a look at your warn level, and you'll understand that this won't be tolerated much longer. And you're old enough to know that REPLYING to !@#$%^&* is just as stupid and pointless, so "who started" is not even a question. Next ban(s) will be counted in weeks, if not months. :wave!@#$%^&*:

He started exactly 2 minutes after he posted; while watching Creemy's lolcat.

How else could you live a happy life anyway? DCME is your salvation

Some major improvements are coming that will cut down memory usage AND be more efficient... Basically, DCME has a couple of 1024x1024 boolean arrays; and booleans in VB6 are actually integers, which mean they take 2 bytes. I made a class that handles a boolean array with bytes, which cuts down memory usage by 2x. Additionnaly, we can do copy/move and set/reset operations MUCH quicker (pretty much instantly) using APIs such as CopyMemory and FillMemory (memcpy and memset equivalent in c++) I just added this to the eLVL regions. Each region now takes 1MB of memory instead of 2MB. (I also fixed a undo/redo problem in regions I noticed on the way) Drake was working on pushing this a bit further, by making a class that works with a field of bits. Technically, a single bit is enough for boolean values, and we could fit up to 8 booleans in one single byte. That means 8x less memory usage than my improvement (or 16x less than how it was before that). This technique is more complex, because when handling memory, you can only work with full bytes. So if you have a 32x32 array, and want to copy the values from 2,2 to 18,18; you have to copy the bytes that are complete, but then you have to check each side of the area and handle the incomplete bytes (i.e. change only the bits you want). That probably would be easier to understand with pics, but whatever. This will probably be a tiny bit slower than the byte implementation, but it probably won't be noticeable. Eventually, we'll be implementing it on everything that is using an array and it will speed things up considerably.