Open GoogleCodeExporter opened 9 years ago
[deleted comment]
Actually just saw this again, and this time it happened without the
"experiencing network issues" error message ever being displayed, so the two
don't seem to be directly related.
In this case, Stranger 1A and 2A were talking (about 2A's mother, humorously
enough). Stranger 1A disconnected. Linger mode disabled and auto-reconnect
enabled, so OmegleSpyX disconnected the conversation and found two new
strangers (Stranger 1B and Stranger 2B).
Two seconds after the new conversation started, Stranger 2B sent messages about
his mother, which were obviously actually still from Stranger 2A. So somehow
OmegleSpyX is keeping the stranger around who did not disconnect when linger
mode is enabled.
Original comment by dedb...@gmail.com
on 7 May 2013 at 4:16
Just noticed that last comment sentence was incorrect. Obviously it should say
"when linger mode is disabled." Sorry for the confusion!
Original comment by dedb...@gmail.com
on 9 May 2013 at 1:30
I believe the problem to be in OmegleSpyPanel around like 660 from v3.2 source,
under "if (spies[k].disconnected){" it disconnects one on the spies but not the
other because it breaks so I added this under the if:
if (k == 0) spies[1].disconnect(3);
if (k == 1) spies[0].disconnect(3);
and haven't had the issue so far...
Original comment by lazycode...@gmail.com
on 21 May 2013 at 5:42
Above should actually be:
if (!mnLinger.isSelected()) {
if (k == 0) spies[1].disconnect(3);
if (k == 1) spies[0].disconnect(3);
}
now it linger will still work when you disconnect someone but have to
disconnect the other person to start a new chat which is good enough for me.
Original comment by lazycode...@gmail.com
on 21 May 2013 at 6:39
Fixed in the up-coming update.
Original comment by malaco...@gmail.com
on 6 Jun 2013 at 10:27
Original issue reported on code.google.com by
dedb...@gmail.com
on 6 May 2013 at 2:09