| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Exit command loop less often too avoid expensive event checking
while in batch mode.
|
|
And while we at it recommend wxWidgets-3.0.3
|
|
|
|
* dgud/wx/fixup-batch-break:
Fixup batch break
|
|
* dgud/wx/pr/1425:
wxe_impl.cpp: pointer comparison fix
|
|
Batches was breaked to often, increase the test and break
if batch is done (and queue empty).
|
|
* Fix ordered comparison between (void *) pointer and zero
|
|
With a bad timing in wx:batch() the driver could get stuck
handling commands without ever checking for gui events.
Avoid that by exiting loop after the driver have done cond_wait a
couple of times.
|
|
The user app may want to handle several mouse motion events before
drawing new data for example.
|
|
|
|
For lists the pointer was not advanced as it should which caused
following in-data (if any) to be wrong.
|
|
|
|
Enable window to handle drop file events.
|
|
Added wxDropFiles event
|
|
The default stacksize on Windows is 1MB which is not enough if you
create many dialogs and callbacks recurse back to erlang.
Increase the stacksize of 8MB which should be sufficent.
|
|
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.
|
|
The command queue could still loose a cmd because the command was
reused while still in (recursive) use, thus when deleting it after
command was done a newly added command could be mistakenly deleted and
not called.
Root cause was that wxeFifo::Strip "deleted" to many cmds.
Solve by differing deleted and executed, i.e. op= -1 cmd have been
executed and op = -2 cmd have been executed and deleted.
|
|
wxEntry is defined to take wxChar** and not char**
|
|
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.
|
|
* henrik/update-copyrightyear:
update copyright-year
|
|
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.
|
|
Set context to avoid future lookups
|
|
Introduced when I optimized the binary handling.
|
|
* dgud/wx/fix-observer-display:
wx: Revert part of 617387025b698c
|
|
Causes issues on mac and observer
|
|
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.
|
|
|
|
Avoid copying between command queues, cleaner, faster and
safer implementation.
|
|
It was broken.
|
|
|
|
After applying a command make sure that it didn't recurse to a callback
invocation, then we must re-start from the saved command queue.
|
|
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
|
