Bug 268495 - Dialog buttons aren't reordered by oxygen-gtk3
Summary: Dialog buttons aren't reordered by oxygen-gtk3
Status: CLOSED FIXED
Alias: None
Product: Oxygen
Classification: Plasma
Component: gtk3-engine (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Hugo Pereira Da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-14 18:53 UTC by nucleo
Modified: 2012-05-15 04:10 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nucleo 2011-03-14 18:53:37 UTC
If I set gtk3 theme to oxygen-gtk3 buttons order in gnome-disk-utility(palimpsest) not changed to KDE defult order:

http://nucleo.fedorapeople.org/oxygen-gtk3/oxygen-gtk3-3.png
http://nucleo.fedorapeople.org/oxygen-gtk3/oxygen-gtk3-4.png
Comment 1 Hugo Pereira Da Costa 2011-03-14 19:28:00 UTC
oxygen gtk3 is not released yet, still has many (more serious) issues, and there is very little applications that we can test it on right now (we've been working with gtk3-demo only so far).

Besides there is an average of 50 commits a day on it, and bugs in gtk3 itself.

For now its just *our* (Ruslan and I) pet project.

So don't expect a fast resolution.
Comment 2 Ruslan Kabatsayev 2012-04-27 16:55:43 UTC
OK, this appears to be a bit more than palimpsest problem. This seems to affect all GTK3 apps, i.e. our DialogEngine isn't even used. Even File Open and similar dialogs have GNOME button order.
(Someone please provide any examples of apps where the order appears to be changed to KDE-like if you know of any)
Comment 3 Ruslan Kabatsayev 2012-04-27 17:52:44 UTC
Git commit 17254348ba8a0607dadde1a03a9395236d8f6f38 by Ruslan Kabatsayev.
Committed on 27/04/2012 at 19:51.
Pushed by kabatsayev into branch 'gtk3'.

Make use of DialogEngine

M  +4    -0    src/oxygenthemingengine.cpp

http://commits.kde.org/oxygen-gtk/17254348ba8a0607dadde1a03a9395236d8f6f38
Comment 4 Ruslan Kabatsayev 2012-04-27 17:53:25 UTC
The commit above fixes this bug.