@SydneyBloom

Sounds like a bug. I think i see the section of code that causes it. I'll do some experiments. I have 3 MSN accounts now, so its easy for me to test. :)

EDIT: Seems to be fixed now. If the user was in your forward list but not your allow list, it was allowing/unblocking them. I've added a check to see if they're being blocked..
if(!(contacts[count].lists & ALLOW_LIST) && (contacts[count].lists & FORWARD_LIST) && !(contacts[count].lists & BLOCK_LIST))

Last edited by jahc on 13-Nov-2008 at 09:05 AM.

@jahc

I happy the site is back.....

2008-11-14: Alpha 35
- Bugfix: blocked users were being unblocked on startup. If the user was in
your Forward List but not your Allow List, it was allowing/unblocking them,
but I've now added a check to see if they're in the Block List before
doing this.
- Each chat window has a unique MUI id, so when you uniconify the app the
chat windows retain their individual size and positions. Previously all
the chat windows would open up in the same size and position after
uniconifying.
- Tinkered with code: sends online presence message a little later than
before. Let me know if you're not seeing any of your online contacts.
If this happens, try changing your status to Busy then back to Online

http://wookiechat.amigarevolution.com

@jahc

Thanks mate. Voodoo was faster DL this time ;(

@thread

2008-11-15: Alpha 36
- Only users in your forward list is displayed in the contacts list now
- When adding users to your forward list, it will create a new entry in
the contacts list if one doesnt already exist. So you dont need to
reconnect to see newly added contacts.
- Added options to the pull down menu for blocking and unblocking contacts
- Experimenting with a 3 second delay to see if that will make all the
contacts show up on startup

http://wookiechat.amigarevolution.com

@jahc

OK. thats great because now I have less contacts and I think all I see now on sabreMSN are contacts who have accepted me

When I launch sabreMSN and a contact write to me the first time, the chat window is opened and I received the first message but not seen the: xxxx is currently writing a mesage, just before, only the first time.

Maybe the AOS3 version take time to open the chat window with a long .log contact and It's why I don't see the writing message the first time, IMHO.

- How close the invite window, if opened by error ???

Thanks for the improvments on SabreMSN

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

@jahc

Hey... yesterday I downloaded 0.35 and now it's already 0.36....

...just kidding.... I wish all programs have yours updates...

_________________

@Mrodfr

Quote:

OK. thats great because now I have less contacts and I think all I see now on sabreMSN are contacts who have accepted me

Okay, good.

Quote:

When I launch sabreMSN and a contact write to me the first time, the chat window is opened and I received the first message but not seen the: xxxx is currently writing a mesage, just before, only the first time. Maybe the AOS3 version take time to open the chat window with a long .log contact and It's why I don't see the writing message the first time, IMHO.

Do you want to see the "user is typing a message.." information before they send you a message for the first time? I dont know if thats possible
EDIT: wait, I've thought about it, and the chat window opens as soon as a switchboard connection has connected. so maybe the speed of os3 is the reason you dont see the "is typing" text before the 1st message arrives.


Quote:

- How close the invite window, if opened by error ??? Thanks for the improvments on SabreMSN

Just click "Invite" a second time and it will close.

Last edited by jahc on 15-Nov-2008 at 08:40 AM.

@jahc

Quote:

Do you want to see the "user is typing a message.." information before they send you a message for the first time? I dont know if thats possible EDIT: wait, I've thought about it, and the chat window opens as soon as a switchboard connection has connected. so maybe the speed of os3 is the reason you dont see the "is typing" text before the 1st message arrives.

SabreMSN loaded here, my friend contact me by sending me a message, but not immediately (thats mean that sabreMSN AOS3.x finish to open completely the chat window) and sabreMSN wait a little and first thing receive is his first message and not the first: user xxx is typing message...

It's of course a simple detail and maybe never noticed and just would like to share this little point with you ..

Quote:

Just click "Invite" a second time and it will close.

the invite part, opened when using the first time the invite button, is not closed by using the button the second time, on AOS3.x version.

Last edited by Mrodfr on 15-Nov-2008 at 01:53 PM.

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

@Mrodfr

Quote:

SabreMSN loaded here, my friend contact me by sending me a message, but not immediately (thats mean that sabreMSN AOS3.x finish to open completely the chat window) and sabreMSN wait a little and first thing receive is his first message and not the first: user xxx is typing message...It's of course a simple detail and maybe never noticed and just would like to share this little point with you ..

I just did a test. Thats how it behaves here too. But who cares?! We're wasting time discussing behavior that doesnt even matter.

EDIT: I'm going to attempt to guess why its not working the way you want it:
When you talk with someone on MSN, the MSN client opens a switchboard connection to the user for the messages to be sent and received. I'm guessing that most MSN clients do not open the switchboard connection until a message has been typed and Enter has been pressed. If Sabre isnt receiving a "user is typing.." message, then that means the sender's client hasnt sent that notification, because the switchboard connection hasnt been opened yet. However, I'm pretty sure that when you initiate a chat with SabreMSN, then Sabre should open the switchboard connection straight away. But I dont think most clients operate that way.

Quote:

the invite part, opened when using the first time the invite button, is not closed by using the button the second time, on AOS3.x version.

My mistake, click "Invite these users" and it will close. If there are no nicks selected, then no one will be invited.

Last edited by jahc on 15-Nov-2008 at 11:44 PM.
Last edited by jahc on 15-Nov-2008 at 11:32 PM.

@jahc

I tried to remove a contact but it didn't disappear. I tried to block the same contact and I got an "Error 0" and SabreMSN disconnected.

Also, this 3 sec delay it's not working. At least for me. The first time I got some contacts, and the second time I got the rest. Using the latest release (0.36).

_________________

@Phantom

Quote:

I tried to remove a contact but it didn't disappear. I tried to block the same contact and I got an "Error 0" and SabreMSN disconnected. Also, this 3 sec delay it's not working. At least for me. The first time I got some contacts, and the second time I got the rest. Using the latest release (0.36).

Yes, MSN is very picky with what it receives. The slightest bug can cause disconnection.

When you reconnected to MSN, was the contact removed?

Btw, the 3 second thing wasnt working too well here either!

@jahc

Quote:

When you reconnected to MSN, was the contact removed?

If I remember right, it was still there.

_________________

@jahc

I'm quite happy with SabreMSN, but I have a stupid feature request: would it be possible to show contact groups or would that require an updated protocol version?

I'm trying OS3 version on MorphOS and it works perfect, thank you! 

OS4 version also works great on my CSPPC 

BTW, I have noticed in the OS3 version that the image "themes" config doesn't seem to detect the images of the smileys (perhaps due to the lack of gif|png extension?) I'll check it more carefully

Last edited by Crumb on 17-Nov-2008 at 09:03 PM.
Last edited by Crumb on 17-Nov-2008 at 07:01 PM.

_________________
The only spanish amiga news web page/club: CUAZ

SabreMSN still whips the llamas ass, already mentioned?

_________________
I´m back in 2023 on Classic Amiga with my A1200/Blizzard1230IB@50Mhz, 32MB RAM, AmigaOS3.2 and ROMs, Indivision AGA MK3, Author of Amiga-Flipclock (OS4)

@Crumb

Quote:

I'm quite happy with SabreMSN, but I have a stupid feature request: would it be possible to show contact groups or would that require an updated protocol version?

Groups isnt hard, its just that I dont like coding trees (nlisttree.mcc). I'm not even sure if the tree class supports images.. I'll look into it.

Quote:

I'm trying OS3 version on MorphOS and it works perfect, thank you! OS4 version also works great on my CSPPC

Fanks.

Quote:

BTW, I have noticed in the OS3 version that the image "themes" config doesn't seem to detect the images of the smileys (perhaps due to the lack of gif|png extension?) I'll check it more carefully

The image extention doesnt matter. As long as the image can be loaded with Multiview or any other datatypes software, it's fine.

The OS3 version may not have all the images, or may have the images commented out in the smileys.theme text file due to speed reasons on slower hardware. I recommend you download the OS4 package for MorphOS, and copy across the images and smileys.theme file.

@jahc

Sorry for annoying but I have this day some crash with sabreMSN AOS3.x.

2 or 3 sabreMSN: disconnect from the server (shell message).

But the main problem are guru or even reboot and red guru when connecting to a contact (opening the chat window)

examples:
Date : vendredi 12-déc-08 19:07:42
Task : 45765FE8 "SabreOS3"
Error : 80000003 (DEADEND)
By : System: no alert occured
Cause : Illegal address access (ie: odd)

Date : vendredi 12-déc-08 19:07:58
Task : 45765FE8 "SabreOS3"
Error : 0100000F (Recoverable)
By : ExecLibrary
Cause : Memory header not located

Date : Friday 12-Dec-08 19:29:41
Task : 44BB8800 "Unknown"
Error : 80000003 (DEADEND)
By : System: no alert occured
Cause : Illegal address access (ie: odd)

Note that the 2 contacts have long history text (100lines each).

The question is finally to know if soon will have a new version planned. thanks for the answer.

Last edited by Mrodfr on 12-Dec-2008 at 06:42 PM.

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

@Mrodfr

Quote:

Sorry for annoying but I have this day some crash with sabreMSN AOS3.x

Did it crash once or does it happen frequently?

Quote:

2 or 3 sabreMSN: disconnect from the server (shell message).

"2 or 3" what?

Quote:

But the main problem are guru or even reboot and red guru when connecting to a contact (opening the chat window)

Did this happen once or does it happen often?

Try deleting your renamed contacts file..

@jahc

Quote:

Did it crash once or does it happen frequently?

3 time yesterday (date on the MCP guru log previous message).

Quote:

"2 or 3" what?

2 or 3 shell message from sabreMSN: disconnect from the server.

This is not the crash but additionnal message from sabreMSN yesterday and crash little later.

Quote:

Did this happen once or does it happen often?

3 time yesterday. 2 time with a guru catched from MCP and last time a big red guru.

Yesterday, during the 3 crash, I have talked with 2 persons at the same time with long log each and the first crash if I remember well was during the creation of the log window.


the renamed contact file has been deleted a long time ago. just the:
email_renamed_contacts.txt just exist on sabreMSN.

Last edited by Mrodfr on 13-Dec-2008 at 05:30 AM.

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

@Mrodfr

Quote:

the renamed contact file has been deleted a long time ago. just the: email_renamed_contacts.txt just exist on sabreMSN.

Thats the file I meant. delete the "email_renamed_contacts.txt" file and see if that helps. I think I need to add some more sanity checks to that part of the program. It seems to cause hiccups regularly for users.

edit: I've uploaded a new version with more sanity checks, but I dont think it'll make much of a difference. I think I must have done something bad somewhere else.

Last edited by jahc on 13-Dec-2008 at 08:41 AM.