| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=579466
|
|
|
|
|
|
|
|
| |
The boolean _gtk_entry_completion_resize_popup's return
value is not used anywhere, and only adds more complexity
for the method.
https://bugzilla.gnome.org/show_bug.cgi?id=751913
|
| |
|
|
|
|
|
|
|
|
|
|
| |
gtk_entry_set_completion() (and _gtk_entry_completion_connect underneath)
may happen when the entry has no toplevel yet. This window acts as the
"parent" for subsurface windows on wayland, and is indispensable to create
its backing wl_subsurface, so this resulted in non-visible popups there.
Fix this by ensuring transient_for is set before showing the popup.
https://bugzilla.gnome.org/show_bug.cgi?id=745463
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When using a completion with some custom cells in the cell layout,
if would often size wrong when first presented on screen.
The entry completion is the only place in the entire gtk code base
that calls gtk_tree_view_column_cell_get_size outside of gtktreeview
itself. It calls into the function before the tree view has done some
important validation on its cell state, the net result of which is
only the first element in the gtkcellareabox the entry completion uses
well actually have its size respected.
We now call gtk_widget_get_preferred_size on the tree view before
calling into the individual cell size routines, to guarantee that the
tree view has run its validate_rows routine and cell state is valid.
https://bugzilla.gnome.org/show_bug.cgi?id=741130
|
|
|
|
|
|
| |
I tried asking but nobody knew why it is necessary to set the background
color of the first cell. It seems with CSS styling this is completely
unnecessary.
|
|
|
|
|
|
|
|
|
|
| |
Using the setting for this property conflicts with the documentation
for gtk_entry_completion_set_text_column() which explicitly states
that setting the property directly behaves differently. Concretely,
this caused the file chooser entry completion popup to have two
columns (with identical content).
This partially reverts 331c28b369edae9aa3df2a24833ccb02ef8d7152.
|
|
|
|
|
|
|
| |
This will make the completion window use GDK_WINDOW_SUBSURFACE and be
shown relative to the parent window without involving compositor grabs.
https://bugzilla.gnome.org/show_bug.cgi?id=695504
|
|
|
|
|
|
|
| |
Add a new 'no-matches' signal and add a function pointer to gtkentrycompletionclass
and remove one from the padding at the end.
https://bugzilla.gnome.org/show_bug.cgi?id=726566
|
|
|
|
| |
Use the newer constructed instead, which has a fast path in GObject.
|
|
|
|
| |
Also, use the setter for text-column, internally.
|
|
|
|
|
| |
gtkwindow.c is too big and too messy. This is a small step
towards making it better.
|
|
|
|
|
|
|
|
| |
There are early returns in this method before the completion timeout
is set later on, so set the source to 0 to avoid trying to remove it
later again.
https://bugzilla.gnome.org/show_bug.cgi?id=725824
|
|
|
|
| |
This reverts commit 9761a966d8ffda724226a21022a42ce40932b443.
|
|
|
|
| |
This reverts commit f6a0debdd9d4f90b9d6b54c263b10926ba530c7e.
|
|
|
|
| |
This reverts commit 3c2829713463228094d66170564a4d6d7c31c245.
|
|
|
|
| |
This reverts commit a9a6fb045a0faedb30ffdad4ed979f380c483ebd.
|
|
|
|
| |
This reverts commit 2f0c610c35215229e53aac4c37fdea49e25f3742.
|
|
|
|
| |
Instead of Return value:
|
| |
|
|
|
|
| |
https://wiki.gnome.org/Design/OS/Typography
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Too many applications and libraries depend on accessing the internally
created cell renderer. Allow that again, but print a warning.
|
|
|
|
|
|
| |
Call gtk_cell_layout_clear() on the area instead of the completion in
gtk_entry_completion_clear_text_column_renderer(), because it is also
called from within gtk_entry_completion_clear().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gtk_entry_completion_set_text_column() always added a cell renderer,
regardless of whether there was an existing one already installed. This
patch reuses an old renderer if it exists, but only if it was added by a
previous call to this function.
To avoid conflicts, all renderers that were added manually are removed
when calling this function. Also, the renderer added by this function is
removed when manually adding new renderers. This effectively gives
GtkEntryCompletion two modes (managed and manual cell renderers) and
allows seamless switching between the two.
This is a minor API break. However, this shouldn't be an issue in
practice as applications couldn't call set_text_column() more than once
because of this bug. Also, it is unlikely that many applications mix
set_text_column() and custom cell renderers. The interaction between the
two modes was erratic and not documented well.
https://bugzilla.gnome.org/show_bug.cgi?id=635499
|
|
|
|
|
|
|
|
|
|
|
| |
Call gtk_entry_completion_set_text_column() when setting the
"text-column" property directly.
The completion appeared empty when setting "text-column" directly (for
example from a GtkBuilder file), because the setter creates and adds the
GtkCellRendererText.
https://bugzilla.gnome.org/show_bug.cgi?id=710533
|
|
|
|
|
|
|
| |
Add names to every timeout we setup, so it's easier to track their
usage, and debug possible misbehaviour.
https://bugzilla.gnome.org/show_bug.cgi?id=710651
|
|
|
|
|
|
| |
This way themes can easily select that window to apply custom styles.
https://bugzilla.gnome.org/show_bug.cgi?id=708414
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702996
|
|
|
|
|
|
|
|
|
|
| |
We block signal handlers areound GtkEntry signal emission and if those
signals get used to call functions on the completion that cause a
reconnection of the signals, then the reconnected signals will not be
blocked anymore (so they might get emitted?) and unblocking the old
signal id will later cause warnings.
Fixes spurious warnings in gtk/tests/filechooser tests.
|
|
|
|
|
| |
This may address
https://bugzilla.gnome.org/show_bug.cgi?id=658148
|
|
|
|
|
|
| |
This partically reverts commit
331bba1ad6c5d9535fc5a827b91019f5824e25a7, which broke documented
behaviour.
|
|
|
|
|
|
|
|
| |
Also remove the starting underscore from function names where
appropriate, as those functions are static now and not exported anymore.
This is part of a bunch of fixes for gcc complaining about
-Wmissing-declarations.
|
|
|
|
|
|
| |
This commit moves all the entry completion implementation
into gtkentrycompletion.c. It also gets rid of an unnecessary
completion_device member in GtkEntryPrivate.
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of setting it on the child scrolled window. This is needed
because the whole window's allocation must be equal to the one of the
entry (in case the popup-set-width property is TRUE); if we set the size
request on a children of the window, there might be other children with
borders/paddings in between the toplevel and the child we set the size
request too, which will break alignment.
https://bugzilla.gnome.org/show_bug.cgi?id=672947
|
|
|
|
|
|
|
| |
The completion popup should be aligned with the GtkEntry allocation, not
less than that.
https://bugzilla.gnome.org/show_bug.cgi?id=672947
|
|
|
|
|
| |
Most of these are forgotten :'s and similar details
which gtk-doc now warns about.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gtk_entry_completion_set_property() was setting many properties by
directly modifying priv values, bypassing notification invocation and
possibly another actions done by gtk_completion_entry_set_xxx ()
functions. Fix by invoking set_xxx() instead of setting the property
value directly.
The real bug observerd was that setting text-column property using
g_object_set() caused SIGFPE later when entry completion was about to
appear. gtk_entry_completion_set_text_column () apparently does way
more important things than just setting priv->text_column member.
https://bugzilla.gnome.org/show_bug.cgi?id=673693
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This uses the new workarea API to avoid placing popups underneath
panels, docks, etc.
|
|
|
|
| |
I want to use it in the file chooser entry autocomplete code.
|
|
|
|
| |
and remove gtkmainprivate.h completely.
|
| |
|
|
|
|
|
| |
Patch by John Lindgren,
https://bugzilla.gnome.org/show_bug.cgi?id=650110
|
|
|
|
|
| |
Indicate what kind of area will be used by default if none is
provided by the user.
|
|
|
|
| |
See https://bugzilla.gnome.org/show_bug.cgi?id=641073
|