summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* settings: Use _gtk_css_provider_load_named()wip/683896Benjamin Otte2012-09-191-4/+9
| | | | | | | | | This way we create one provider per settings object instead of stuffing it into a global unchanging never-deleting hash table. Also, we now reload the theme when instructed instead of keeping the old loaded (and possibly stale) data forever. https://bugzilla.gnome.org/show_bug.cgi?id=683896
* cssprovider: Move fallback code into _gtk_css_provider_load_named()Benjamin Otte2012-09-192-10/+21
| | | | | | | | | This makes sure the full theme loading logic resides in one function and isn't scattered around. As a side-effect, the hash table kept by gtk_css_provider_get_named() will now be populated with fallback themes. This will not be a problem after the next commit though.
* cssprovider: Export gtk_css_provider_load_named) functionBenjamin Otte2012-09-192-5/+21
| | | | | ... and document it. For now, the function is only exported internally.
* cssprovider: Split out theme loading functionBenjamin Otte2012-09-191-93/+92
| | | | | | | Split maintaining the global themes hash table and the theme loading code into two functions. This also fixes leaking the provider when loading a theme from a builtin resource.
* cssprovider: Remove another path that can't be reachedBenjamin Otte2012-09-191-16/+5
| | | | ... because the return value of a function is always TRUE.
* docs: Clarify GtkCssProvider loading return valuesBenjamin Otte2012-09-191-3/+12
|
* cssprovider: Get rid of return valueBenjamin Otte2012-09-191-14/+7
| | | | ... that is always TRUE.
* hindi updateRajesh Ranjan2012-09-191-421/+447
|
* hindi updateRajesh Ranjan2012-09-191-1345/+1413
|
* GtkSettings: Fix small typo in docs.Murray Cumming2012-09-191-1/+1
|
* Updated Galician translationsFran Diéguez2012-09-191-305/+305
|
* bump versionMatthias Clasen2012-09-181-1/+1
|
* 3.5.183.5.18Matthias Clasen2012-09-181-1/+1
|
* Prepare for 3.5.18Matthias Clasen2012-09-181-0/+66
|
* Fix distcheckMatthias Clasen2012-09-181-1/+0
| | | | A mention of gtkmodelmenu.h was leftover in Makefile.am.
* Avoid an unintented exportMatthias Clasen2012-09-181-1/+1
| | | | GtkStyleCascade is entirely private, so don't leak any symbols.
* Fix gdk docs buildMatthias Clasen2012-09-183-4/+4
| | | | | This took far too long: The actual problem turned out to be an unclosed <SECTION> in gdk3-sections.txt.
* GdkWindow: remove reference to a long-removed exampleMatthias Clasen2012-09-181-19/+0
|
* mountoperation: fix previous commitCosimo Cecchi2012-09-181-1/+2
| | | | We don't want to call this method if there's no shell agent.
* mountoperation: don't timeout proxied mount operation dialogsCosimo Cecchi2012-09-181-0/+2
| | | | | | When we proxy mount operation dialogs to the Shell agent, don't use a timeout for the remote calls, since we will be waiting on user interaction.
* Updated Spanish translationDaniel Mustieles2012-09-181-313/+310
|
* Raleigh: Improve the spinner animationBenjamin Otte2012-09-181-47/+320
| | | | Make it closer to how it was previously.
* GtkAccelLabel: adjust recent accel changesRyan Lortie2012-09-181-8/+22
| | | | | | | | | | In the event that a GtkAccelKey was present for the closure but it contained a keyval of 0 the previous code would show "". After the recent adjustments, "-/-" would be shown in this case. It turns out to be a pretty common case, so fix the logic to stop using '0' as a magic value to mean "don't have an accel" and add a separate boolean for that purpose.
* cssimage: Add a hack to get antialiased circlesBenjamin Otte2012-09-181-0/+51
| | | | | We like to draw circles in themes, and as radial gradients are the only okayish way to do that, at least make them antialiased.
* Updated Marathi TranslationsSandeep Sheshrao Shedmake2012-09-181-314/+317
|
* Updated British English translationBruce Cowan2012-09-181-306/+324
|
* Force spinners to be squareMatthias Clasen2012-09-171-3/+10
|
* GtkSettings: Properly clean up style providersMatthias Clasen2012-09-171-7/+6
|
* Revert "Bind the themes to the livecycle of the screen"Matthias Clasen2012-09-174-198/+129
| | | | | | | | | This reverts commit 1f5dea9eba4de5a54e9370fe8e4b90e6c0cec200, since it was causeing noticable behaviour changes. Previously, GTK_DATA_PREFIX=/ ./gtk3-demo would start gtk3-demo with the Raleigh theme. With that change, it was starting with no theme at all (i.e. all black).
* Updated Hungarian translationGabor Kelemen2012-09-181-649/+528
|
* gtk-demo: fancier css demoMatthias Clasen2012-09-171-14/+55
| | | | Thanks to Lapo Calamandrei.
* Updated header for Brazilian Portuguese.Rafael Ferreira2012-09-171-1214/+1387
|
* Updated Brazilian Portuguese translation.Og B. Maciel2012-09-171-660/+712
|
* css: Add a spinner animation to the default themeBenjamin Otte2012-09-171-0/+66
|
* cssanimation: Implement pausing the animationBenjamin Otte2012-09-173-25/+79
|
* stylecontext: Always create animationsBenjamin Otte2012-09-171-14/+14
| | | | | | Even when there is no current values, do create animations. This ensures that animations do exist for unmapped widgets when they get mapped later.
* stylecontext: Only create transitions conditionallyBenjamin Otte2012-09-172-2/+24
| | | | | | | | | While regular animations should always be created, transitions should not. This patch allows to express this by passing NULL as the values to transition from. It also adds a gtk_style_context_should_create_transitions() function that returns TRUE when transitions should be created.
* stylecontext: Refactor the way animations are started and stoppedBenjamin Otte2012-09-173-68/+51
| | | | | We now create animation objects unconditionally, but we only run the animation loop when gtk_style_context_should_animate() return TRUE.
* stylecontext: Clear animations for values kept in cacheBenjamin Otte2012-09-173-0/+20
|
* stylecontext: Remove leftover debuggingBenjamin Otte2012-09-171-2/+0
| | | | | | | | ... that actually was both wrong, a performance failure and has been there since the original checkin. Updating the cached style data absolutely does not mean clearing all cached style data first. There's nothing to update then.
* csscomputedvalues: Handle starting animations differentlyBenjamin Otte2012-09-173-28/+26
|
* animation: Don't set the changed properties anymoreBenjamin Otte2012-09-175-32/+14
| | | | | The code is not needed anymore. And it looked wrong, too, so I'm glad it's gone.
* csscomputedvalues: Compute the changes by animations ourselvesBenjamin Otte2012-09-171-0/+17
| | | | | Instead of letting the animation set a bitmask unconditionally, actually compare the before and after values for changes.
* cssimage: Make cross-fade code safe for non-integer sizesBenjamin Otte2012-09-171-13/+10
| | | | This includes sizes < 1px, which previously caused a SEGV.
* cssvalue: Fix out-of-bounds in array transition codeBenjamin Otte2012-09-171-2/+2
|
* themingengine: animate spinners againCosimo Cecchi2012-09-171-2/+7
| | | | Using the animation specified with CSS by the theme.
* cssvalue: Always consider values equal to themselvesBenjamin Otte2012-09-171-1/+5
|
* csseasevalue: fix wrong priority in steps easing transformationCosimo Cecchi2012-09-171-1/+1
| | | | | We need to add parentheses around the ternary operator, or it will be applied to the whole expression.
* tests: Add a simple CSS test for cross-fadeBenjamin Otte2012-09-172-0/+16
|
* cssimage: Implement (most of) current cross-fade syntaxBenjamin Otte2012-09-171-34/+33
| | | | | The CSS4 spec adapted their cross-fade syntax again. Yay! (The previous parser was completely broken anyway...)
View Lorry Controller Status