| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This fixes the longstanding bug where GTK would not update styles when
parent styles would change.
https://bugzilla.gnome.org/show_bug.cgi?id=672046
|
|
|
|
|
|
| |
This just changes the arguments passed to build_properties() and moves
that function around in the source file. No functional changes are
happening.
|
|
|
|
| |
This is not used yet in this patch.
|
|
|
|
| |
This simplifies the code.
|
|
|
|
|
|
|
| |
... in the case where no change of the DOM tree actually happened.
We don't do anything yet with that information, this patch just
correctly computes it.
|
| |
|
|
|
|
|
| |
We now track what values have dependencies on what other values so that
we could in theory recompute them when we need to.
|
|
|
|
| |
This way, inherited properties can be updated.
|
|
|
|
|
|
|
|
|
| |
When values are computed, they might depend on various other values and
we need to track this so we can update the values when those other
values change. This is the first step in making that happen.
This patch does not do any dependency tracking at all, instead it uses
GTK_CSS_DEPENDS_ON_EVERYTHING as a sort of FIXME.
|
|
|
|
|
| |
... to the compute vfunc. Simplifies code quite a bit. But makes the
code no longer a simple step-by-step implementation of the spec.
|
|
|
|
|
|
|
| |
Both _gtk_css_style_property_print_value() and
_gtk_css_style_property_compute_value() aren't necessary anymore and are
replaced by _gtk_css_value_print() and _gtk_css_value_comptue()
respectively.
|
|
|
|
| |
This way, we don't need the print_value vfunc anymore.
|
|
|
|
| |
Nobody does that these days.
|
|
|
|
|
| |
Now that we call _compute() by default, we don't need any special cases
anymore that do the same thing.
|
|
|
|
| |
... instead pof just reffing the value.
|
|
|
|
| |
This is in preparation for the next commits.
|
|
|
|
|
|
|
| |
This gets rid of the public function
_gtk_css_rgba_value_compute_from_symbolic().
The fallback is now handled using a switch statement instead of letting
the caller pass the function.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a reorganization of how value computing should be done.
Previously the GtkCssStyleProperty.compute vfunc was supposed to take
care of special cases when it needed those for computation. However,
this proved to be very complicated in cases where values were nested and
only the last value (of a common type) needed to be special cased.
A common example for this was the fallback handling for unresolvable
colors.
Now, we pass the property's ID along with all compute functions so we
can do the special casing where it's necessary.
Note that no actual changes happen in this commit. This will happen in
follow-ups.
|
|
|
|
|
|
|
| |
This commit is essentially a large reorganization. Instead of all value
subtypes having their own compute function, there is the general
_gtk_css_value_compute() function that then calls a vfunc on the
subtype.
|
|
|
|
|
|
| |
Remove the g_print debug statement from propagate_purpose.
https://bugzilla.gnome.org/show_bug.cgi?id=682747
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=682724
|
|
|
|
|
|
| |
Before left/right was used.
https://bugzilla.gnome.org/show_bug.cgi?id=682662
|
|
|
|
|
| |
The lack of this was pointed out by Carlos Garnacho in
https://bugzilla.gnome.org/show_bug.cgi?id=651244
|
|
|
|
|
|
|
|
|
| |
This hint may be used in text widgets to inhibit their
input methods. The most compelling usecase is calculator
applications, which already have a builtin and better
suited onscreen keyboard.
https://bugzilla.gnome.org/show_bug.cgi?id=651244
|
|
|
|
| |
Pointed out by Carlos Garnacho in bug 651244.
|
|
|
|
|
|
|
|
|
| |
This improves the layout of the mount operations dialog to:
* Make primary labels bold in all cases
* Lay out the widgets in a grid
* Put space between the two radio groups to distinguish them
https://bugzilla.gnome.org/show_bug.cgi?id=682552
|
|
|
|
|
|
| |
gtk_widget_insert_action_group (widget, "foo", NULL) is valid, but
g_action_muxer_insert (muxer, "foo", NULL) is not. Use
g_action_muxer_remove() for that case.
|
| |
|
| |
|
|
|
|
|
|
|
| |
First, ensure we always consume floating values, as documented.
Second (and more serious), don't try to query the action if the
action name is not set yet. This will cause crashes...
|
|
|
|
|
|
| |
Because they should be normal buttons in that case.
https://bugzilla.gnome.org/show_bug.cgi?id=681617
|
|
|
|
|
| |
This should not be a const string, since the caller is supposed to free
it.
|
|
|
|
| |
This was causing a warning from the introspection scanner.
|
|
|
|
| |
Or the introspection scanner will emit a warning.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Document the new API and properties, and their interaction with
existing properties.
https://bugzilla.gnome.org/show_bug.cgi?id=651244
|
|
|
|
|
|
|
| |
Add input-purpose and input-hints properties and pass these through
to the GtkIMContext.
https://bugzilla.gnome.org/show_bug.cgi?id=651244
|
|
|
|
|
|
|
| |
Add input-purpose and input-hints properties to GtkEntry,
and pass these on to GtkIMContext.
https://bugzilla.gnome.org/show_bug.cgi?id=651244
|
|
|
|
|
|
| |
Add input-purpose and input-hints properties to GtkIMContext.
https://bugzilla.gnome.org/show_bug.cgi?id=651244
|
|
|
|
|
|
|
|
| |
This commit adds two enumerations that will be used
to pass additional information to input methods, in
the subsequent commits.
https://bugzilla.gnome.org/show_bug.cgi?id=651244
|
|
|
|
|
|
|
|
| |
It's too close to the release so we'll keep _set_menu() around, but
deprecate it, pointing to the new API. It will be removed (and the name
reused) before the 3.6.0 release.
https://bugzilla.gnome.org/show_bug.cgi?id=682235
|
|
|
|
|
|
| |
Only if there was a selection active.
https://bugzilla.gnome.org/show_bug.cgi?id=681613
|
|
|
|
|
|
| |
If a section or submenu item has a "action-namespace" attribute, the
action names of the created GtkModelMenuItems will be prefixed with that
namespace. Namespaces can be cascaded.
|
|
|
|
|
|
| |
There are no remaining users of the GActionMuxer in GtkApplicationWindow
because they've all been ported over to using the one on GtkWidget (via
GtkActionHelper, for the most part).
|
|
|
|
|
| |
The only place that this was being created was in GtkApplicationWindow
and the last commit dropped that code.
|
|
|
|
|
|
| |
There are no remaining users of the GtkApplicationWindow API to create
GSimpleActionObserver or to get the GActionObservable (ie: muxer) for
the appwindow. Drop those APIs.
|
|
|
|
|
| |
Use the muxer from GtkWidget to setup the accels rather than our own
local muxer (which will soon be removed).
|
| |
|
| |
|