| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NULL was returned in case of an empty last line. Every users needed to
special-case this. Now it will return the expected result: char_len of 0
with one PangoLogAttr.
In compute_log_attrs(), 'paragraph' will be the empty string "" with
'char_len' == 0.
pango_get_log_attrs() works fine with an empty string, it will return
one correct PangoLogAttr (because there is one text position for the
empty string).
It fixes the unit tests for gtk_text_iter_is_cursor_position().
https://bugzilla.gnome.org/show_bug.cgi?id=156164
|
|
|
|
|
|
|
|
| |
- only one blank line is enough to separate code sections.
- the 'signals' variable was in the middle of function prototypes.
- compare pointers to NULL in some conditions ("if(blah) should be used
only if blah is a boolean variable). It makes the code clearer.
- various other things.
|
|
|
|
|
|
|
| |
g_memmove() is deprecated, it is a simple macro that just calls
memmove() with the same parameters.
Reviewed by Paolo Borelli on IRC.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Although there is the "changed" signal, it is more correct to notify the
"text" property too. It can be useful for a small text view, where the
text is saved e.g. to gsettings with a binding to the text property.
The "text" property includes only the text, not child widgets or images,
so the notify signal is sent too many times (also for child widgets and
images), but it's not a big problem.
https://bugzilla.gnome.org/show_bug.cgi?id=624791
|
|
|
|
|
|
| |
GSlice is better for allocating structs.
https://bugzilla.gnome.org/show_bug.cgi?id=733407
|
|
|
|
|
|
| |
This is expected to happen on wayland and other platforms with no primary selection,
and just leads to the selected text being cleared after any attempt to change the
text selection itself through either mouse/keyboard.
|
|
|
|
|
|
|
|
| |
Returns NULL in case of a duplicated tag name in the tag table. It is
still a programmer error to duplicate a name, but if it happens the
behavior is a little nicer (and hopefully doesn't crash).
https://bugzilla.gnome.org/show_bug.cgi?id=614717
|
|
|
|
| |
Instead of Return value:
|
| |
|
| |
|
| |
|
|
|
|
| |
https://wiki.gnome.org/Design/OS/Typography
|
| |
|
| |
|
| |
|
|
|
|
| |
It is a little heavy handed. The text can speak for itself.
|
|
|
|
|
|
|
| |
It didn't explain the behavior when there is a non-empty buffer
selection.
https://bugzilla.gnome.org/show_bug.cgi?id=339539
|
|
|
|
|
|
|
|
|
|
|
| |
It is more logical to first delete the selection and then pasting the
text. When the selection and the text contain tags, the new behavior is
more natural.
A segfault in paste_from_buffer() is also avoided. The segfault occurs when
the text to paste is deleted because it is the selection.
https://bugzilla.gnome.org/show_bug.cgi?id=339539
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move GtkWrapMode from GtkTextTag to the GtkTextView section. The wrap
mode property is in the text view.
Links to the "mark-set" and "mark-deleted" signals.
Add a precision about gtk_text_buffer_get_iter_at_line().
Fix typo in gtk_text_tag_set_priority().
https://bugzilla.gnome.org/show_bug.cgi?id=708076
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702996
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=700007
|
|
|
|
|
|
| |
For gtk_text_iter_get_char(), due to the "Returns" at the beginning of
the description, the description was not visible. So the first sentence
has been reworded.
|
|
|
|
| |
This is a slight performance optimization in the common case.
|
| |
|
|
|
|
|
| |
Mostly making sure that return values and varargs don't loose
their docs.
|
|
|
|
|
|
| |
These functions match closely to the AtkText interface;
they will be used in the GtkTextView accessible implementation.
Keep them private for now.
|
| |
|
| |
|
|
|
|
| |
This patch fixes bug #590459.
|
| |
|
|
|
|
| |
And fix gail to not poke at GtkTextTag internals
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
gtk_text_buffer_insert_at_cursor isn't really the length of the 'text' argument
|
| |
|
|
|
|
| |
It's only needed one time and should not be used again in the code.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=623845
|
|
|
|
| |
There is no need to use caller-allocates if the scanner already detects it.
|
| |
|
| |
|
|
|
|
|
|
| |
Add (transfer none) to the return value of gtk_text_buffer_create_mark(),
as the documentation clearly states the caller doesn't have ownership of
the returned value.
|
|
|
|
|
|
|
|
| |
Copying to the clipboard is not a buffer mutation, so calling
gtk_text_buffer_begin_user_action() and _end_user_action() is only
confusing apps which connect to these signals in order to build undo
stacks or otherwise track buffer changes. Most likely, these apps
either didn't notice the bugus undo step or simply work around it.
|
|
|
|
|
|
|
|
| |
This commit was created using a script that searched for all docstrings
containing a parameter and the string 'or %NULL'.
Gdk backends and demos excluded as they are not part of a public API
https://bugzilla.gnome.org/show_bug.cgi?id=610474
|
|
|
|
|
|
|
|
| |
The Gtk-custom.c file in gir-repository contained a number of
introspection annotations. Merge those into the GTK source files.
Some documentation was moved from the tmpl/ files to accomodate
the addition of annotations.
|
|
|
|
| |
delete_interactive already uses them so no need to wrap the call.
|
|
|
|
|
|
| |
Special case \r\n in gtk_text_buffer_backspace since \r should not be
reinserted even if we are deleting one char at a time. Also add
corresponding unit test. Fixes bug #544724.
|