aboutsummaryrefslogtreecommitdiffstats
path: root/lib/wx/c_src/wxe_impl.cpp
AgeCommit message (Collapse)Author
2011-11-16[wx] Fix deadlock in callback handlingDan Gudmundsson
New testcase showcase the deadlock
2011-09-21[wx] Fix trailing whitespaceDan Gudmundsson
2011-09-21[wx] Fix cleanup memory referencesDan Gudmundsson
Could cause a crash in later restarts
2011-07-14Handle overloading callbacks the same as eventsDan Gudmundsson
Previously other process wx calls where allowed to execute in the callback code, but that lead to a deadlock if for example a dialog was created.
2011-07-07Add support for virtual listctrlsDan Gudmundsson
2011-03-02Make MacOS (NS) wx use the main threadPatrik Nyblom
2011-03-02Fix start argsDan Gudmundsson
2011-03-02Fixed coredump when graphics could not be initiatedDan Gudmundsson
For instance when DISPLAY was not set
2010-11-15Split opengl functionality into separate dynamic libraryDan Gudmundsson
The idea is to build a separate opengl library which can be reused by other erlang applications.
2010-08-18Callback crash reported by Sergei Golovan.Dan Gudmundsson
May also be the reason of the crash seen on windows by several others.
2010-03-10wx: Correct usage of driver callbacks from wx threadPatrik Nyblom
2010-01-19Fixed a memory reference bug which caused unexplained {badarg, Int} exits.Dan Gudmundsson
You could get a reference to another applications memory, if wx had deleted that applications memory without the drivers knowledge about it, typically memory allocated by wx and not the application using classes where wx-driver can't override the desctructors. When wx allocated new memory and got a pointer to that memory, the wx-driver detected the same pointer and forwarded the old ref to erlang.
2009-11-20The R13B03 release.OTP_R13B03Erlang/OTP