Shoutbox

try turning off the chat logging then put it on again

Still no go. Just tried it then. Same bug appears. I didn't think it would've helped too much given that other people also experience it.

I think it may be to do with under what conditions trigger the writing of chat in a window to the logfile. IE: it writes when you send a message, and when you recieve a message after you've sent one or after they've sent one, but not if it's the first message they've sent that you recieve, prior to all of that.

Alas, I have no ability to find the bug in code

can you show me a screen shot of the problem

You'll note that I messaged him with "ok message me again to recreate this smegging bug" and then closed the window. He then replied, as can be seen in the acutal chat window, with "indeed" and then I replied "ta", however in the logfile, "indeed" does not exist, and nor will it ever appear later on unless I leave that chat window open for a long time.

Another thing to note that with each time I close/reopen a chat window, it considers it a new session as far as logging goes. This never used to be the case in versions prior to MSN live! plus - it had some sort of timeout where it took, say, 5 minutes of no active conversation before it considered the last session to have ended and the new one to have begun. If I had done the same thing in older versions, it would've simply considered it all one session and logged all text. I figure this may help to pinpoint down the bug if Patchou reads this.

Anyhow, it's 3am here so I'm off to bed. Adios.

Ok i think i know ...... were did you dowlnload wlm from

http://get.live.com/messenger/overview
It's version 8.0.0812 - the latest they've put up there.

I have modified it with apatch (as can be seen by the rather simple view of it) but I'd not see why that should affect the execution of a script that is included as part of Messenger Plus. If it is, however, then I'm going to have to change one of them.

ok uninstall it then install it again ( remember to save contacts )

Reinstalling WLM has about 0% of helping you with this to be honest, but back onto the problem...

In the screenshot posted, I recall seeing this thread in the beta testers section a few months back. It appeared to be fixed at that stage so it could be something reocurring.

I think it's something to do with the fact when your contact sends that first message the window isn't already created so Plus! Live finds it a bit more difficult to log for one reason or another... hopefully next time Patchou pops into the forums he'll give it another look, as there's no simple fix at the moment.

[OFF TOPIC RANT]

krissyafc,

It is nice you're trying to help, but can you please NOT post when you don't know what you're talking about.

The only senseable thing you've did in this thread is asking for a screenshot (and even that wasn't really needed as the problem has been described clearly already)...

quote:

---

Originally posted by krissyafc
Can it be that when you send somthing it takes say 2 minutes to go to the chat logg so if you wait a while it will all be there.
(..)
well try to keep the convo open For ten minutes that might work

---

That is VERY clearly not the case. It has been stated several times that a first message isn't logged, but all the others afterwards are.

quote:

---

Originally posted by krissyafc
try turning off the chat logging then put it on again

---

Messages are being logged, it is not that nothing is logged.

quote:

---

Originally posted by krissyafc
Ok i think i know ...... were did you dowlnload wlm from

---

Hasn't got todo with anything.

quote:

---

Originally posted by krissyafc
ok uninstall it then install it again ( remember to save contacts )

---

If it is a bug it is going to be present in the re-install too. It is very clear that the problem is not because of a "bad" installation. Also, you never need to save contacts when uninstalling ad/or re-installing. Contacts are kept on the msn servers

[/OFF TOPIC RANT]

Correct - reinstalling won't assist given that this problem has spanned multiple computers and multiple reformats. It's not a bug to do with corrupted files, but rather the code itself.

Ah well, here's hoping the big man himself has some idea.