| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
Fix some configurations so that it works with new doxygen and
with complete install outside of /usr/include/wx...
|
|
|
|
|
|
This reverts commit eaf8ca41dfa4850437ad270d3897399c9358ced0.
|
|
|
|
Exit command loop less often too avoid expensive event checking
while in batch mode.
|
|
And while we at it recommend wxWidgets-3.0.3
|
|
This reverts commit dc57404252c47520f352834ad9be45ad684f96c9.
|
|
|
|
|
|
* 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
|
|
* zandra/stdlib/optional-callbacks/OTP-13801:
wx: make wx_object callbacks optional
stdlib: Make gen_fsm callbacks optional
stdlib: Make gen_event callbacks optional
stdlib: Make gen_server callbacks optional
|
|
|
|
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.
|
|
Fix error handling in gl as in wx.
|
|
|
|
Previously only accepted lists tough a call is made to
unicode:characters_to_binary/1, and the functions where specified to
handle chardata.
|
|
Enable window to handle drop file events.
|
|
Added wxDropFiles event
|
|
|
|
* dgud/wx/broken-links:
wx: Add missing specs
|
|
* dgud/wx/increase_wx_stacksize:
Request a larger stacksize for wx thread
|
|
Create correct links to datatypes outside of the wx application.
The added time for generating the doc/specs/specs_* files is unwelcome
(they are currently not used).
|
|
Some taylormade functions still used edoc spec's, and some
where wrong which caused broken links.
Change them to be real spec's and correct the types.
|
|
|
|
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.
|
|
Previously error from async functions made an exit when the next
sync call checked the message queue. This have been changed to an
error report instead since the errors where async there where really
hard to handle.
Also changed the error report format to make it easier to filter
them with a custom error_handler.
|
|
* dgud/wx/fix-seqfault-in-cleanup:
wx: Fix occasional seq fault after appliction stops
|
|
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.
|
|
Follow the convention and make atom more visibile in types and specs
|
|
|
|
|
|
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.
|
|
To avoid failing on slow machines
|
|
Bitmaps of size less than 1 generates asserts,
and size 0 event is before window is realized.
|
|
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
|
|
Needed functionality, to avoid abusing opauqe objects.
|
|
and avoid large logs when tests succed
|
|
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.
|
