-
Notifications
You must be signed in to change notification settings - Fork 285
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
Child window with ALLEGRO_MENU causes crash upon open/close display. #1381
Comments
I hope I'm not wrong. For work with the menu in the Windows system, a ./addons/native_dialog/win_menu.c is needed. I can't work with Windows so I can't check either. EDIT: You have to ask for a new feature, I guess. |
win_menu.c is non-existant in the source. |
Before, we'd spawn bespoke threads every 50ms. One issue with this design was that destroying a display before that 50ms elapsed caused crashes, which happened in the menu code. The new code has a persistent thread that periodically sends those resize events. More importantly, we make sure that thread is aware of displays being destroyed. Fixes liballeg#1381
Before, we'd spawn bespoke threads every 50ms. One issue with this design was that destroying a display before that 50ms elapsed caused crashes, which happened in the menu code. The new code has a persistent thread that periodically sends those resize events. More importantly, we make sure that thread is aware of displays being destroyed. Fixes #1381
Using the ex_menu.c example in a program.
The program will crash, if you open/close the child window multiple times.
This is a problem, since I'm developing a game where you can open editor windows for e.g. maps, items, etc.
Crash upon close is in 'allegro5/platform/aintwthr.h' line 59
Crash upon open is in 'allegro/src/win/wwindow.c' line 196
GetWindowInfo(my_window, &wi);
and sometimes other places, like allegro/src/memory.c line 44
The text was updated successfully, but these errors were encountered: