| Age | Commit message (Collapse) | Author |
|---|
|
This fixes these warning messages:
Gdk-WARNING **: Event with type 10 not holding a GdkDevice.
It is most likely synthesized outside Gdk/GTK+
Gdk-WARNING **: Event with type 11 not holding a GdkDevice.
It is most likely synthesized outside Gdk/GTK+
|
|
Calling gtk_container_add is not the correct way to chain
up to GtkBin's container_class->add. This just causes
hildon_pannable_area_add to be called again and we're in
an infinite loop. In-tree widgets have the lovely convenience
function _gtk_bin_add_child but we can't call that so we have
to jump through these hoops.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
with some added fixes for strict compiler checks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes: MB#5589
|
|
|
|
The newly added hildon stock items don't have a corresponding icon, so
they shouldn't be added to the touchselector in these examples.
|
|
In order to get advantage of the fix in the previous commit.
Fixes: NB#174382 (Only filtered contacts are picked from contact list)
|
|
This is because calls to hildon_live_search_set_text() followed by a
retrieval of the selection will then break, and at least addressbook
assumes that this will happen synchronously.
Since we only want to give better responsiveness in the case when the
user is typing, no need to go fully asynchronously.
|
|
|
|
|
|
|
|
If GtkButton:use-stock is %TRUE, look up for the string in the title
in the stock.
|
|
|
|
These stock items are the strings that are provided by the library for
standard buttons and actions. Up to now, the only possibility to use
them in application side was to find out the logical ID and to make a
call to a gettext() function. This had several disadvantages:
- It doesn't provide guarantees of API or ABI stability.
- Application developers need to find out the gettext context, which
is internal to the library.
- Calls to gettext() for hildon strings in application code causes
unwanted strings to appear in the application pot file, which cause
confusion among translators.
|
|
These methods allow for more complete matching rules, including for
example the polish Ł. Use them now in the HildonTouchSelector live
search.
Fixes: MB#9948 (Contact quick search entering L does not recognize Polish "Ł")
Fixes: NB#165083 (Contact quick search entering L does not recognize Polish "Ł")
|
|
|
|
|
|
There is no need to do a blocking call to refilter(), so simply
connect an idle callback. This improves responsiveness in huge lists.
|
|
|
|
Need to remove a row reference from the hash table when it's
no longer in the model.
|
|
|
|
This fixes a bug when the underlying model changes and the selection
becomes corrupt.
Also, this patch uses a more efficient approach when creating and
using the mapping, avoiding iterating the whole model but the selected
items only instead.
Fixes: NB#165952 (HildonLiveSearch selection is not consistent when
the model changes)
Signed-off-by: Claudio Saavedra <csaavedra@igalia.com>
|
|
Fixes: NB#162288 (Changing the presence continously will lead to
multiple GLIB Criticals in syslog)
|
|
These happen when convert_child_path_to_path() returns a NULL
pointer.
|
|
It is not necessary to maintain a selection mapping when the GtkTreeView's
selection mode is GTK_SELECTION_NONE, so don't waste time on it.
|
|
|
|
This method not returning the location of the matched string
when the string is found after a sequence of non alphanumeric
strings.
To fix this, it was necessary to extend get_next() to return as well
the location of the next valid character.
|
|
|
|
|
|
Previous patch by Alban introduces a read-after-end error
in get_next(). This is a more robust attempt at skipping
but not aborting on control characters.
Signed-off-by: Claudio Saavedra <csaavedra@igalia.com>
|
|
This allows IM to do its work and switch the keyboard layout.
Fixes: NB#155362 (Cannot change language in Contacts from keyboard)
|
|
Signed-off-by: Claudio Saavedra <csaavedra@igalia.com>
|
