I have experimented and I would love to see an MFC Tray
App, that the size is "taken into consideration". Just
using MFC is bloating it and then having resources raises
the bar more. Its MFC. I dont know a lot of people who
still really worry about the 16mb people, and this really
shouldnt hinder them that much more than they Already are.
Anyway, I know this is an old post but Thanks for
TSR History Lesson. Neat. Now they're called Utilities.
Fundamentally there kinda the same, Sorta?!! But who
I noticed on an app I wrote(simple animation)
using CSystemTray that if I let it run for a longer
period of time, the size that Task Manager reports for
Memory Usage decreases. I dont know if this corresponds
to what Norton is dishing out, but my app will start at
1500KB and Ive seen it as low as 300KB. I believe TrayCal
does this to some extent too.....
Anyway, this app is about 170KB statically linked
and comes up at about 1500Kb. I totally rewrote
CSystemTray so It no longer had MFC in it, and then
wrote the same app in Win32 and the app size ends up
at 32KB and its memory Usage comes up at 1200KB.
Significant, beats me, the only computers it's been
run on (about 30 different ones of different sizes)
all handled the original CSystemTray one just fine.
Just thought I'd share my findings, and thank Chris
for a cool class to work with!!!!
Not to difficult to tear out the MFC I might add.
Then it works swell in ATL.