I don't think this is a problem with AIMLog. I believe that I have experienced this since downloading AIM 4.2.1107. You might try using AIMLog with earlier versions of AIM which may be found at ftp://ftp.aol.com/aimgen/73010 and see if it still happens.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You're right, with AIM 4.2.2144 (Oct. 2), this bug occurs in IM Images connections WITHOUT AIMLog running. However, in normal conversations, it only occurs while AIMLog is running and it is reverted once you close AIMLog.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running AIM version 4.3.2188 and AIMLog version 0.5 (recompiled to fix the runtime 380 bug), and this problem is still happening here. It has happened on every computer I've tested it on, and no new version of AIM has fixed it. It can't just be me, because I have tested it on 3 different computers (two running win2k and one running windows 98).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to write an AIM logger program a few months ago myself and ran into the same problem... anyone figure anything out??? I'm getting ready to do some debugging/subclassing on the aim.exe process to do the logging, but I really didn't want to resort to that. ;-) Oh yeah, I also emailed AIM tech support with a feature request to ask if they were ever going to put in plugin support. Someone actually responded and he said they were working on it right now. So, sometime this next year we may be able to write a plugin and access AIM's memory space without "hacking" it. :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think the problem occurs anymore with aim 5+ . but if
for any reason it does... *cough* SendMessage
(AIMConvoBoxWnd,WM_VSCROLL,wparam,lparam) *cough*
If you feel so obligated to use WM_GETTEXT to pull out
crucial log information, Who says you can't use
WM_VSCROLL to make sure the vertical scroll bar
behaves :P
-XenoZ-
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think the problem occurs anymore with aim 5+ . but if
for any reason it does... *cough* SendMessage
(AIMConvoBoxWnd,WM_VSCROLL,wparam,lparam) *cough*
If you feel so obligated to use WM_GETTEXT to pull out
crucial log information, Who says you can't use
WM_VSCROLL to make sure the vertical scroll bar
behaves :P
-XenoZ-
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
damn dude, when the hell are u going to fix this? fix this, and aimlog will finally be usable
I don't think this is a problem with AIMLog. I believe that I have experienced this since downloading AIM 4.2.1107. You might try using AIMLog with earlier versions of AIM which may be found at ftp://ftp.aol.com/aimgen/73010 and see if it still happens.
You're right, with AIM 4.2.2144 (Oct. 2), this bug occurs in IM Images connections WITHOUT AIMLog running. However, in normal conversations, it only occurs while AIMLog is running and it is reverted once you close AIMLog.
The newest beta of AIM (4.2.2179) fixed this problem. I recommend downloading it.
I am running AIM version 4.3.2188 and AIMLog version 0.5 (recompiled to fix the runtime 380 bug), and this problem is still happening here. It has happened on every computer I've tested it on, and no new version of AIM has fixed it. It can't just be me, because I have tested it on 3 different computers (two running win2k and one running windows 98).
I tried to write an AIM logger program a few months ago myself and ran into the same problem... anyone figure anything out??? I'm getting ready to do some debugging/subclassing on the aim.exe process to do the logging, but I really didn't want to resort to that. ;-) Oh yeah, I also emailed AIM tech support with a feature request to ask if they were ever going to put in plugin support. Someone actually responded and he said they were working on it right now. So, sometime this next year we may be able to write a plugin and access AIM's memory space without "hacking" it. :-)
Logged In: NO
I don't think the problem occurs anymore with aim 5+ . but if
for any reason it does... *cough* SendMessage
(AIMConvoBoxWnd,WM_VSCROLL,wparam,lparam) *cough*
If you feel so obligated to use WM_GETTEXT to pull out
crucial log information, Who says you can't use
WM_VSCROLL to make sure the vertical scroll bar
behaves :P
-XenoZ-
Logged In: NO
I don't think the problem occurs anymore with aim 5+ . but if
for any reason it does... *cough* SendMessage
(AIMConvoBoxWnd,WM_VSCROLL,wparam,lparam) *cough*
If you feel so obligated to use WM_GETTEXT to pull out
crucial log information, Who says you can't use
WM_VSCROLL to make sure the vertical scroll bar
behaves :P
-XenoZ-