summaryrefslogtreecommitdiff
path: root/gtk/gtkfontbutton.c
Commit message (Collapse)AuthorAgeFilesLines
* font button: Add an element nameMatthias Clasen2015-10-301-0/+11
| | | | Give this GtkButton subclass element name button and style class .font.
* Redo font map support in GtkFontChooserMatthias Clasen2015-06-131-10/+14
| | | | | | | | We can't add properties to the interface, since it breaks 3rd party implementations of the GtkFontChooser interface. These exist, for example in gnumeric. So, instead of a new property, add getter/setter vfuncs.
* GtkFontChooser: Allow a custom font mapMatthias Clasen2015-05-071-7/+34
| | | | | | | This lets applications show their own fonts instead of or in addition to system fonts. https://bugzilla.gnome.org/show_bug.cgi?id=748771
* GtkFontButton: Stop using deprecated APIMatthias Clasen2014-10-021-17/+44
|
* GtkFontButton: Make sure the dialog isn't destroyed on delete-eventRui Matos2014-09-281-0/+3
| | | | | | | | | | | The remaining code assumes that the dialog doesn't get destroyed, but it actually does on delete-event. In particular, the filter function and the preview text are lost as soon as the dialog is created and thus when we create a new dialog we don't have those properties to set on it anymore. https://bugzilla.gnome.org/show_bug.cgi?id=719936
* GtkFontButton: Avoid criticalsMatthias Clasen2014-08-151-2/+8
| | | | | The font_family and font_face members may be NULL, and we shouldn't cause critical warnings in that case.
* GtkFontButton: Limit the decimals shown for sizeMatthias Clasen2014-08-151-1/+1
| | | | | | | It doesn't make sense to show a font size with 6 digits. Use the same formatting we use in the font chooser widget now. https://bugzilla.gnome.org/show_bug.cgi?id=724996
* GtkFontButton: Use the same font name as the font chooserMatthias Clasen2014-08-151-9/+6
| | | | | | | The font chooser constructs the display name for the font from the family and face names. Do the same in the font button, so we don't end up calling the same font by different names, which would be confusing.
* GtkFontButton: Use G_PARAM_EXPLICIT_NOTIFYMatthias Clasen2014-06-091-4/+4
|
* GtkFontButton Trivial cleanupMatthias Clasen2014-06-091-4/+2
| | | | Replace GTK_PARAM_READABLE|GTK_PARAM_WRITABLE by GTK_PARAM_READWRITE.
* GtkFontButton: Fix the handling of show-preview-buttonMatthias Clasen2014-06-091-4/+9
| | | | We were not storing the value at all, and not notifying.
* docs: use Returns: consistentlyWilliam Jon McCann2014-02-191-2/+2
| | | | Instead of Return value:
* docs: use apostrophe in *'reWilliam Jon McCann2014-02-071-1/+1
|
* docs: don't use <emphasis>William Jon McCann2014-01-281-1/+1
| | | | It is a little heavy handed. The text can speak for itself.
* resources: move resources into a subdirectoryWilliam Jon McCann2014-01-231-1/+1
|
* 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>
* gtk: Use new macros for defining private dataEmmanuele Bassi2013-07-091-5/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=702996
* GtkFontButton: Define children with a GtkBuilder templateTristan Van Berkom2013-04-081-32/+15
|
* Deprecate gtk_widget_push_composite_child & friendsTristan Van Berkom2013-04-081-3/+0
| | | | | | | | Deprecate gtk_widget_push_composite_child, gtk_widget_pop_composite_child, gtk_widget_set_composite_name, gtk_widget_get_composite_name. This API is just bloat and was never useful, this patch deprecates it and removes all internal calls to the composite child APIs
* GtkFontButton: default show-preview-entry to TRUEMatthias Clasen2013-03-171-1/+1
| | | | | This is what the property declaration says, after all. https://bugzilla.gnome.org/show_bug.cgi?id=695948
* Change FSF AddressJavier Jardón2012-02-271-2/+1
|
* Fix void function n gtkfontbutton.c so it does not try to return a value.Brian Cameron2011-10-101-3/+3
| | | | Fixes bug #661089.
* fontbutton: Properly display absolute sizesBenjamin Otte2011-09-221-2/+4
| | | | Display them the same way as Pango does.
* fontbutton: Properly update label after property changesBenjamin Otte2011-09-221-15/+14
| | | | Previously, the font wasn't properly updated after some changes.
* fontbutton: Display the same text as elsewhereBenjamin Otte2011-09-221-11/+6
| | | | | In particular, display names of families that don't have an installed font.
* Take font size also from the font descriptionChristian Persch2011-09-131-0/+5
|
* Fix implementation of GtkFontButton:get_font_{family,face}Christian Persch2011-09-131-103/+109
| | | | | Returns a PangoFont{Family,Face} even when the font dialogue has never been popped up.
* Rename gtk_font_chooser_get_{family,face,size}Christian Persch2011-09-131-3/+3
| | | | | ... to gtk_font_chooser_get_font_{family,face,size}, in order to avoid naming conflicts in bindings.
* Add GtkFontChooser:font-desc propertyChristian Persch2011-09-131-41/+92
| | | | Add a way to set/get the font as a PangoFontDescription.
* Remove GtkFontChooser:[sg]et_fontChristian Persch2011-09-131-19/+0
| | | | | Now that the setter doesn't return a value anymore, we can just use g_object_[sg]et instead of having these vfuncs.
* Setters should not return a booleanChristian Persch2011-09-131-8/+5
| | | | | | The setter for the "font" property returned a boolean that indicated whether the given font has been found. Instead, fall back to the default font name when the given font doesn't exist.
* GtkFontChooser implementation for GtkFontButtonChristian Persch2011-09-131-11/+253
|
* Rename GtkFontChooser:font-name to :fontChristian Persch2011-09-131-4/+4
| | | | | | | GtkFontButton already has a property named "font-name" which may conflict / be an ABI break when moving GtkFontButton to implement GtkFontChooser. Also, this is more in line with how other parts in gtk (e.g. GtkCellRendererText) call a font string property.
* Make GtkFontChooser an interfaceChristian Persch2011-09-131-8/+9
| | | | | | | | Make the GtkFontChooser API similar to the Gtk{File,Recent,App}Chooser APIs by introducing GtkFontChooser as an interface, that has a default implementation in GtkFontChooserWidget. https://bugzilla.gnome.org/show_bug.cgi?id=657627
* More include cleanupsMatthias Clasen2011-08-281-1/+1
|
* GtkFontChooserDialog: GtkFontButton now uses GtkFontChooserDialog instead of ↵Alberto Ruiz2011-08-151-54/+45
| | | | GtkFontSelectionDialog
* gtk: Use const instead G_CONST_RETURNJavier Jardón2011-06-101-2/+2
|
* Drop unneeded includes: gtkalignment.hMatthias Clasen2011-06-071-1/+1
|
* Clean up more includesMatthias Clasen2011-06-071-1/+0
| | | | | Mainly removing unused h/v includes, but also adding some that will be necessary as replacements.
* Move documentation to inline comments: GtkFontButtonJavier Jardón2011-04-111-0/+12
|
* gtk: remove "gboolean homogeneous" from gtk_box_new()Michael Natterer2010-11-021-2/+2
| | | | Because it's FALSE in virtually all use cases.
* Use gtk_box_new() instead gtk_[v|h]box_new()Javier Jardón2010-10-301-1/+1
|
* Use gtk_separator_new() instead gtk_[v|h]separator_new()Javier Jardón2010-10-301-1/+1
|
* Use accessor funtions to access GtkFontSelectionDialogJavier Jardón2010-07-131-2/+2
|
* gtkfontbutton: unseal private pointerJavier Jardón2010-07-131-2/+3
|
* gtk/: fully remove gtkalias hacksJavier Jardón2010-07-101-4/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=623845
* Deprecate widget flag: GTK_WIDGET_VISIBLEJavier Jardón2010-03-011-1/+1
| | | | | | Use gtk_widget_get_visible() instead https://bugzilla.gnome.org/show_bug.cgi?id=69872
* Deprecate flag macros for toplevel, state, no window and composite childChristian Dywan2010-01-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Deprecate widget flag macros GTK_WIDGET_STATE, GTK_WIDGET_SAVED_STATE, GTK_WIDGET_FLAGS, GTK_WIDGET_TOPLEVEL, GTK_WIDGET_NO_WINDOW and GTK_WIDGET_COMPOSITE_CHILD. Also deprecate the type macros GTK_WIDGET_TYPE, GTK_OBJECT_TYPE_NAME and GTK_OBJECT_TYPE which have become redundant. Instances of GTK_WIDGET_TOPLEVEL are replaced with gtk_widget_is_toplevel, GTK_WIDGET_TYPE is replaced with G_OBJECT_TYPE, GTK_WIDGET_COMPOSITE_CHILD is replaced with use of the "composite-child" property and uses of GTK_WIDGET_NO_WINDOW are adjusted to use gtk_widget_get_has_window. Uses of GTK_WIDGET_SAVED_STATE and GTK_WIDGET_FLAGS inside GtkWidget are changed to direct flag usage. Documentation is updated to refer to gtk_widget_set_has_window and gtk_widget_get_has_window. Gail and tests are updated as well. Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=69872
View Lorry Controller Status