| Age | Commit message (Collapse) | Author |
|---|
|
Been included in wxWidgets since 2.7.1, but not documented and
have been missed in wx.
Is documented in 3.0.0
|
|
Have been around since 2.6 but undocumented, add it since it is
useful in multi-display setup.
|
|
* dgud/wx/mojave-crash/OTP-15426:
wx: Do not delay deletes of wxGraphicContext
|
|
Fixes crash on Mojave, where refresh events are sent early and
invoked recursively the delete of wxGraphicContext was delayed
until after callback returned causing the crash to happen.
|
|
wx did not build with wxWidgets-3.1.1 since they have removed
wxGraphicsRenderer:CreatePen(wxPen).
Get the pen info and create the pen from that in 3.1.1 as
is done for wxGrahicsContext:CreatePen(wxPen).
|
|
Functions where missing and where without alternatives, and
the functions are available in wxWidgets-3.0.*.
So either I missed it or they where removed for a while in
wxWidgets-2.9 branch, but that should not be used anywhere as
it was only a development branch.
|
|
|
|
Enable window to handle drop file events.
|
|
Added wxDropFiles event
|
|
There seems to be a timeing dependent double delete when doing
reference cleanup after wx:destroy(). wxGraphicsObjects can thus not
be free'ed by wx in the cleanup phase. A guess is that the underlying
rendering context deletes all graphics objects without careeing about
wxWidgets reference counting.
|
|
These functions have been removed from wxWidgets-3.1 and according
to documentation have been noops anyway.
So remove them to make wx build with wxWidgets-3.1 if
wxWidgets is compiled with --enable-compat28
|
|
Commands could be executed twice, if the command was dispatched
from a callback and caused a recursive invocation of command loop.
Solution is to mark op as -1 before calling wxWidgets.
Also commands could be missed when idle processing was done inside
while executing a recursive callback, solved be always resetting peak
index after idle processing is done.
|
|
May cause incompatibility for applications but the flags argument is
out only in C++.
|
|
|
|
Available in at least 2.8.12 and later.
|
|
This is really needed on windows to get rid of flickering when updating
some widgets. These functions are only available if 3.0 and not on mac
where everything is double buffered already.
|
|
Available since 3.0
|
|
Some events are callbacks inside wxWidgets so idle processing doesn't
take place until operation is completed, for instance move/resize window
on Windows. This way we get some response while mouse button is pressed.
|
|
By default wxUSE_POSTSCRIPT is not enabled on Windows,
make it optional, postscript generation doesn't work that good
and is probably never used on windows anyway.
|
|
|
|
It was broken.
|
|
|
|
|
|
|
|
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.
|
|
delete_object used a deleted reference
|
|
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
|
|
|
|
It was missing.
|
|
|
|
Nice to have functionality
|
|
|
|
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.
|
|
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.
|
|
|
|
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.
|
|
It was missing and needed
|
|
|
|
|
|
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.
|
|
|
|
wx-2.9 have changed some functions from returning references to objects to
returning objects instead
|
|
In 2.9 several functions takes enum's instead of int as arguments,
remove dirty -fpermissive fix and fix it correctly instead.
|
|
|
|
|
|
Generated code with previous commit.
|
