I'm running Pop!_OS 19.10 with KDE Plasma (5.16.5). I am using the Breeze Dark theme (which comes standard with Pop).
I just want to change the title bar color, but I am not sure how this is done. I don't want to break the existing theme, but I'm not sure how to clone an existing theme if that's possible.
Where in the theme file/folder directory is the title bar specified?
The answer referenced by Roj worked for me.
Created: /home/UserA/.local/usera.colors which contains:
[General]
Name=UserA_TitlebarTheme
[WM]
activeBackground=140,69,211
inactiveBackground=80,40,120
Kudos to Roj!
Related
I've updated my IntelliJ IDEA and after the update the javadoc`s became almost useless, as a big white block:
However, when I use any default theme from the IDE, it works just fine:
This is happening to any non default theme in IntelliJ IDEA.
Is there any way to fix this issue?
It's a known issue caused by the custom color scheme not inheriting Darcula and instead inheriting the white background Default scheme.
The solution is to either edit the scheme .xml file to make in inherit Darcula or to change the documentation background color:
I'm trying to create a dark mode for my application made in Xcode 8. My first though was to use Mojave's Dark Aqua, but I get many errors:
Unrecognized effect parameter type 10 encountered for effect type 1131375730. Skipping.
My next idea was to create my own .car file, using https://github.com/insidegui/AppearanceMaker. However, this did not change the background/window, even when I edited its Windows and Menus/Menu/Menu Background and its Colors/Window Background.
My third idea was to use El Capitan's Dark Theme (for the dark Menu and Dock, I'd assume). However, this changed the Aqua blue to a grey. Laaaaame.
What am I to do?
At the end of the day, Mojave's DarkAquaAppearance worked! I needed to set my NSWindow to the theme. (using yourNSWindow.appearance = [[NSAppearance alloc] initWithAppearanceNamed:#"DarkAquaAppearance" bundle:nil];, making sure that DarkAquaAppearance.car is in your "Supporting Files")
If you want to do the same, I have all the Mojave appearances in https://github.com/radzo73/Mojave-Appearances. It still will call errors about "Unrecognized effect parameter", but that's probably just the compressed assets, and I'm using an older system. ¯\_(ツ)_/¯
With (real) hope,
Conrad
My pelican blogs uses theme pelican-bootstrap3, and the color of code is always grey, link below,
I just want it to be
How to change its background-color to other colors.
There are various syntax highlighting styles available for Pygments. The one you are using is the default style. If you have not installed Pygments already, install it by executing:
pip install Pygments
and put:
PYGMENTS_STYLE = 'your_style_here'
in your "pelicanconf.py" and replacing "your_style_here" with your preferred style.
I recently started to create custom theme for ExtJS 5 by Sencha.
Following http://docs.sencha.com/extjs/5.0.0/core_concepts/theming.html I managed to create ThemeDemoApp, inherit ext-theme-neptune, change $base-color to green and refresh/rebuild ThemeDemoApp with my-custom-theme. All ok.
My problem is, ThemeDemoApp is quite poor for testing a custom theme. A panel, tab, button and a modal window. That's it?
After bit of googling I bumped into http://dev.sencha.com/ext/5.0.0/examples/themes/index.html. (Why isn't this mentioned in the guide?!) Heading says: View and test every Ext component against bundled Ext Themes, or your own custom themes.
My question is: How? How do I test my own custom theme against this example? Do I have to dig into the source (themes.js) and build such page/application myself?
The examples - including the Theme tester - is included in the ExtJS download.
You can modify the list of themes available by editing the shared/options-toolbar.js file.
To get it to find your theme, you'll either need to name it similar to the others (ext-theme-name), or modify themes.js accordingly.
Or you could just hack the theme.js file to hardcode your theme.
(Ext JS 4 used to create an example page for themes automatically - it doesn't seem to do that now, though)
According to advice at How do I include a JavaScript file in another JavaScript file? I decided to load both options-toolbar.js and themes.js (with just minor modification - commenting out Ext.onReady(...) function in themes.js) and I used functions getBasicPanel(), getCollapsedPanel(), etc. in my own application to create the same testing page (absolute-layout container that fits the page).
Anyhow, I guess Robert's answer is the correct one - there is no prearranged, ready-to-use functionality from Sencha :-(
I'm re-creating an AIR app with FB 4.5.1. (I've started from scratch, having had trouble importing FB 4 projects).
In the app.xml I have the following defined:
<systemChrome>none</systemChrome>
<transparent>true</transparent>
Having done this I still get a full window with titlebar, min, max, and close buttons.
what gives?
I believe you need to create a skin for the application.
This appears in Adobe's forum, and includes an FXP of a functional transparent app:
http://forums.adobe.com/thread/476699
Setting systemChrome & transparency along with "backgroundAlpha" to "0" would have helped in Flex 3.
But, skinning of components in Flex 4 i.e Spark components is little different and completely customizable.
Following are the steps you need to do make the window transparent.
Set systemChrome to "none" in the XML configuration file
Set transparent to "true" in the XML configuration file
Copy the skin code from <SDK_FOLDER>\frameworks\projects\airframework\src\spark\skins\spark\S parkChromeWindowedApplicationSkin.mxml and paste in a new MXML file.
Set the "alpha" property of "backgroundRect" object inside the skin file to "0".
Assign the newly created skin as the "skinClass" for "s:WindowedApplication" object
Please import the attached FXP file using "File->Import Flex Project" menu and have a look at the code to make it much more clear.
First, I discovered it is easier to interact with app.XML by opening it via "Open With -> Text Editor".
Second, and this is really embarrassing, I had simply failed to remove the comments bracketing
was:
<!-- <systemChrome>none</systemChrome> -->
<!--<transparent>true</transparent>-->
should have been:
<systemChrome>none</systemChrome>
<transparent>true</transparent>
...duh! I knew better, but...
Lastly, for a completely chromeless app, add
showStatusBar="false"
to the app header.
that's it!