-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random blank screen at connection #65
Comments
HI @arvanus This issue has happened to me several times but I was unable to identify a sequence of steps that was 100% reproducible. Best Regards, |
I think it's something related to the thread while connecting, it's an easy stuff to mess with, and hard do find |
0.9.3.1...master |
I doubt that the lack of optimization is the cause. In fact to much optimization at compiler level can lead to some strange bugs like this small example: |
Looks like don't occurs at debug, just in the "Release Dynamic" build |
Can we get a clear picture of what's happening?
Looks to me like some kind of race condition in wx setting up the dialog. So I guessed at a possible solution in pull req #117 |
Yes
double-click
3.1.3
This bug just occurs randomly in release mode,when I'm running in debug mode never occurred |
Have you tried 3.1.4? Seeing as wx3.1 is the development branch, it's likely they've created some bugs along the way. Seen problems like this before in other desktop GUI libs (Qt, IUP), and it's usually a case of forcing the dialog to layout. TBH I've just been using the wx debug DLLs for code work, I should really build the static libs. |
I'll try 3.1.4 |
Apparently with the new cmake build it's working |
Randomly occurs:
Expected behavior:
Anyone got this problem too?
I don't know if it's a build problem, some cross-compile wxWidget error or another thing like that
@mariuz had you gotten this too?
The text was updated successfully, but these errors were encountered: