Hello everybody,
It appears that when I use wxServer and wxClient on the same system, using TCP, I cannot always stop the Advise from the client.
This also happens when I am using the sample. In fact, I always use the client sample to run with my server.
When I use DDE, there are no issues and I can stop the Advise just fine, no crashes what so ever.
The first time I press StopAdvise, nothing happens. Then the second time, I get this:
The server is allowed access through the firewall, so it's not a security issue.
wxConnection cannot stop advise
Re: wxConnection cannot stop advise
Hi,
How do you know you can't stop it?
Thank you.
How do you know you can't stop it?
Thank you.
Re: wxConnection cannot stop advise
I start it, and then when I try to stop it, my OnStopAdvise function isn't called.
There's a log line in OnStopAdvise which logs the unique ID of the connection as well as it request.
This log line never appears. The same happens with the server sample! The OnStopAdvise line is never logged.
EDIT:
It seems that once I start my server, then stop and start the server sample, the issue occurs.
When I first run the sample, I can stop advising.
There's a log line in OnStopAdvise which logs the unique ID of the connection as well as it request.
This log line never appears. The same happens with the server sample! The OnStopAdvise line is never logged.
EDIT:
It seems that once I start my server, then stop and start the server sample, the issue occurs.
When I first run the sample, I can stop advising.