Multimedia timers could be called for here. Check Nemanja Trifunovic's Timers tutorial. The minimum resolution attainable with these timers depends on the OS [and the hardware it is running on], but probably it is decent for your needs. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

You've got 2 choices: * MAPI (yuk) * SMTP (easy) I've done both -- and neither are great. SMTP has turned out to be easier, but you gotta learn the protocol. MAPI is a pain.... MAPI is a little more memory intensive, by making those memory calls, all of the MAPI suport gets loaded. SMTP only needs to load winsock... As for your main problem -- it seems that you've not actually authenticated. -p

Jeez.... talk about overkill. :-D :bob: -=:bob:=- David Wulff dwulff@battleaxesoftware.com

I know with this article, you have to specify an SMTP server, but perhaps the code will get you going in the right direction. PJ Naughter's CSMTPConnection. Jon Sagara "Go Banana!" -- Ralph Wiggum

Yeah the forum ate my code. The type was, let's try to do this explicitly, typedef std::list<Socket *> SOCKLIST; but I fixed the problem, so it's OK. Thanks for the feedback!

Thanks, I just finally found that. I guess DefWindowProc was the culprit that kept changing the cursor back!

TrackMouseEvent does this. But it's not available on Windows 95. Tomasz Sowinski -- http://www.shooltz.com

When you say char anArray[200] you are saying "Grab me 200 characters worth of local space and call it "anArray". You could them go on to put "Hello World" into it if you wanted, but only by copying it in character by character, for example with: strcpy(anArray, "Hello World!"); However because the space for anArray is local it's discarded as soon as your function exits. A pointer returned to it will point to garbage, because that pointer looses it's validity when the routine exits. The string constant "Hello World" is a different kind of beasty. The string is stored by the compiler in static storage. It's address remains valid for the life of the program. When you say, for example, const char *p = "Hello World"; You are allocating a pointer. A memory location containing the address of that static string. Not a new block of memory containing the string itself (which is why it's ok to do a simple assignment in such a case rather than a more complex copy). Does that make things clearer?

I've been caught out by this one in the past. What happens is that the object, although allocated enough space for a fooplus is first initialised as a foo object, then the foo constructor is called. At that point the foo virtual method table is in effect. Only once the foo constructor exits does the fooplus intialisation occur and the VMT switches to the one containing fooplus::bar. This behaviour is logical, fooplus::bar might refer to variables in fooplus that the foo constructor doesn't know to initialise. How you get arround it depends on details of what you're doing that we don't know. If you're really getting into polymorphic programming you'll often find the best solution is static factory routines which give you a uniform access to constructors e.g. class foo { protected: foo(...) { }; public: static foo *factory( ... ); virtual void bar(); }; class fooplus : public foo { protected: fooplus( ... ) : foo(plus) { } public: static foo *factory( ... ); virtual void bar; .. }; foo *foo::facory( ... ) { foo *f = new foo( ...); f->bar(); return f; } foo *fooplus::factory ( ...) { fooplus *f = new fooplus ( ...); f->bar; return f; } Because the factory methods are static and have the same signature you can store pointers to them in a table of variations on foo.

This is one of those problems that would have been a nagging doubt for a long time. Thanks for explaining it to me! :rose:

Thanks for the responses! Continuing on Ben's idea, I could manually set the values of the first scanline and then memcpy it to the other scanlines. However my original goal wasn't mainly speed gain but rather to make the code nicer, so I guess I'll give it a miss and just set the values manually :cool:

First, it's a good idea for everyone to have the same directory structure (if for no other reason that to serve as a common frame of reference). For instance, I have the following directory structure for ne of my projects: \Johns Projects\ --- CommonFiles --- DeMONS2\ --- D2CommonFiles --- D2Config --- D2Launcher --- D2Scrub With the directory structure described above, any project in the johns projects root can get to any header file in CommonFiles or D2CommonFiles, even if "Johns Projects" has another name or is copied (in its entirety) to another drive altogether In your project settings dialog... 1) Click Project | Settings... in the Visual Studio menu. 2) On the left side of the dialog, you'll see a combo box labeled "Settings for:". Select "All Configurations". 3) On the right side of the dialog, select the "C++" tab, and in the combo box labeled "Category:", click the "Preprocessor" item (last one in the list). 4) In the edit field lebaleled "Additional Include Directories:", and your relative path. Using the directory structure example above, for all of the projects in the DeMONS2 folder (D2Launcher, D2Config, and D2Scrub), I used "..\..\CommonFiles,..\D2CommonFiles". At this point, all you have to do is #include the filename itself without worrying about the path at all. In order to share a project, everyone will find it much simpler to just have identical directory structures.

I saw that option while I was poking around (though it doesn't help that SS_NOTIFY isn't in the MSDN help index :mad: ) and I dismissed it after looking at the scant offerings of STN_* (I think they were 'click' 'dblclick' 'enable' and 'disable' or something) since I needed more information (like *where* they clicked and which button) which is why I decided to learn about subclassing. Anyway, I tried the SS_NOTIFY style just for the hell of it, and lo and behold all of the subclassing stuff I was trying to do started working! I guess the subclassing doesn't work unless you have SS_NOTIFY on, though I can't find that in the help anywhere. Thank you, Benner! :cool: