Having a hard time following the logic on your math. You're multiplying the tangent by 12, which appears to be the length of the hypotenuse since you using it later in what looks like the Pythagorean theorem. Since tangent has no relation to the hypotenuse, I'm not sure why you're doing that. (tangent = opposite / adjacent). I'm not sure what you're trying to do, but if it's drawing "spokes" (like a wagon wheel) from the origin to various angles, then why wouldn't you just use something like: x = length * cos(currentAngle) y = length * sin(currentAngle) And sweep thru the angles you want to cover?

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

Apparently you can make your own from an old DVD drive and a Maglite flashlight: http://www.youtube.com/watch?v=SdN08Qfs9wI

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

The most annoying thing I see is: "I should of..." People actually type that crap instead of: "I should have..." or "I should've..." I'm not a grammar expert by any stretch of the imagination, but that one astounds me. :)

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

It seems a little bit hackish, but that might actually work ;). It's almost like a proxy server at that point. I found a pretty cool thread on dotnet247.com after finding the highly undocumented "PageParser" class. This approach might actually work for me: PageParser idea I'm going to try that approach later and see what happens.

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

The problem is if you forward it to an ASPX page (via Server.Transfer or other methods) the underlying ASPX page still generates a FORM with an ACTION attribute with its name. In other words, if Page.xxx redirected to Page.aspx, the page that's generated still goes to Page.aspx. I want it to post to Page.xxx and have that page forward the post values to Page.aspx. It's hard to explain exactly why I want this (without going into a lot of details), but here's what I'm trying to do in a nutshell 1. Accepts all request of a given extension (easy, use a HttpHandler) 2. Based upon the requested URL (what's in the browser's address bar basically), it then determines which underlying ASPX page to actually load 3. Have that ASPX generate itself and have the output POST to the original request's URL (so that the POST comes in the same way as the original GET) I can currently use some things in my HttpHandler like Server.Execute, but the underlying ASPX page still generates it's own name as the action attribute in the POST. I can then modify the ASPX page's output to get the proper action in, but then IsPostback and events in general stop working inside the ASPX page.

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

Please don't ask me why I'm doing this (trust me, it makes sense in my system), but I'd like to basically redirect requests for a certain extension (thus a handler) to an ASPX page behind the scenes. I've created a handler and set it up to handle the extension in question. In my ProcessRequest, I'd like to basically figure out which ASPX page to "forward" the request to. I've tried all sorts of methods (Server.Transfer and Server.Execute for instance), but they all have their downfall. One problem is the ASPX page in question always sets his form "action" to the name of his own page (ending in ASPX). I'd like the "action" to be the URL I'm currently at (which will in turn eventually get handled by the same ASPX page). I figured out a cheesy way to get the action to properly have the correct output by using the Server.Execute overload that allows you to redirect the output to a TextWriter and then modifying the output and sending that out. The problem with that approach is now the IsPostback of the actual page never thinks it's a post back and controls never get their events fired. Does anyone know of a way to do what I'm trying to do?

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

I'm not sure what type of transparency you're currently building into this PNG. If you're doing a color key where basically one color indicates 100% transparency, you can't really do something like anti-aliasing. Your image would have to know color of what it's being drawn on top of an anti-alias to that color (thus defeating the purpose of a transparent image :)). People have this problem with transparent GIF's because they only allow one color in the pallete to be transparent (100% transparent). If you can get an alpha channel going instead of a color-key (256 levels of transparency on 8 bits of alpha for instance), then you can have the edges do some anti-aliasing. I'm not exactly positive of the best way to actually anti-alias, but I can tell you it's pretty much impossible for things with only 100% or 0% transparency (without knowing what you're being drawn on top of). One easy (cheesy) way to make it look better is draw the image at 2x or 4x and then resize (with a good resizing algorithm) it to the size you want (all with an alpha channel, in other words a 32-bit image). Let us know how this turns out...

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

Good deal. Glad to see someone else stumbled across that REALLY useful error message as well :).

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

Not sure if you were getting the same "general error" I was (I got something equally informative), but I ran into a problem writing an HTTPHandler to convert TIF's to PNG's on the fly. I was trying to save the image to the ResponseStream directly, but I kept getting that error. I then created a MemoryStream, and I was then able to write the contents of the MemoryStream to the HTTP Response. I'm GUESSING here, but I think the stream it wants needs to be seekable, so in my case the HTTP ResponseStream didn't work. You might make sure that the stream you're trying to write the PNG is a MemoryStream and see if it fixes some of your problems.

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

Nice find...I just wish they would have had that up a few years ago :).

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

They did a deal with Computer Associates so you can get a personal firewall (think Zone Alarm) and anti-virus free for a year. Go here. Pick your OS, pick "use detailed steps", get to step 3 and notice you can get anti-virus from Computer Associates 12 months for free. If you're in a non-commercial environment and want anti-virus longer than 12 months, I recommend this one.

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

You can load the document into an XmlDocument class (Load method) and then start adding XmlDocumentFragment's as children to the various XmlNode's inside the XmlDocument. Once you've got the document modified, then you could save it out using the Save method.

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

Knowing your taste in music, it would have been my first guess anyway.

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

Give my buddy Google one while you're at it...

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

(Paul) Bruce Dickinson of Iron Maiden?

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

They're not perfect *cough*

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

//bill dean says kids, stay in school ;)

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

From what I understand, the RFC allows a LOT of crap that "nobody" uses. For instance, fred@123.123.123.123 (IP address) is supported in the RFC. There's also a lot of people who try to check things like the length of the TLD (2 - 6 characters for the museum TLD). I'm currently using the regular expression here. It's a pretty decent one. Also notice how many submissions there are on that site for email regular expressions. Some people stick to the RFC and some people realize the RFC is not quite restrictive enough for "real" usage.

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

I did this for a large email list, and in the end, it was mostly a waste of time. You can forget getting anything from AOL. When I tried it, hotmail and msn actually did verify the addresses. I'm not sure if that's still true. You end up creating a fairly complicated program to handle all of the conditions (couldn't find the MX record, couldn't connect to any of the given MX's, try again later? how many times?). You'll get so many false positives (SMTP servers that say "sure, I'll send email to fred@... when fred doesn't exist). Depending on your connection, you'll also run into servers that won't even allow you to connect ("you're on a cable modem? you have no business trying to relay mail..."). Don't get me wrong, it's a pretty fun project. Just don't expect to get too much valuable information from it :).

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins

Look at the protected keyword...

I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins