Age | Commit message (Collapse) | Author |
|
Do not postpone deletion of wx*DC objects since they need to be
deleted directly. Otherwise, if inside showModal, causes an eternal
loop of wxPaint events on Windows.
|
|
Messages was routed via the wxe_server process, which caused process
to never get the message.
|
|
|
|
|
|
Mac doesn't add clicked files to program arguments, a callback
is invoked instead, send msgs to erlang about them.
|
|
Avoids crashes.
|
|
The pid is not available via driver_caller(..) (see wxeCommand constr)
inside driver_monitor callback.
|
|
Previously we could do a cleanup while we where recursed down
and thus delete the objects we where invoking.
|
|
Try to clean up the files a bit
|
|
wxWakeUpIdle doesn't always work on wxGTK and the workaround is to
periodically invoke it, so the gui-thread doesn't get stuck in poll.
Previously it was only called when NOT in batch mode, however if the
wxWakeUpIdle call after a batch_begin command did not wake up the
thread it would still get stuck in poll.
|
|
Event handlers was not removed after objects/process had been
delete/died, which causes memory leakage and that fun's was
kept in the wx_server process. Code that might be purged and
the server died.
|
|
Remove dummy windows and move the console to gui app code before
wxWidgets gets initialized to prevent hangings on current wxWidgets svn
version.
|
|
|
|
|
|
wxWidgets looked in the wrong executable after icons and cursors, stole
wxLua's solution.
Also finds wx-2.9 on windows
|
|
|
|
New testcase showcase the deadlock
|
|
|
|
Could cause a crash in later restarts
|
|
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.
|
|
|
|
|
|
|
|
For instance when DISPLAY was not set
|
|
The idea is to build a separate opengl library which can be reused
by other erlang applications.
|
|
May also be the reason of the crash seen on windows by several others.
|
|
|
|
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.
|
|
|