Age | Commit message (Collapse) | Author |
|
So they work on both wxWidgets-2.8 and 3.0
|
|
Instead of popping up an annoying msgbox
|
|
Needed to avoid asserts when capturing mouse on Windows.
|
|
|
|
|
|
|
|
Preallocated an rt array of 64 items (which covers 99%) of the calls
and thus avoids allocation and copying in most cases.
|
|
To many floats in return value could cause a reallocation and
pointers to reallocated data. Fix it by ensuring that the temp
float array is large enough before add values to it.
|
|
When emulator is stopped all drivers are stopped but not unloaded
and since the clean wx thread stoppage code was in unload callback it
was not called and could cause crashes.
|
|
Some events where missing useful information.
May require user code recompilation, since some records in wx.hrl
have chnaged it's definition.
|
|
delete_object used a deleted reference
|
|
Remove allocations
|
|
|
|
Fix cursor constants that changes with OS and wxWidgets releases.
|
|
On mac and wxWidgets-3.0 the crtlDown field in keyboard and
mouse events are set when command button is pressed.
The ctrl key on mac keyboard is in a field called raw_control as this
would be backward incompatible to add we reuse the metaDown field as
indicator when the ctrl keyboard button is pressed.
|
|
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.
|
|
Useful class though not documented in wxWidgets-2.8
|
|
wxSL_LABELS have changed constant value in 3.0, make version agnostic
by doing a lookup during runtime instead of constant.
Thanks Enrique Fernández (efcasado)
|
|
|
|
It was missing.
|
|
Messages was routed via the wxe_server process, which caused process
to never get the message.
|
|
|
|
Nice to have functionality
|
|
|
|
Mac doesn't add clicked files to program arguments, a callback
is invoked instead, send msgs to erlang about them.
|
|
|
|
Using CPP as the variable name for the C++ compiler makes no sense, as CPP
usually refers to the C/C++ preprocessor. That's why we have CXXFLAGS for C++
and CPPFLAGS for the C/C++ preprocessor.
|
|
Remove the extra wxEvtListener that only caused confusion,
now everything is automatically cleaned up by the destructors
and event sent to erlang when it becomes delete for all cases.
|
|
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
|
|
It was missing.
|
|
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.
|
|
wxStyledTextCtrl had no wrapper class so, because it was not detected
that it had virtual destructors, thus references to it was not cleaned
up on destruction. When a process dies and wx cleans up the event handlers
access was made to the deleted object and caused a seg fault.
Added a testcase which I thought could provoke the bug but didn't.
|
|
|
|
The first window didn't get activated when using old method and new wxWidgets-3.0.1.
|
|
|
|
Find endless loop, if we wxe_master is killed we can't send messages
to it.
|
|
|
|
|
|
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.
|
|
It was missing and needed
|
|
|
|
|
|
|
|
* dgud/wx/depr-driver-if:
Document howto build wxWidgets on mac
wx: Fix crash in glu tesselate
wx: Remove deprecated driver_send_term usage
wx: Removed wx internal event
|
|
Since I have replaced the wxTreeItemIdClass with integers, there
is no way to verify that it is a valid wxTreeItemId that is returned
from the wxTreeCtrl:getItem* functions.
Still the check is that is non null so beware don't construct your own id's.
|
|
Fixes wxTreeCtrl:getBoundingRect/2 and wxTreeCtrl:hitTest/1.
wxTreeCtrl:hitTest now returns a tuple, i.e. not bug compatible with previous
releases but needed to know if the returned wxTreeItemId is valid or not.
|