You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Moving forward the ability to choose separate window border and control themes may die in Cinnamon completely. Support for the metacity format requires a lot of code in muffin. It also has some limitations with HiDPI. They don't affect all windows either. Try opening something like calculator and you'll see it uses a window border styled by the controls theme. This is the source of a lot issues/reports on our side." - JosephM, https://forums.linuxmint.com/viewtopic.php?p=1495361#p1495361
Yep, Metacity support might be DYING OFF completely in Cinnamon. Take it with a pinch of salt, because it might not happen, but I ought to warn ya @petrucci4prez , because this will REALLY affect CinnXP BADLY if it happens.
What I think will happen if this comes to fruition, and why you should be worried if it does: Given Cinnamon's a GNOME Fork, I fear that what they're gonna do is make it so Muffin uses GTK3 Window Decorations, rather than Metacity themes, that WILL NOT THEN BE CHANGEABLE without changing the Controls Theme, just like GNOME has done for quite a while now (though GNOME does still have an option to have Metacity themes on the Metacity WM, using DCONF, but there again that's not too valid as the GNOME Shell doesn't run on Metacity anyway), meaning for starters your theme would be RUINED, the titlebars then looking just like the headerbars, ruining the XP Look that people like on your theme (if you ignore the panel), and making the titlebars look as if they weren't themed all too much...
Just wanted to warn you, in case it does happen. Just be ready to take some salt with you when thinking over this possibility, as there's still a chance this could be stopped, or rejected.
The text was updated successfully, but these errors were encountered:
dominichayesferen
changed the title
GTK Titlebars might actually need to be done.
GTK Titlebars might actually need to be themed.
Aug 14, 2018
Oh, and speaking of metacity, if you do start themeing the GTK Titlebars, an easy way to check the titlebars is to use Metacity as the Window Manager, and set its theme to (GTK3) CinnXP, to see that theming in real time...
"Moving forward the ability to choose separate window border and control themes may die in Cinnamon completely. Support for the metacity format requires a lot of code in muffin. It also has some limitations with HiDPI. They don't affect all windows either. Try opening something like calculator and you'll see it uses a window border styled by the controls theme. This is the source of a lot issues/reports on our side." - JosephM, https://forums.linuxmint.com/viewtopic.php?p=1495361#p1495361
Yep, Metacity support might be DYING OFF completely in Cinnamon. Take it with a pinch of salt, because it might not happen, but I ought to warn ya @petrucci4prez , because this will REALLY affect CinnXP BADLY if it happens.
What I think will happen if this comes to fruition, and why you should be worried if it does: Given Cinnamon's a GNOME Fork, I fear that what they're gonna do is make it so Muffin uses GTK3 Window Decorations, rather than Metacity themes, that WILL NOT THEN BE CHANGEABLE without changing the Controls Theme, just like GNOME has done for quite a while now (though GNOME does still have an option to have Metacity themes on the Metacity WM, using DCONF, but there again that's not too valid as the GNOME Shell doesn't run on Metacity anyway), meaning for starters your theme would be RUINED, the titlebars then looking just like the headerbars, ruining the XP Look that people like on your theme (if you ignore the panel), and making the titlebars look as if they weren't themed all too much...
Just wanted to warn you, in case it does happen. Just be ready to take some salt with you when thinking over this possibility, as there's still a chance this could be stopped, or rejected.
The text was updated successfully, but these errors were encountered: