092cb9e202
GTK: Fix build for pre-C99 compilers
...
Some compilers we support, such as pre-2013 Visual Studio, does not support
for INIFINITY, log2() and exp2(), so check for exp2() and log2() during
configure, and use fallbacks for them and INIFINTY if they are not found.
https://bugzilla.gnome.org/show_bug.cgi?id=766207
2016-05-10 17:14:07 +08:00
3952bd60a5
inspector: Port to new monitor api
...
Adapt to new monitor apis, and show more information.
2016-04-27 23:18:16 -04:00
6225d435e6
inspector: do not leak seat capabilities descriprion
...
Factor out an utility function for readability and free the string
with the list of capabilities
2016-04-24 17:49:26 +02:00
8a2061f581
inspector: Don't lie with statistics
...
If we don't have statistics, despite GOBJECT_DEBUG being set,
explain how to fix this.
2016-04-14 22:52:59 -04:00
abff6e23c0
inspector: simplify some code
2016-04-09 15:48:34 -04:00
af1c873bca
inspector: Use GdkAxes instead of GdkAxisUse
2016-04-09 12:14:33 -04:00
d83ad00f9e
inspector: Add an origin mark to the slowdown scale
...
Makes it easier to get back to the original speed.
2016-04-09 11:56:08 -04:00
e6c408c08a
inspector: Give the font scale an entry
...
This matches what Matt did for the slowdown.
2016-04-09 11:56:08 -04:00
46b120b35e
inspector: add slider to control slowdown factor
2016-04-08 16:09:29 -07:00
72346cb209
inspector: add slider for adjusting the font scale
...
https://bugzilla.gnome.org/show_bug.cgi?id=761435
2016-03-25 16:10:28 -04:00
65927caf84
inspector: Look for themes in system data dirs
...
This matches what GTK+ does now.
2016-03-22 08:22:48 -04:00
7cb36aba40
Load theme settings from the right location
...
When loading a per-theme settings.ini file, look for it in
the same directory where we found the gtk.css file for the
theme. Previously, we were always looking in
$prefix/share/themes/THEME/gtk-3.0/, even if the css was
loaded from somewhere else.
https://bugzilla.gnome.org/show_bug.cgi?id=641354
2016-03-21 22:19:19 -04:00
5e68c4e62d
inspector: Reset the treewalk when required
...
The tree walk holds a tree iter, which will become invalid
when we either remove the row that it points to or remove
all rows.
Reset the tree walk in those cases to avoid a crash that
was pointed out by Bastien Nocera.
2016-03-11 13:53:57 -05:00
2e34ce8f7c
inspector: Add api to get the current tree walk position
...
This will be used in the next commit.
2016-03-11 13:53:57 -05:00
eeb945e4c1
inspector: Widgets update automatically when CSS changes
...
There's no need to force-invalidate their CSS.
2016-03-11 17:00:41 +01:00
97250ea5e6
inspector: Add a switch for the layout debug flag
2016-03-11 00:22:36 -05:00
2b773e07e3
inspector: Show the frame clock in misc
...
There is no convenient way to get a handle on the frame clock,
otherwise, and the frame clock object is where we show the frame
rate...
2016-03-10 16:21:35 -05:00
30faa9a2a9
inspector: Refine strv editor
...
Put some spacing between the rows, and link the buttons to
the entries they belong to.
2016-03-09 21:59:43 -05:00
6e9fd6832a
inspector: Do a better job with readonly properties
...
Say if they are non-writable or construct-only, and also
gray out construct-only properties in the list.
2016-03-09 21:59:43 -05:00
c24cc63523
inspector: Minor refactoring
...
Break out some functions in prop-editor.c
2016-03-09 21:59:43 -05:00
c1c8a861aa
inspector: Redo property lists a bit
...
Break out value types as a separate column, to make the
value column more readable.
2016-03-09 21:59:43 -05:00
0c929b7124
inspector: Avoid overflow when editing doubles
...
The adjustment double properties allow values from -G_MAXDOUBLE
to G_MAXDOUBLE, which leads to overflow when calculating
max - min / 10. To avoid that, simply use a fixed page_size of 1.0.
2016-03-09 21:59:43 -05:00
6af8e9f3cc
inspector: Wording changes
...
Align the property nicks of GtkCssNode with the column names
in the inspector node tree.
2016-03-09 19:29:58 -05:00
f23c77b14b
inspector: Some more cleanup
...
The last commit left some unused functions behind.
2016-03-09 19:29:58 -05:00
e5a5f0a59a
inspector: Remove an unncessary context menu
...
Now that we have the style properties on the same page again,
we don't need the context menu anymore.
2016-03-09 19:29:58 -05:00
aa193ce4a4
inspector: UI refresh
...
The sidebar in the object page was using up more space than it deserves.
Replace it with a combo box in the subheader. Now that we have more space,
put the CSS node tree and the style properties in the same page again.
2016-03-07 00:24:15 -05:00
4b5bcdeaa5
inspector: Drop the per-object CSS editor
...
The global editor is good enough for all uses.
2016-03-06 21:41:46 -05:00
251810ff40
inspector: Avoid pointless selections
...
The CSS selector and the class hierarchy are purely
informative, no need to select anything here.
2016-03-05 00:35:08 -05:00
e69c1c5a9b
inspector: More grid lines
...
I had forgotten the css property list.
2016-03-05 00:34:39 -05:00
360bad6865
inspector: Some ui refinements
...
Remove pointless expanders from lists, add grid lines and,
in some places, tree lines.
2016-03-05 00:29:06 -05:00
8b93c013c3
inspector: Simplify general tab setup
...
Factor out the code to create a listbox row with two labels,
and use it throughout.
2016-02-25 20:49:09 -05:00
4f5f299266
inspector: React to device changes
...
Recreate the device section in the general tab when
devices come or go.
2016-02-25 20:28:23 -05:00
53fe9c2b0c
inspector: use guint to fix the windows build
2016-02-25 15:25:19 +01:00
fe4602acc5
inspector: Show ::num-touches for touch devices
...
This can be useful information.
2016-02-25 08:27:08 -05:00
84ba01d713
inspector: Update for screen config changes
...
Repopulate the display section whenever the monitor configuration
changes.
2016-02-25 01:22:01 -05:00
15ccdcd25b
inspector: Don't show numeric ids
...
The vendor and product ids for input devices aren't useful
as-is; need to figure out how to translate them to names.
2016-02-25 01:10:23 -05:00
455935a06a
inspector: Show more device information
...
This adds vendor and product id and axes. This reveals that
the GDK backends have quite different quality when it comes
to returning meaningful information here.
2016-02-25 00:49:50 -05:00
03db14c2d6
inspector: Show some basic device information
...
Add information about seats and their associated devices
in the General tab.
2016-02-25 00:17:09 -05:00
13e5e83798
Add message contexts to translated strings
...
The string "None" is used in multiple contexts; add message contexts
to give translators a chance to translate them accordingly.
https://bugzilla.gnome.org/show_bug.cgi?id=762165
2016-02-16 18:33:16 -05:00
f5d4fb1a0b
inspector: Don't use unused variables
...
Windows-specific refactorings broke this.
2016-02-11 04:14:56 +01:00
76e56c5038
win32: Stop using _gdk_display global in device code
...
Use gdk_device_get_display() instead.
2016-02-11 03:44:47 +01:00
8ea573b473
css node tree: Fix crash
...
This function would return "" whenever the state of the css node was
unset, causing a crash when selecting the css node tree from the
sidebar.
2016-02-10 12:28:32 +01:00
dc407dbc8f
inspector: Avoid crash in magnifier
...
We can't use gtk_widget_draw on widgets that are not allocated.
2016-02-08 09:34:24 +01:00
fe6d4cbdf5
inspector: Drop type name from node list
...
It's not used anymore in the CSS, so people don't need to see it.
2016-02-05 19:31:47 +01:00
b783670820
inspector: Don't hardcode builtin themes
...
Insteead, enumerate the resources that are available. Fixes windows
themes not being listed in the inspector.
2016-02-04 13:35:21 +01:00
761120a5e2
inspector: Show CSS pseudoclass names for node state
...
This is a better fit for showing CSS node state, since one
commonly looks at this information to devise CSS selectors,
where the CSS names are needed.
2016-01-24 10:59:46 -05:00
d6f989f59c
Inspector: Plug a few leaks
2016-01-24 08:01:36 +01:00
57baf6804b
inspector: Show baseline value
...
The misc info page already shows the allocation and clip areas,
the baseline fits right in.
2016-01-22 22:24:46 -05:00
ffc4f8ee11
Forgotten file
2016-01-21 08:18:28 -05:00
e33bda3078
inspector: Show full allocation + clip
...
Previously, we were only showing the size of the allocation
and clip area. But there is no good reason to hide the position
of these rectangles, so add them, in the traditional format
of X geometry strings: wxh+x+y
2016-01-20 22:52:05 -05:00
