When a stranger disconnects, can't type as them anymore but as the remaining stranger

[GoogleCodeExporter]

Could you, perhaps, describe how we could reproduce the problem?
When one of the two strangers disconnect (for instance stranger 1), I can keep 
typing as the other stranger only (for instance stranger 2, while only stranger 
2 is still here). Which basically means that conversation stops as soon as a 
stranger disconnects, since I can't communicate with the remaining one.
This is not always the case, but happens at least once every two times a 
stranger disconnects.

What is the expected output? What do you see instead?
The expected output would be that when stranger 1 disconnects, I can keep 
talking as stranger 1 to stranger 2.

What version of OmegleSpyX are you using? On what operating system?
OmegleSpyX v2.3.1b on Windows 7

Please provide any additional information below.
I've noticed this issue as well in 2.2.1, but I've been using 2.1.1 for a while 
without ever facing that issue.
A temporary quick fix could be not to block the typing field of anyone when a 
stranger disconnects, so at least one wouldn't be prevented to keep typing as 
the disconnected stranger (I think typing *to* a disconnected stranger is not a 
problem, it's just useless).

Original issue reported on code.google.com by fantasti...@gmail.com on 7 Feb 2013 at 9:51

[GoogleCodeExporter]

I'll look into this, thanks.

Original comment by malaco...@gmail.com on 8 Feb 2013 at 12:40

• Changed state: Accepted
• Added labels: Priority-Medium
• Removed labels: Priority-Pending

[GoogleCodeExporter]

I confirm that this is still a problem for 3.0, I just had it happen yesterday, 
shame too, wanted to finish the convo with the person, but my only option was 
to disconnect him, no swap for the other. But everything else with 3.0 is 
pretty amazing, liking it a lot so far.

Original comment by chray...@gmail.com on 12 Feb 2013 at 11:17

[GoogleCodeExporter]

I confirm that I still have the issue in 3.0 as well (which seems great 
otherwise, but I stick to 2.1.1 until it has been fixed).

Original comment by fantasti...@gmail.com on 13 Feb 2013 at 7:10

[GoogleCodeExporter]

Likewise, except it gives false disconnection messages so the blocked out 
message occurs prematurely. It will say the other person has disconnected but 
they will still continue typing.

Original comment by prid...@gmail.com on 19 Feb 2013 at 3:13

Attachments:

• what.png

[GoogleCodeExporter]

How often is this happening?

Original comment by malaco...@gmail.com on 19 Feb 2013 at 3:35

[GoogleCodeExporter]

For me pretty frequently, I'm not sure what kind of check the system makes to 
see if the stranger has disconnected but it may also repeat a few times 
throughout the conversation.

Original comment by prid...@gmail.com on 23 Feb 2013 at 12:13

[GoogleCodeExporter]

I've gotten this sort of text before, so the program probably checks two 
different places to get the number. Having it check the same place *might* make 
it work better.

Finding two strangers...
Stranger 1 connected
Stranger 2 disconnected
Stranger 2 connected

Original comment by meltynin...@gmail.com on 26 Mar 2013 at 3:27