summaryrefslogtreecommitdiff
path: root/gtk/gtkinfobar.c
Commit message (Collapse)AuthorAgeFilesLines
* infobar: Fix typoTimm Bäder2016-05-191-1/+1
| | | | Style class names are prefixed with a '.'
* infobar: Avoid a memory leak in an error caseMatthias Clasen2016-02-261-4/+10
| | | | | | Parsing <action-widgets> could sometimes fail to free some of the data, if a nonexisting widget is referenced. Found by gcc's leak sanitizer.
* infobar: Don't expose implementation detailsMatthias Clasen2016-01-281-2/+2
| | | | Only export the documented widgets as internal children.
* infobar: remove unneeded gadgetCosimo Cecchi2016-01-031-105/+0
| | | | | | | It turns out we don't really need to use a separate gadget for the infobar, if all we do is chaining up to the parent GtkBox which already uses a gadget. Just remove all the boilerplate.
* infobar: port to use a gadgetCosimo Cecchi2016-01-031-44/+59
|
* infobar: trivial code cleanupsCosimo Cecchi2016-01-031-5/+6
|
* Don't pass widget state flags to GtkStyleContext APITimm Bäder2015-11-221-1/+1
|
* Annotate deprecated style propertiesMatthias Clasen2015-11-161-4/+4
| | | | | | Use G_PARAM_DEPRECATED with deprecated style properties. This will make it easier to identify and remove such stale properties from css, since it will now trigger warnings.
* infobar: Add a name to the css nodeMatthias Clasen2015-10-251-0/+8
| | | | This lets us avoid the type name in css.
* GtkInfoBar: Use _gtk_builder_lookup_objectMatthias Clasen2015-04-271-10/+12
|
* GtkInfoBar: Use the new helpersMatthias Clasen2015-04-271-56/+103
| | | | | | | Instead of issuing g_warning, fill the provided GError. This lets us test this error handling, and is the right thing to do. Use the new GtkBuilder helpers and g_markup_collect_attributes to do so.
* stylecontext: Split render functions out into gtkrender.[ch]Benjamin Otte2014-10-031-0/+1
|
* GtkInfoBar: Use G_PARAM_EXPLICIT_NOTIFYMatthias Clasen2014-06-091-2/+2
|
* gtk: add missing type annotations ported from Vala bindingsEvan Nemerson2014-05-271-1/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=730745
* infobar: Remove unneeded checksBenjamin Otte2014-05-011-8/+4
| | | | | Size vfuncs always get non-null out variables passed, so no need to check for NULL.
* Docs: use // for comments in examplesMatthias Clasen2014-02-141-3/+3
| | | | | Without sgml mode, we can't escape /* as /&ast; anymore, so just switch to // for comments in examples.
* docs: fully break lines in examplesWilliam Jon McCann2014-02-121-12/+21
| | | | | | | | | Try to do a better job of keeping example content from being too wide. It is often rendered as <pre> text so the only time we can wrap it is in the source. It is best to full break lines at all punctuation and to try to keep the width under 70 chars or so.
* Docs: Remove all entities and turn off sgml modeMatthias Clasen2014-02-091-4/+4
| | | | | With all element markup gone, it is time to turn off sgml mode, and get rid of entities as well.
* docs: don't use <anchor>William Jon McCann2014-02-071-1/+1
|
* docs: use proper quotations instead of '*'William Jon McCann2014-02-071-1/+1
|
* docs: use proper apostropheWilliam Jon McCann2014-02-071-2/+2
| | | | https://wiki.gnome.org/Design/OS/Typography
* docs: Use markup for linksWilliam Jon McCann2014-02-071-1/+1
|
* docs: use proper quotesWilliam Jon McCann2014-02-051-5/+5
|
* docs: Use "#" for refsect2 instead of ##William Jon McCann2014-02-041-1/+1
|
* docs: Convert to markdownMatthias Clasen2014-02-021-10/+4
| | | | Specifically, switch to using markdown syntax for sections.
* docs: Identify examples that are C codeWilliam Jon McCann2014-01-291-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=723119
* docs: use |[ ]| instead of <programlisting></programlisting>William Jon McCann2014-01-291-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=723119
* resources: move resources into a subdirectoryWilliam Jon McCann2014-01-231-1/+1
|
* GtkInfoBar: Set a more accurate accessible roleMatthias Clasen2014-01-041-4/+2
| | | | | And update the a11y tests to match. Pointed out in https://bugzilla.gnome.org/show_bug.cgi?id=721042
* infobar: Fix visibility when enable-animations=falseChristian Persch2013-12-011-1/+1
| | | | | | | | When enable-animations is false, the revealer's child-revealed property is notified immediately, so make sure to connect to it before toggling the revealer. https://bugzilla.gnome.org/show_bug.cgi?id=719510
* Add a revealer to GtkInfoBarMatthias Clasen2013-08-031-0/+35
| | | | | | Make GtkInfoBar slide in and out as it is shown or hidden. https://bugzilla.gnome.org/show_bug.cgi?id=704334
* Revert "Add a revealer to GtkInfoBar"Matthias Clasen2013-08-021-35/+0
| | | | | | | This reverts commit 1198ffb0bc195c6044d4d0efd864ccf093d637c7. This change needs more work, to avoid breaking existing ui files.
* Add a revealer to GtkInfoBarMatthias Clasen2013-08-011-0/+35
| | | | | | Make GtkInfoBar slide in and out as it is shown or hidden. https://bugzilla.gnome.org/show_bug.cgi?id=704334
* Another round of template binding api changesMatthias Clasen2013-07-261-3/+3
| | | | | | | | | | | We rename the gtk_widget_class_bind_template_child{_internal} macros by appending a _private to their name. Otherwise, it would be too magic to pass the 'public' names as arguments, but affect a member of the Private struct. At the same time, Add two new macros with the old names, gtk_widget_class_bind_template_child{_internal} that operate on members of the instance struct.
* Rename the widget template APIEmmanuele Bassi2013-07-261-3/+3
| | | | | | | | | | | | | | | | | | | | The macros and functions are inconsistently named, and are not tied to the "template" concept - to the point that it seems plausible to use them without setting the template. The new naming scheme is as follows: gtk_widget_class_bind_template_child_full gtk_widget_class_bind_template_callback_full With the convenience macros: gtk_widget_class_bind_template_child gtk_widget_class_bind_template_child_internal gtk_widget_class_bind_template_callback https://bugzilla.gnome.org/show_bug.cgi?id=700898 https://bugzilla.gnome.org/show_bug.cgi?id=700896
* widget: Use a real offset in gtk_widget_class_automate_childAlexander Larsson2013-07-261-3/+3
| | | | | | | | | | Using an offset from the struct means you can have children in both the public and private (via G_PRIVATE_OFFSET) parts of the instance. It also matches the new private macros nicer. https://bugzilla.gnome.org/show_bug.cgi?id=702563 Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
* Add an optional close button to the info barWilliam Jon McCann2013-07-241-2/+83
| | | | | | | | This adds gtk_info_bar_{get,set}_show_close_button. Similar to the one for the search bar. This can replace Cancel buttons. https://bugzilla.gnome.org/show_bug.cgi?id=704274
* Move wholly deprecated classes to gtk/deprecated/Matthias Clasen2013-07-191-1/+1
| | | | | | | | | | | | | | | | | | We've recently a number of classes wholly. For these cases, move the headers and sources to gtk/deprecated/ and adjust Makefiles and includes accordingly. Affected classes: GtkAction GtkActionGroup GtkActivatable GtkIconFactory GtkImageMenuItem GtkRadioAction GtkRecentAction GtkStock GtkToggleAction GtkUIManager
* Fix infobar docs to not mention type colorsWilliam Jon McCann2013-07-151-13/+3
| | | | | The theme may not use colors to distinguish the info bar message types.
* Make info bar action area horizontalWilliam Jon McCann2013-07-151-2/+2
| | | | | | | A vertical action area causes the info bar to be imposingly large. This defeats the whole point of the info bar which is to be unobtrusive. Not to mention it is impossible to make it look and feel good.
* gtk: Use new macros for defining private dataEmmanuele Bassi2013-07-091-5/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=702996
* Deprecate the gtk stock functionsWilliam Jon McCann2013-06-271-0/+4
|
* Start deprecating some GtkStock APIWilliam Jon McCann2013-06-251-7/+16
|
* Start migrating internals away from GtkStockWilliam Jon McCann2013-06-241-11/+8
|
* GtkInfoBar: Define children with a GtkBuilder templateTristan Van Berkom2013-04-081-43/+7
|
* Chain up custom_tag_start() propertly.Juan Pablo Ugarte2012-05-181-5/+5
| | | | Fixes bug #675899 "Infobar not loadable by GTKBuilder (using python gi introspection)"
* infobar: set default border/spacing on action/content areasCosimo Cecchi2012-05-071-4/+14
| | | | | | | | | Commit cdf473ec100d23ea6a9a8750ad301307a116b674 deprecated the style properties associated with the container border width and box spacing of the action and content areas, in favour of using gtk_container_set_border_width() and gtk_box_set_spacing() on the widgets themselves, but failed to initialize those values to the defaults.
* infobar: deprecate broken GtkInfoBar style propertiesCosimo Cecchi2012-04-301-30/+4
| | | | | | | | | | | | The way we use these style properties to set regular properties on containers accessible from the public API is really just broken, and could lead to undefined values for the spacing and border-width container properties (since they could be set from public API and then changed from under in a style_update handler from GTK). Take this as an occasion to deprecate these style properties, which do not make a lot of sense anyway, now that GtkInfoBar supports regular CSS padding and border.
* Fix info-bar reftestPaolo Borelli2012-04-301-19/+78
| | | | | | InfoBar must take into account the border and padding when requesting its allocation, since it is then drawing them. Besides, the border and background should always be drawn, even when the message type is OTHER.
* Change FSF AddressJavier Jardón2012-02-271-3/+1
|
View Lorry Controller Status