You are not logged in.
I noticed a difference in how the panel clock's calendar is formatted between Adwaita and Matcha-sea.
Specifically the week number (left side) and days that belong to the previous month (top) or next month (bottom).
Where Adwaita formats the week number in a different color font than the current months days, Matcha-sea uses the same color font.
How do you change the panel clock's calendar week number font color?
I suspect I need to use some css in the local gtk.css, where do I begin to look for selector names?
Is there a way to inspect just the panel clock's calendar?
When I have tried GTK_DEBUG=interactive xfce4-panel, an inspector window is opened for everything on the panel.
Thank you.
xfce 4.16
Last edited by xfceforumorg1220 (2021-05-18 23:23:41)
Offline
When you run "GTK_DEBUG=interactive xfce4-panel" it will open a number of windows (one for each external plugin, and one for all internal plugins). To make it easier to find, its the one that has "XfcePanelWindow" listed in the object column.
That being said, the clock plugin uses the GtkCalendar widget. To affect the columns, you would direct changes to the highlight element of calendar. Something like:
calendar.highlight { color: red; }
...note, this will change all GtkCalendars in the system.
The complete list of GtkCalendar's tweakable settings are available in Adwaita's code.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
This is very helpful. For the life of me, I couldn't find Adwaita code at gitlab.
I did get the multiple inspectors. I found the clock widget. Progress. Yeah.
I can get the info from the Adwaita code, but is there any way to use the inspector to examine the calendar. Unfortunately I can't click "Select an Object" and have the clock's calendar stay active. I can use the gitlab code here, but if this comes up again, where I need to click something in order to get at the object that I really want to inspect, is there a way to somehow delay the inspector until the object is activated?
I think I can limit the css to just the clock on the panel.
calendar.highlight alters the week-number (left), as well as the days of the week (top). Is there a way to only alter the week-number? I'll keep looking at the Adwaita css.
Last edited by xfceforumorg1220 (2021-05-19 04:15:32)
Offline
I can get the info from the Adwaita code, but is there any way to use the inspector to examine the calendar. Unfortunately I can't click "Select an Object" and have the clock's calendar stay active. I can use the gitlab code here, but if this comes up again, where I need to click something in order to get at the object that I really want to inspect, is there a way to somehow delay the inspector until the object is activated?
Yes, this is an issue with the inspector - getting it to inspect popups. You need to get it to display in an app. GTK3 comes with a bunch of tests including testcalendar.c that display the calendar in an app so you can access it. I couldn't find these tests packaged in any Arch package so I built it manually. To build it, copy over the code to a testcalendar.c file on your computer, delete the "#include config.h" line and then run:
cc `pkg-config --cflags gtk+-3.0` testcalendar.c -o testcalendar `pkg-config --libs gtk+-3.0`
Then I could run:
GTK_DEBUG=interactive ./testcalendar
...and get access to the calendar widget. Unfortunately, there isn't much there. It doesn't break it down into its elements, so you are stuck guessing again.
I think I can limit the css to just the clock on the panel.
Let me know if you do - I couldn't figure it out.
calendar.highlight alters the week-number (left), as well as the days of the week (top). Is there a way to only alter the week-number? I'll keep looking at the Adwaita css.
I can't find where these two can be separated.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
[ Generated in 0.011 seconds, 7 queries executed - Memory usage: 535.3 KiB (Peak: 536.14 KiB) ]