summaryrefslogtreecommitdiff
path: root/gtk/gtkinfobar.c
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Set infobar css classes permanentlyPaolo Borelli2012-02-241-16/+18
| | | | | | | | | The message-type css classes must be in the widget context all the time, not only when drawing, otherwise they are not propagated to the children, for instance a label in the InfoBar must inherit the color. Add a corresponding reftest. https://bugzilla.gnome.org/show_bug.cgi?id=670555
* Init the InfoBar message_type to GTK_MESSAGE_OTHERPaolo Borelli2012-02-241-0/+5
| | | | | In this way the the code executed when the message_type property is set to its default value (which is 0) gets actually run.
* docs: Make infobar code example use GtkGrid instead of GtkTableBenjamin Otte2011-09-291-5/+3
|
* Silence a warningMatthias Clasen2011-06-161-3/+5
|
* info_bar: call style_updated at the end of info_bar_initJosé Aliste2011-06-161-0/+1
| | | | | This fix a render bug where the infobar would not add borders arount its content. Fix proposed by Benjamin Otte.
* More include cleanupsMatthias Clasen2011-06-071-1/+1
|
* GtkInfoBar: derive from GtkBox, not GtkHBoxMatthias Clasen2011-06-071-1/+2
|
* Always chain up in ::style-updatedMatthias Clasen2011-02-071-0/+2
| | | | | This was not handled consistently, but the default handler does useful things, so we should always chain up.
* State that _add_button functions return a "#GtkButton widget"Christian Dywan2011-01-261-1/+1
| | | | Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=586635
* Silence new gcc warningsMatthias Clasen2011-01-231-10/+2
| | | | | gcc 4.6.0 has started to warn about set-but-unused variables. So don't do that, then.
* Remove gtktypeutils altogetherMatthias Clasen2011-01-041-0/+1
| | | | | | Based on patches by Javier Jardón. https://bugzilla.gnome.org/show_bug.cgi?id=629955
* Drop explicit includes of gdkkeysyms.hMatthias Clasen2011-01-041-1/+0
| | | | | These are no longer needed. At the same time, port gtkimcontextsimpleseqs.h to use the new GDK_KEY_ symbols.
* Make GtkInfoBar use GtkStyleContextCarlos Garnacho2010-12-141-119/+27
| | | | | | All colors are defined now in the default css, and classes have been added so the bars are fully themeable (as opposed to gtk_widget_override_*, which require changing the color map itself)
* Revert "docs: Reinstate pixbufs section in GDK docs"Benjamin Otte2010-12-091-7/+57
| | | | | I committed my whole working tee instead of just one file. Ooops. This reverts commit ded14b256202d8792629b88874d934638762cee3.
* docs: Reinstate pixbufs section in GDK docsBenjamin Otte2010-12-091-57/+7
| | | | It was accidentally removed in 0775b0a85818e14d12087f33977e14efec6a058a
* Rewrite GtkInfoBar color handling to bypass GtkStyleMatthias Clasen2010-12-041-20/+29
| | | | | This avoids a segfault that was happening due to the recursion detection not working anymore with the old way of doing things.
* gtk: remove "gboolean homogeneous" from gtk_box_new()Michael Natterer2010-10-311-1/+1
| | | | Because it's FALSE in virtually all use cases.
View Lorry Controller Status