| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Basically everything where we hav a transition path that works for
both gtk3 and 4. We'll need to add new deprecation warnings for gtk3
once things have settled down.
|
| |
|
|
|
|
| |
skip template/builder tests for now as they require larger changes
|
|
|
|
| |
We'll get back to them later
|
|
|
|
| |
pack1/2 are gone
|
| |
|
| |
|
|
|
|
|
| |
We don't need to override anything, once we drop the deprecated
compatibility layer for pygtk.
|
|
|
|
|
| |
Drop all the deprecated compatibility layer for pygtk, and the
inheritance from GtkContainer.
|
|
|
|
| |
The Container class does not exist any more.
|
|
|
|
| |
Similar to what the Gdk.py overrides do.
|
|
|
|
|
|
|
| |
gtk4 calls get_dbus_object_path() on the default app and glib leaves
invalid GApplication instances as default in various places. It's hard
to track where a new default instances gets set, so just disable a11y
in the test suite for now.
|
|
|
|
|
| |
GFileIcon asserts that it gets a file now:
https://gitlab.gnome.org/GNOME/glib/-/commit/e2fbb74301
|
|
|
|
|
|
| |
Py_TYPE was changed to a function in Python 3.10. Suggested approach is
to use Py_SET_TYPE macro instead, see:
https://docs.python.org/3.10/whatsnew/3.10.html.
|
| |
|
| |
|
|
|
|
|
|
| |
The newest lcov supports gcc 10 again. Also collect coverage
before the tests run as a baseline and add a config file so
every lcov call uses the same settings (taken on glib)
|
| |
|
| |
|
|
|
|
|
|
|
| |
This was required for Python 2 where Python didn't import our built modules
in the build dir because there is no __init__.py. In Python 3 this just works.
Tested with setup.py/pytest/meson
|
| |
|
| |
|
|
|
|
|
|
|
| |
PyUnicode_GET_SIZE() is deprecated and actually wrong in case wchar_t
is not 4 bytes and high code points, use PyUnicode_GET_LENGTH() instead.
Fixes a deprecation warning with Python 3.9
|
|
|
|
|
|
| |
The GIL is now created by Python at initialization time no matter what.
PyEval_InitThreads() triggers a deprecation warning and will be removed in
3.10 so don't use it with 3.9+.
|
| |
|
|
|
|
|
|
|
| |
It results in crashes downstream (pulls in a meson fallback in gst-ci)
and it isn't really needed, so revert for now.
Also Fedora only has 3.1 it turns out.
|
|
|
|
|
|
| |
Motivated by the EOL of Python 3.5 and the EOL of Ubuntu 16.04 next year
this requires Python 3.6 and moves all other dependencies to what is available in
Ubuntu 18.04.
|
| |
|
| |
|
|
|
|
| |
So user have more control on whether to build it or not
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
override is there
Also make it conditional on the Gtk.Widget method existing since that was only
added with gtk 3.20 and we support 3.18+.
|
|
|
|
|
|
|
|
| |
Fixes #371. Gtk.Button.set_focus_on_click and Gtk.Button.get_focus_on_click
are deprecated since version 3.20. This override calls the Gtk.Widget methods
so that users don't get a deprecation message.
Signed-off-by: Dan Yeaw <dan@yeaw.me>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
See gtk commit c1f71ee3e8add0c8e43445b888719ac85a743583. There are now
top_level windows only.
A new gtk4 test is added to check that windows are correctly created
and work from builder.
|
|
|
|
| |
See gtk commit 2244eeb7270f5a0b351aae98c19ddbc4d4b5bea7.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
init_template method is automatically called when a widget is
created and it is not supposed to be called multiple times. That is
why this method is turned into a no-op after its first call via a
lambda function.
init_template can still be called after a widget creation (and it is
supposed to do nothing). However, a second call will result in a crash
because the lambda function has a parameter while init_template is not
supposed to have any parameter.
This issue is fixed by removing the parameter of the lambda function.
A new test is also added to assert that a second init_template call
does nothing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a widget is inside a template it is created through a
g_object_new and does not have a python wrapper when
pygobject__g_instance_init is called. In that case, a wrapper is
created and the "__init__" method is called to instantiate it. Then,
"init_template" is called to init its own template (if it exists).
However, "init_template" needs to be called before the object
constructor in order to create and instantiate all its children,
signals and properties.
This issue is fixed by calling init_template before the contructor if
the python object has been created through g_object_new.
A new test for the template hierarchy is added (based on an example
from Marinus Schraal).
Closes: #257, #386
|
| |
|
|
|
|
|
|
|
|
|
| |
This should help distros update to the new version even if they have
to still support Python 2.
If there are any open questions please add something in #392
Fixes #392
|
|
|
|
| |
This is a leftover from when things were split up
|
|
|
|
| |
Less macro magic
|
|
|
|
| |
Less macro magic
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
TreeModel.sort_new_with_model exist
In https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1134 the method was changed to a constructor
which means the API is different between older and newer gtk.
Add fallbacks for both in our overrides so both ways work all the time.
|
| |
|